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.
New to CPaaS?
Start here: five short reads
In this order, they cover what CPaaS is, how channels differ, and what you're actually choosing between. No jargon assumed.
- 1What CPaaS actually is, and what it is notThe category is defined more clearly by what it replaced than by any vendor's feature list. A working definition, what it is often confused with, and three questions that separate a real platform from a reseller.4 min
- 2Channels are not interchangeable: the most common early mistakeSMS, 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.4 min
- 3A2P, P2A, P2P: why the direction of a message decides everything about itThe same 160 characters are priced, routed, filtered and regulated differently depending on whether a person or a program pressed send — and on who wrote first.4 min
- 4The five layers of a communications stack, and which one you are actually shopping forMost evaluations compare transport — getting a message to a phone — which is the commodity layer. The four layers above it are where programmes succeed or fail, and where switching gets expensive.5 min
- 5Choosing a channel per message, not per programmeThe 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.5 min
Done? You're ready to Find providers →
Learn by theme
Seven tracks, each running from the basics to the advanced. Follow one as far as you need.
- CPaaS basicsWhat the category is, how a message actually travels, and which part of the stack you are really buying.4 pieces
- Channels 101One primer per channel: its history, how it works, where it is used, what it costs, the rules, its limits and when to choose it, with every claim sourced.17 pieces
- Channels in depthSMS, WhatsApp, RCS and the rest: what each is good at, the rules each comes with, and how to pick per message.8 pieces
- Voice and videoCalls and video inside your product: how real-time media works, what latency feels like, and when video is worth it.4 pieces
- Consent, compliance and trustOpt-in, sender registration around the world, AI disclosure and data handling — the rules that decide whether a message arrives at all.8 pieces
- Conversations, journeys and AIOne customer across many channels: journeys that branch, support as a system, automation and AI agents that actually resolve things.6 pieces
- Choosing and buyingHow to choose a provider, when to build instead, and how to read a contract before you sign it.4 pieces
- Markets and numbersThe state of the market, how to read a forecast without being misled, and what changes from one region to the next.6 pieces
The library
Apple Messages for Business 101: service chats inside the Messages app
How people on Apple devices message a business from the Messages app, what list pickers, time pickers and Apple Pay add, why a provider and Apple's review are required, and how it differs from RCS on the iPhone.
Video 101: calls and meetings as a business channel
How live video reaches customers through a link or inside your own site and app, where businesses use it from support to telehealth and video identity checks, what it costs, and the rules for recording.
Web chat & booking page 101: help where visitors decide
Web chat is a conversation window on your own website, answered by people, a bot, an AI agent or a mix; a booking page lets visitors pick a time without a phone call. Both meet people at the moment they decide, and both come with duties: telling people when a bot answers, accessibility, cookie consent and keeping transcripts no longer than needed.
In-app chat 101: conversations inside your own product
In-app chat puts messaging inside your own mobile or web app through an SDK: support chat between customers and your team, and chat between your users in marketplaces and communities. You keep the context, the design and the data, and you also take on what platforms usually carry for you: moderation, safety and data rules.
Push notifications 101: alerts people allowed
Push notifications are short alerts from your own app or website, carried by the platforms' notification services (Apple's APNs, Google's FCM, Huawei's Push Kit and the browsers' push services). Sending is free or nearly free; the real price is permission, which people can refuse or withdraw at any time.
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.
LINE 101: official accounts people add as friends
How LINE Official Accounts, the Messaging API, LINE notification messages and MINI Apps work, how LY Corporation prices them in Japan, Thailand and Taiwan, and when LINE is worth adding.
Viber 101: branded messages where Viber is the everyday app
How Viber Business Messages, chatbots and business accounts work, how Rakuten Viber prices them, and which markets make Viber worth adding.
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.
Instagram 101: direct messages for businesses people discover by sight
How businesses use Instagram direct messages in October 2026: professional accounts, the two ways to connect through Meta's API, the 24-hour window and the seven-day human agent rule, what it costs and when it is the right channel.
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.
WhatsApp 101: the Business app, the Business Platform and the rules between them
What WhatsApp offers businesses in October 2026: the free Business app for one team on one phone, the Business Platform for systems and scale, how the 24-hour window and templates work, what Meta charges since the October 2026 changes, and where the channel fits.
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.
RCS 101: the phone's own messaging app, with a brand name and buttons
What RCS business messaging is, how a rich message reaches a phone and falls back to SMS when it cannot, what it costs, the approval and consent rules, and when the upgrade is worth it.
SMS 101: the text message every phone can receive
What SMS is, how a business text travels to a phone, what it costs, the registration and consent rules by region, and when plain text is still the right choice.
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.
How to choose a CPaaS provider: a step-by-step guide for business buyers
Ten plain steps, from defining the job to planning your exit, with a checklist you can take into any sales conversation.
The state of business messaging, 2026
Four changes that landed between 2024 and 2026 (per-message WhatsApp billing, stricter sender registration, RCS on both major phone platforms, and AI disclosure) and what each one does to a programme built before them.
What CPaaS actually is, and what it is not
The category is defined more clearly by what it replaced than by any vendor's feature list. A working definition, what it is often confused with, and three questions that separate a real platform from a reseller.
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.
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.
The 24-hour window: the rule that breaks most first integrations
Why your WhatsApp test message worked and your production message did not: how the customer service window works, what it costs inside and outside, and how to design around it.
A2P, P2A, P2P: why the direction of a message decides everything about it
The same 160 characters are priced, routed, filtered and regulated differently depending on whether a person or a program pressed send — and on who wrote first.
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.
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.
How to read a market forecast without being misled by one
Three reputable firms size this market at figures that differ widely, yet agree on how fast it grows. Why both are true, and how to use a forecast for what it is actually good for.
What RCS changed, and what it did not
Apple's adoption in iOS 18 turned a long-stalled standard into something with reach, and 2026 brought new versions and cross-platform encryption. Reach is still not the same as a business case.
Delivery rate is not a result
It is the metric most often reported and the least often useful. What delivery actually means, what to measure instead, and how a simple holdout group tells you whether messages changed anything.
The five layers of a communications stack, and which one you are actually shopping for
Most evaluations compare transport — getting a message to a phone — which is the commodity layer. The four layers above it are where programmes succeed or fail, and where switching gets expensive.
Peer-to-peer video: what it removes, and what it does not
For small calls, a media server is optional. When it stops being optional — and what a hosted video service gives you in exchange for its price — is the whole decision.
Conversational marketing, minus the hype
A useful definition has to exclude something. This one — the customer's reply changes what happens next — excludes most of what gets sold under the name, and tells you how to staff and measure the rest.
WebRTC in plain terms
What the browser gives you for free, what it does not, the three acronyms you cannot avoid, and where the real costs and support load sit.
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.
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.
Federating systems without merging them
When several products serve genuinely different audiences, consolidation can destroy what made each one good. Published contracts can do the same job with less loss, at a real operational cost.
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.
What the analysts disagree about, and why it is the useful part
Three firms, three market sizes, one category. Reading the disagreement tells you more about your own decision than any single number does.
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.
RCS after iOS: what changed in the numbers, and what to distrust
Adoption figures for RCS are widely quoted and rarely defined. What can be said confidently, and what is being counted loosely.
Evaluating a CPaaS contract: the clauses that decide what you actually bought
Unit price is one of the least consequential numbers in the agreement. Nine provisions that matter more, and what a good answer to each looks like.
Regional messaging in the Gulf: why global platforms can underperform here
A regional case study: four structural features of Gulf markets that a globally designed product does not automatically inherit, and that can decide outcomes more than software quality does.
GSMA on RCS, encryption and the future of operator messaging
A guide to the GSMA's own primary material on where operator-run messaging is heading, the standards body's account rather than a vendor's summary of it, and how to read it.