Learn · track
CPaaS basics
What the category is, how a message actually travels, and which part of the stack you are really buying.
- 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.
- CPaaS turns carrier contracts and telecom protocols into an API and a bill. Judge providers on what surrounds the message, not the unit price.
- Ask what happens when a message fails. A specific cause signals a real platform; a bare "failed" usually signals a reseller.
- Track accepted, delivered and acted on as three separate numbers. A platform can promise the first, partly the second, never the third.
- 2A2P, 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.
- Business messages sent by software are registered, filtered and priced differently from personal texts. Plan registration time for every country you send to.
- Give customers reasons to write first. Conversations they start face the fewest rules and the lowest costs on almost every channel.
- Check your sender type can receive replies, use a link domain you own, and treat big sends as a schedule, not an instant.
- 3The 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.
- Do not choose a provider on per-message price alone. Compare identity, orchestration, consent and measurement too — that is where programmes succeed or fail.
- Negotiate hardest for export rights on journeys and consent history; those layers are the hardest to leave.
- If you build, start with consent and keep transport behind a thin interface so you can switch routes later.
- 4Delivery rate is not a resultIt 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.
- Report outcomes per thousand messages sent — bookings, payments, replies — and use sent, not delivered, as the denominator.
- Use delivery rate as an alarm: alert on sudden drops, which usually mean a lapsed registration, a rejected template or a route change.
- Keep a small, random, permanent group who receive nothing. Comparing them with everyone else is the only honest measure of impact.