Learn · every claim sourced
Understand CPaaS, step by step
Plain-language guides, use cases and research from the community, with a source for every claim. New here? Begin with the five short reads below.
The library
Telegram 101: bots, channels and codes people opt into
How businesses use Telegram's bots, channels, Telegram Business and the Gateway verification service, what each costs, and where Telegram is worth adding.
Messenger 101: conversations that start on Facebook
How businesses use Messenger in October 2026: conversations with a Facebook Page, the 24-hour standard messaging window, what may be sent after it now that most message tags are retired, what it costs and where it fits.
Which channel for what: matching sixteen channels to your need, place and audience
All sixteen channels side by side: who can start a conversation, what the person needs, how rich each is, how it is priced and what must be approved first, then guidance by need, by region and by audience, and when not to use each one.
Channels are not interchangeable: the most common early mistake
SMS, WhatsApp, RCS and email differ in who may start a conversation, what may be said, what silence tells you and what a mistake costs. Those differences are not cosmetic.
Omnichannel is an identity problem, not a channel count
The difference between multichannel and omnichannel is not how many channels you support. It is whether the customer has to repeat themselves — and that depends on how you recognise one person across many addresses.
Designing a journey that actually branches
Most 'journeys' are sequences with a delay between steps. Four decisions, made before any copy is written, turn one into something that responds to what the customer actually does.
The support queue as a system, not an inbox
Ownership, state, two clocks, routing that survives staff changes, and the ways messaging channels break email-era ticketing — the machinery that separates a support function from a shared mailbox.
When video belongs in a support conversation, and when it is theatre
Video resolves a narrow class of problems dramatically faster and every other class slightly slower. Knowing which is which — and deciding recording and data flows up front — is the entire design.
A consent architecture that survives an audit and a vendor migration
A schema, a set of invariants, and the three queries every send path and every regulator eventually asks.