A2P Network
a2p.networkVerifiedOur productFeatured
One API and one console for every business messaging channel, with scoped keys, quotas, health and signed callbacks.
- SMS
- Telegram
The CPaaS Company
Understand cloud communications before you buy them
Research, explainers and field-tested use cases on CPaaS, omnichannel engagement and conversational marketing — written to be useful whether or not you ever become a customer.
Insights
Latest thinking
The state of business messaging, 2026
Four changes that landed between 2025 and 2026 — per-message billing, mandatory registration, RCS on every modern handset, 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, and the three questions that separate a real platform from a reseller.
Channels are not interchangeable, and treating them as if they are is the most common early mistake
SMS, WhatsApp, RCS and email differ in who may start a conversation, what may be said, and what happens when the recipient ignores it. Those differences are not cosmetic.
The 24-hour window: the rule that breaks most first integrations
Why your test message worked and your production message did not, explained without reference to any particular vendor's documentation.
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.
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.
Filed under
Start anywhere
Every topic runs from a foundation piece to an advanced one. Pick a subject and the reading order is already built.
The CPaaS Company
Why this exists
Most writing about this category is produced to sell something. This is too, in the sense that we build products here — so the arrangement is stated openly.
Publishing a buyer's guide while selling to buyers is a conflict. Pretending otherwise would be worse than the conflict itself, so here is the arrangement:
Our products are labelled as ours, everywhere they appear, including in the directory alongside competitors.
The directory applies one standard. Our own products are assessed against the same six published criteria as everyone else, and one of them currently sits under review rather than verified — for a reason stated on its card.
Editorial content does not recommend our products. Where a piece describes a capability we happen to sell, it describes the capability.
Sources are linked, not summarised away. If a claim here matters to a decision you are making, you should be able to check it without taking our word for anything.
Corrections are made in place, and noted.
Ecosystem
The directory
Every provider we cover, assessed against the same six published criteria — ours included, and labelled as ours.
Omnichannel Systems
omnichannel.systemsVerifiedOur product
Inbound conversations become tickets and appointments, routed by rules and measured against service-level targets.
- Telegram
Unified CX
unified.cxVerifiedOur product
A visual journey engine over twelve channel adapters, with a contact graph that tracks lifecycle, consent and engagement.
- Telegram
iCall
icall.telVerifiedOur product
Self-hostable video meetings with three interchangeable backends, including a path that needs no video vendor at all.
- WebRTC video
- LiveKit
- GetStream
Rasayel
rasayel.netUnder reviewOur product
Arabic-first messaging for small businesses that will never read an API document.
Twilio
twilio.comListed
The category's reference implementation: programmable messaging, voice and video with broad carrier reach.
- SMS
- Voice