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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.