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
Email 101: the open channel people keep
Email is the one business channel nobody owns: it runs on open standards, reaches more than four billion people and holds the records customers keep. Whether a message lands in the inbox depends on proving who sent it, keeping complaints low and respecting consent rules that differ by country.
WeChat 101: official accounts, mini programs and WeCom
How businesses use WeChat's Official Accounts, Mini Programs and WeCom, what verification costs, the messaging limits and Chinese data rules that come with them, and when WeChat is worth adding.
Voice 101: business phone calls, numbers and caller-ID trust
How a business phone call travels between the phone network and the internet, what numbers, SIP and IVR are, what calls cost, and the caller-ID and robocall rules that decide whether anyone answers.
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.
Consent is a data model, not a checkbox
A single yes/no field cannot answer the questions a regulator or a customer will ask — when, for what, on which channel, and how. A simple ledger can, and it keeps more customers reachable.
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.
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.
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.
The gap nobody fills: service-to-service identity
Messaging platforms issue credentials to people and to applications. Few can express 'system A is acting on behalf of customer B, with these permissions, until this moment'.
The real cost of an unofficial transport
Unofficial protocol implementations are cheaper, faster to launch and genuinely useful. They also transfer a risk to the business using them that should be priced and disclosed.
Article 50 for messaging teams: what the AI Act's transparency rules require
A reading of the transparency obligations that apply from 2 August 2026, focused on automated conversations rather than AI in general.