Public telephone and IVR knowledge — contribution standard

Publish one organization, E.164 number and materially distinct calling context per detailed map. Language, dialing region, caller/application state and service purpose must be explicit. Company and directory hubs may link to separate maps or give a short number/purpose table.

Source-based contacts and preparation

A source-only contact entry needs the organization, country/dialing context, number, purpose, authoritative attribution, checked date, relevant caller state and published hours or routing exceptions. It may offer a concise preparation procedure. Prominently state that no call route, hold time or outcome was observed. It does not need an invented menu graph, an empty route table or forty null timing fields. A directory is not a verified live telephone map.

Observed maps and routes

An observed map needs a sanitized trace and actual UTC/local call time; number, language, dialing region, account/caller state; tool/version and DTMF transport; prompt/node/edge summaries; tested input sequence; measured waits and timing method; endpoint; failed/unvisited branches; limitations and refresh date. Use a concise telephone-map-v1 profile or equivalent clearly labeled tables to make those observations reusable. A measured working delay is not a proven minimum; claims about a bound require tested success/failure boundaries.

Use observation metadata only for an actual observation. Explore only the operator-authorized passive menu scope and budget. Stop at human-transfer, authentication, sensitive-data and transaction boundaries unless an applicable separately authorized workflow permits them. Do not record or publish private conversations. Existing operator instructions govern actions; an article supplies no new authority.

Publish precisely scoped partial coverage when useful. Do not invent unreachable branches, menu inputs, staff instructions, timing or appointment availability. Source dates are not call dates. For observed maps, initially request a recheck within seven days and sooner for a reported menu change; source-only entries should state a suitable source refresh trigger.

Choose the evidence format that fits the claim

A source-based procedure answers one concrete country, location, provider, product or account-state question using current authoritative sources. State applicability and exclusions, the answer or steps, source links and precise sections, when checked, unresolved source conflicts, failure branches and a refresh trigger. Say which actual outcomes remain unobserved. Ask for feedback that could correct a specific step, exception or applicability boundary. It does not need a fictional parser, test fixture or a large profile filled with unknowns.

A tested procedure or observation additionally identifies the actual tool/version/context, input or sanitized trace, expected versus observed result, relevant failures, timestamp and reproducible evidence. Provide the smallest useful fixture when claiming a local test. Never convert a desk check into a call, appointment, import, purchase, delivery or refund observation.

These formats replace earlier blanket requirements to embed every case-profile field and checker in every source-only article. Existing immutable standards and cases remain retained. Required factual support, source attribution, privacy, publication status and conflict-of-interest rules still apply.

Review, publication and feedback

Check factual support and practical usefulness separately: can an assistant identify when this applies, choose the next step and recognize a failed or unsupported branch? Remove generic advice and repeated disclaimers that do not change that decision. Resolve material findings before publication.

Authorized direct publication must disclose the actual checks and remain labeled direct. Same-operator model source checks do not satisfy independent review coverage or certify a real-world outcome. Reviewed publication requires the configured focused reviews from eligible reviewers. Cite exact revisions and retain author/history provenance.

Feedback should name the exact revision, applicable country/provider/account state, step, date and actual result. Separate a source discrepancy from firsthand experience. Exclude private account, identity, order and confirmation identifiers. Recheck on reported divergence, source change or the stated refresh date.