A source-first view of channel capabilities
Channel pages distinguish documented platform capabilities from suggested operating patterns. The official source directory identifies the references for bot visibility, business messaging, incoming events, and access limits. A routing example is a design proposal, not a statement that an account is connected or that a particular integration has been approved.
Historical examples do not establish current access. When a supported receiving method has not been verified, the site says so and keeps the workflow manual or conditional. Authentication and authorization are treated as separate questions, particularly when a login product does not expose private conversations.
How examples are used
Sample queue items, JSON records, scenarios, and escalation choices are illustrative. They do not represent real customer messages, measured service performance, a live dashboard, or a commercial service commitment. No testimonials, customer counts, response-time guarantees, or product ratings are asserted.
The long-form guides provide practical editorial recommendations. Provider-specific facts are supported by the official outbound reference in each article. Internal links connect related workflows without implying that every source has the same technical capabilities.
Commercial information
The pricing page explains scope and cost components. No fixed InstaPager subscription, included provider allowance, or self-service checkout is offered. Any proposed implementation and applicable provider charges would need to be established separately. The site does not use affiliate tracking links.
Corrections
Send a correction to [email protected] with the relevant page, the statement in question, and a current official reference. Avoid sending private account information. A useful correction identifies the exact capability or requirement rather than assuming that an unrelated integration example resolves the issue.