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