Platform
Every channel, without building anything new.
Arrivo handles the hard part of every send —the channel, the provider, the backup and the follow-up— so your team can focus on its own work.
One integration
Connect once. Everything else plugs in.
Your system keeps sending the way it does today, over SMPP or API. From there, every new channel and provider is added on Arrivo’s side, without touching your code.
Arrivo Smart- SMS
- RCS
- + whatever comes next
Translation between channels
Every channel speaks its own language. Arrivo translates.
WhatsApp requires approved templates and the recipient’s permission. SMS has a character limit and, in some countries, the sender must be registered. RCS requires a verified brand. We tell you what applies in each case, and Arrivo converts your message to the format each one demands.
Your access code is 4821
-
WhatsApp
approved template · with the recipient’s consent
4821 is your verification code.
Copy code -
SMS
1 part · 24 characters · registered sender
Your access code is 4821
-
RCS
Your brand ✓verified brand · buttons and images
Your access code is 4821
Copy code
- WhatsAppApproved templates and delivery statuses.
- SMSLocal and international; long texts in multiple parts.
- RCSBranded messages with buttons and images.
- EmailTransactional notices and confirmations.
New ones join without changing your integration.
Before it goes out
Every message is checked before it’s sent.
Arrivo checks who it’s for, whether that phone can receive it and whether it follows the rules you set. That’s how you avoid lost sends, fraud and billing surprises.
- Phone availableactive on the network
- Operator identifiedOperator A · even if the number was ported
- Channels it receivesWhatsApp · SMS
- Meets your policiessender · content · volume
- Within your balanceprepaid or credit limit
ready to send →
About the recipient
- Is it available?Know whether the phone is active before sending.
- Which operator is it on?Even if the number was ported.
- Which channels does it take?Whether that phone has WhatsApp or RCS, so the channel is chosen before trying.
About your operation
- Policies per customerSender, content and volume rules you configure for each account. Verification codes don’t allow advertising.
- Your brand, protectedReserve your brand name as a sender.
- No floodingCap repeated sends to the same number.
- No billing surprisesPrepaid balance or credit limit, with suspension for non-payment.
- Only from your serversYour connection only accepts traffic from your IP addresses.
Control
You set the order.
Decide which channel and provider go first for each message type and country, and change it when the market moves. Every adjustment is saved, so you always know what was applied.
If one option fails, the next one takes over on its own.
What happened at exit 1?
- 1WhatsAppProvider 1primary
- 2WhatsAppProvider 2backup · same channel
- 3SMSProvider 3next channel
- 4SMSProvider 4backup
A provider problem says nothing about the recipient. The next provider in the plan is tried — on the same channel.
Visibility
Every message, start to finish.
See whether it arrived, which way it went and how many attempts it took. Reports are grouped by country and operator, and exported to your systems.
One message, step by step
- Provider
- Provider 3
- Route
- option 3 of 4 in the plan · SMS
- Attempts
- 3
- Delivery path
- WhatsApp (prov. 1) → WhatsApp (prov. 2) → SMS (prov. 3)
- Operator confirmation
- received
- Delivery status
- delivered
- Delivered channel
- SMS
- End to end
- 4 seconds
Latin America
A country is not a route.
One country has several operators, and each may be best reached through a different provider. Arrivo identifies each number’s operator from its numbering range and applies the matching rule.
| COUNTRY | CODE (MCC) | OPERATOR | PROVIDER | STEP |
|---|---|---|---|---|
| Mexico | 334 | Operator A | Provider 1 | step 1 · primary |
| Mexico | 334 | Operator A | Provider 4 | step 2 · backup |
| Mexico | 334 | Operator B | Provider 2 | step 1 · primary |
| Colombia | 732 | Operator C | Provider 2 | step 1 · primary |
| Argentina | 722 | Operator D | Provider 3 | step 1 · 60% |
| Argentina | 722 | Operator D | Provider 5 | step 1 · 40% |
Illustrative structure. Markets shown do not represent a coverage claim.
234countries with their numbering ranges loaded.
The MCC is the public code that identifies each country on mobile networks (ITU-T E.212); operators and providers are examples.
For your tech team
The details, for whoever integrates.
What your IT team will ask, in one place.
Connection
- SMPP 3.4
- encrypted connection (TLS)
- REST API
- batch sending
- access only from your IPs
Notifications and records
- signed webhooks
- delivery receipts (DLR)
- per-message records (CDR)
- event export
Testing and security
- test environment (sandbox)
- per-account key
- revocable keys
Shall we look at your traffic?
Bring a real case —one message type and one country— and we’ll build it together on the call.