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
Sender registration around the world: who you have to tell before you text
Why countries regulate who may send business messages, what you usually have to register, and how the rules differ across the US, Canada, Europe, India, Brazil, the Gulf, Singapore and Nigeria.
Choosing a channel per message, not per programme
The channel decision belongs at send time, driven by intent, region, consent and where the person actually reads — not to a procurement meeting eighteen months earlier.
10DLC registration without tears
US carriers now block unregistered business texts from ordinary ten-digit numbers. The process has two layers, takes longer than launch plans assume, and most rejections are avoidable.
Getting messages into the Gulf: sender IDs, licensed aggregators and the AD marker
Business messaging in the UAE and Saudi Arabia is a registration and licensing question before it is a technical one, and a global platform does not inherit local standing.
A WhatsApp template strategy that survives contact with production
Templates are approved in advance, billed by category and impossible to improvise. Design the set before you need it, not during an incident.
Measuring a conversational programme without fooling yourself
A method: choose one outcome, build a permanent holdout, instrument the funnel, and be honest about what the numbers cannot settle.
Containment is not resolution, and optimising the first destroys the second
A support agent can post excellent containment numbers while making customers angrier. The metric that separates the two is uncomfortable and worth adopting.
Telling people they are talking to a machine
Since 2 August 2026 this is a legal requirement in the EU, and similar rules exist elsewhere. It is also, independently, what makes automated support tolerable. One line, in the right place, does it.
When to build messaging infrastructure, and when not to
A layer-by-layer decision framework based on what actually breaks in production and who is accountable for it, rather than on a feature comparison.
Latency you can actually feel
For messages, the network is rarely the slow part: queues, carriers and handsets dominate, and most of it is chosen at purchase. For live calls, a few hundred milliseconds decides whether a conversation feels natural.
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.
Arabic-first is not translation
Using Arabic as the worked example: direction, numerals, names, SMS encoding and register. A localised product differs from a translated one within the first minute — and the same checks apply to any right-to-left or non-Latin-script audience.
Adding RCS to an SMS programme without running two programmes
Every RCS deployment is two deployments: the rich one and the SMS fallback. Designing the fallback first, checking capability at send time and measuring honestly keeps it from becoming a second programme.
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.