Straight answers to what buyers actually ask us — how A2P messaging is priced, which channel to use when, what delivery rates are realistic, and what it takes to go live. No sales copy. For definitions rather than buying advice, see the glossary.
A2P stands for application-to-person: a message sent to a customer by software rather than typed by a human. Order confirmations, delivery alerts, appointment reminders, one-time passcodes and marketing campaigns are all A2P. It travels over the same networks as ordinary texts but is sent through a provider's API.
More detail: what A2P messaging is, and its four categories. The opposite is P2P (person-to-person) messaging. The distinction matters commercially, because mobile operators price and filter the two differently, and because most countries apply separate registration rules to A2P traffic.
A CPaaS — Communications Platform as a Service — is a provider that gives you one API for sending messages, and handles the connections to mobile operators and channel owners behind it. Instead of negotiating separately with hundreds of networks and with Meta, Viber and Telegram, you integrate once.
More detail: what a CPaaS actually sells, and how it differs from UCaaS and CCaaS. What you are really buying is the routing and the relationships: direct operator agreements, sender-ID registration, template approval, delivery receipts and compliance with each market's rules. Ritorica maintains over 500 direct connections to mobile operators for exactly this reason.
Ritorica is a business communication platform that delivers SMS, WhatsApp, Viber, Telegram, push and email messages through a single API. It has operated for over 20 years, delivered more than 12 billion messages in 2025, and serves banking, insurance, retail, transport, tourism and entertainment customers from offices in Cyprus, the UAE and Bangladesh.
Ritorica is a GSMA member and a listed Viber partner, runs 500+ direct operator connections, and employs 150+ in-house specialists in messaging protocols such as SMPP. See About Ritorica.
Use SMS when the message must arrive no matter what: it reaches every mobile phone, needs no app and no internet connection. Use WhatsApp when the message benefits from rich formatting, images, buttons or a two-way conversation, and when you know your customer uses it. Most businesses need both.
| SMS | WhatsApp Business API | |
|---|---|---|
| Reach | Every mobile phone | Only users with the app installed |
| Needs internet | No | Yes |
| Message length | 160 characters per segment | Long-form, with media |
| Rich content | Text only | Images, documents, buttons, lists |
| Two-way | Limited | Yes, full conversation |
| Pre-approval | Sender ID registration | Template approval by Meta |
| Typical use | OTP, alerts, universal fallback | Support, rich notifications, marketing |
Side by side on reach, cost and pre-approval: SMS vs WhatsApp for business. The practical answer for most teams is not to choose. See cascaded messaging — try the cheaper rich channel first, fall back to SMS only when it fails.
Cascaded messaging sends one message through several channels in sequence until one delivers. You set the order — for example push, then Viber, then WhatsApp, then SMS — and a timeout for each step. If a channel does not confirm delivery in time, the next one is tried automatically. You pay only for the attempt that lands.
Because the cheapest suitable channel is tried first and SMS is used only as the last resort, cascading typically reduces messaging spend by up to 60% while pushing delivery close to 100%. Ritorica supports up to four channels per cascade with a single API call, and reports which channel finally delivered. See Cascaded Messaging.
Choose Viber or Telegram where they have real local penetration — Viber is dominant in parts of Eastern Europe, the Balkans, Greece and the Philippines; Telegram is strong across the Middle East, Central Asia and parts of Eastern Europe. In those markets they cost less than SMS and support richer content.
Both work best as the first step of a cascade rather than a standalone channel, because neither reaches customers who do not use the app. See Viber Business Messaging and Telegram Gateway.
Per message delivered, at a rate that depends on the destination country, the channel and the message category. There is no single global price: the cost of one SMS to Germany and one to Bangladesh can differ by an order of magnitude, because each mobile operator sets its own termination fee.
Three things change the number on your invoice:
Ritorica quotes per country and channel. Check coverage for your markets or ask for a quote.
It depends entirely on where it is going. Rates are set by the destination mobile operator, so the same message costs different amounts in different countries, and prices move as operators revise their termination fees. Any provider quoting one worldwide price is averaging — and you will pay for that average.
Ritorica publishes a per-country coverage directory covering 207 countries; contact sales for the rate card that matches your actual traffic mix.
Four levers, in order of impact: route through cheaper channels before SMS, keep messages inside one segment, clean invalid numbers before sending, and consolidate traffic with one provider to earn better rates. Cascading alone commonly cuts spend by up to 60%.
On a well-configured route with a registered sender ID and clean recipient data, expect 95% or better for SMS. Ritorica reports 95%+ coverage worldwide and a 99.9% delivery rate on OTP traffic, which is routed on dedicated paths. Rates below 90% almost always point at a configuration problem, not a network one.
The usual causes of a low rate are an unregistered sender ID, a message category that the destination market filters, or a recipient list that has not been validated.
Most often the message was filtered, not lost. Operators block unregistered sender IDs, traffic that looks like spam, and marketing content in markets that only permit transactional messages. The rest is accounted for by switched-off handsets, invalid numbers and ported numbers on stale routing data.
Delivery receipts tell you which case you are in. Ritorica returns per-message status with timestamps, so a failure can be traced to a specific operator and reason rather than guessed at.
Under five seconds, and ideally under three. An OTP sits at the most fragile point of a signup or checkout flow: every extra second of waiting increases abandonment. Ritorica delivers most one-time passcodes in under three seconds at a 99.9% delivery rate, with capacity for 10,000 OTPs per second.
Speed comes from routing rather than luck. Dedicated OTP routes bypass the queues that bulk marketing traffic sits in, and automatic fallback moves the code to another channel the moment one path is slow. See Verify OTP.
An OTP is a single-use code. 2FA is the security design that asks for a second proof of identity in addition to a password. An OTP is one way to deliver that second factor — the most common one — but 2FA can equally use an authenticator app, a hardware key or biometrics.
Put simply: 2FA is the requirement, OTP is a mechanism that satisfies it. More on what counts as a factor and what makes a good OTP implementation.
207 countries and territories, across SMS, Viber, WhatsApp and Telegram, through direct operator connections. Channel availability varies by market — not every channel is present everywhere — so the coverage directory lists which channels are live for each individual country.
Look up a specific market in the worldwide coverage directory.
A sender ID is the name or number a recipient sees as the sender — for example your brand name instead of a phone number. In most countries it must be registered with the operators before traffic will pass, and in a growing number of markets unregistered traffic is blocked or silently discarded.
The four types, and what happens if you skip registration: sender IDs explained — and for US traffic, 10DLC. Registration requires documentation about your company and your intended message content, and takes from a few days to several weeks depending on the country. It is the single most common cause of a delayed launch, so start it first. Ritorica handles the filings as part of onboarding.
Because WhatsApp only lets a business start a conversation using content Meta has reviewed. Any message you send outside a 24-hour window opened by the customer must use a pre-approved template. It is Meta's protection against the channel filling with unsolicited marketing.
Approval usually takes minutes to hours. Rejections are nearly always caused by promotional language in a template submitted as transactional, placeholder variables with no example values, or missing opt-out wording. Our WhatsApp integration guide covers what gets approved on the first attempt.
For marketing, yes — nearly everywhere, and the record of that consent must be produced on demand. Transactional messages the customer has asked for, such as an order confirmation or a one-time passcode, generally do not require separate marketing consent. The rules are set per country, not per provider.
Every message must also carry a working opt-out, and opt-outs must be honoured across channels rather than per campaign. Ritorica applies channel-specific opt-out rules and sender-ID requirements automatically, but the lawful basis for your contact list remains yours.
Message content is processed to deliver it and to produce the delivery reports you see, under your service agreement with Ritorica. Ritorica operates as a licensed personal data operator with enterprise-grade security controls. Handling of message data is governed by that agreement, not by the website's privacy policy.
The privacy policy covers a separate question — what ritorica.com collects from visitors to this website.
Through a single REST API. One authenticated HTTP request sends a message on any channel, and a webhook you host receives the delivery receipts. High-volume senders can connect over SMPP instead. The same call drives a cascade, so adding channels later needs no new integration.
Start with the API documentation and the integration guides.
Use the HTTP API unless you have a specific reason not to: it is faster to build against, works from any language, and is enough for the overwhelming majority of traffic. Choose SMPP for sustained very high throughput, where a persistent binary connection avoids the overhead of one HTTP request per message.
The full comparison: SMPP vs HTTP API. SMPP costs more engineering time — you manage the session, binds, window size and reconnection yourself. Most teams start on HTTP and only move if their volume justifies it.
Technical integration is typically a matter of days. The schedule is set by sender ID registration and, for WhatsApp, template approval — these run in parallel with development and can take from a few days to several weeks depending on the country.
Onboarding runs in five steps: contract, sender ID registration, message template setup, technical integration, then testing before live traffic. Beginning the registration paperwork on day one is what shortens the overall timeline.
All four are CPaaS providers with overlapping channel coverage. Ritorica differentiates on cost-optimised cascaded routing, direct operator connections rather than resold routes, and hands-on onboarding — 150+ in-house specialists and 24/7 support rather than self-service only. It is the better fit for teams that want routing and registration handled for them.
The honest guidance: if you want a pure self-service developer platform with the largest product catalogue, the very large US-listed providers are strong. If your priority is delivery rate and cost per delivered message in EMEA, Asia and the Gulf — with a team that will configure the routing with you — that is where Ritorica competes. Ask us for a per-country comparison against your current provider's rates.
Tell us which countries and channels you need, and we will come back with coverage, rates and a delivery estimate for your traffic.
Request a demo