Rich Communication Services, delivered natively on Android through Google Messages. As a Google RBM Partner, BroadNet provisions your verified branded sender — the blue badge, rich-media carousels, interactive replies and read receipts — with automatic fallback to SMS on any handset that can't render RCS.
Direct bind to Google's Jibe RCS hub with verified-sender credentials. Capability lookup catches non-RCS handsets at the door and falls back to SMS without your app writing a single conditional.
Your rich card, suggested replies, image or carousel — submitted through the gateway send. The verified RCS sender and route are configured on your account, so the same submit reaches the branded agent.
MSISDN lookup against the RCS capability cache. If the handset can't render RCS, message auto-falls back to SMS on the same submit.
Direct bind to Google's Jibe platform with verified-agent credentials. Brand logo and badge present from the first render.
Operator-side RCS messaging stack delivers to the handset's Messages app. Read receipt, typing indicator, suggested-reply tap all flow back.
Delivered, read, replied, button tap — each as a webhook to your endpoint. Same event schema as SMS DLR plus rich-event fields.
Your rich card, suggested replies, image or carousel — submitted through the gateway send. The verified RCS sender and route are configured on your account, so the same submit reaches the branded agent.
MSISDN lookup against the RCS capability cache. If the handset can't render RCS, message auto-falls back to SMS on the same submit.
Direct bind to Google's Jibe platform with verified-agent credentials. Brand logo and badge present from the first render.
Operator-side RCS messaging stack delivers to the handset's Messages app. Read receipt, typing indicator, suggested-reply tap all flow back.
Delivered, read, replied, button tap — each as a webhook to your endpoint. Same event schema as SMS DLR plus rich-event fields.
One HTTPS call to POST /rcs/message/sendbulk — a Bearer token, a multipart form with destinationNo, messageType and content, and your verified RCS agent. Non-RCS handsets fall back to SMS on the same submit.
# Send an RCS message (non-RCS handsets fall back to SMS)curl -X POST https://api.broadnet.me/rcs/message/sendbulk \ -H "Authorization: Bearer $BROADNET_TOKEN" \ -F messageType=TEXT \ -F destinationNo=+447700900123 \ -F content="Your order has shipped. Track it in the app."RCS is not a feature flag on SMS. Each capability requires a verified agent, an accepted brand kit and a carrier-grade route. BroadNet handles all three.
Your business name, logo, accent colour and the blue verification tick — handled end to end through Google's RCS Business Messaging programme. Customers see a trusted brand, not a shortcode.
Inline product cards with image banner, title, description and up to four actions. Swipe carousels of up to ten cards — no app, no link redirect.
Quick-reply chips beneath the message — up to eleven per send. Customers tap instead of typing. Replies route straight back through the API.
True delivery and read signals from the handset — not gateway approximations. Power journeys that wait for the customer to actually see the message.
Show your customer that an agent is composing a reply, or trigger typing during a long bot generation so the conversation feels alive instead of stalled.
Your full-colour logo renders inside Google Messages — in the conversation list, header and notification. The single biggest trust uplift versus an SMS sender ID.
SMS still owns reach. But where the handset and the carrier agreement support it, RCS replaces a 160-character monologue with a branded, two-way surface.
Verified sender provisioning through Google RBM in each market below. New markets onboarded on request — typical lead time four to six weeks.
The same carrier-grade network that has powered Google, Meta and Uber since 2003 now carries your verified RCS — riding the identical operator interconnects as our A2P SMS, with automatic fallback built in.
Direct to the operator in 86 countries, labelled partner routes elsewhere.
Direct operator interconnects wherever commercially available.
Application-to-person traffic carried across the BroadNet network.
Two decades of carrier-grade messaging delivery.
Per market, with Google's review usually clearing in 3–10 business days once we submit. We handle the agent registration, brand-asset upload, and use-case attestation. UAE (Etisalat, du), KSA (STC, Mobily, Zain), and Egypt (Vodafone, Orange, Etisalat Misr) are the fastest; some markets take 2–3 weeks for the operator's side.
Capability lookup runs at submit time against our cache (refreshed every 6 hours from the operator). If the MSISDN can't render RCS — iPhone, older Android, or RCS disabled — the message auto-falls back to SMS on the same submit. You get one webhook with channel: "rcs" | "sms" telling you which leg ran.
Per message session, not per-message. A conversation that includes a card, a reply, and a button tap counts as one session — typically $0.018–0.025 in UAE/KSA, $0.012 in Egypt. The SMS fallback bills at the standard SMS rate for that market. No setup fee for the agent registration.
Yes — all standard RBM message types: text, image, video, audio, rich card (title, description, image, up to 4 buttons), carousel (2–10 cards), suggested replies (up to 11), and suggested actions (call, URL, calendar, location, view map, share location). All schemas validated server-side before submit.
UAE (Etisalat, du), KSA (STC, Mobily, Zain), Egypt (Vodafone, Orange, Etisalat Misr), Kuwait (Zain, Ooredoo, STC), Qatar (Ooredoo, Vodafone), Bahrain (Batelco, STC, Zain), Oman (Omantel, Ooredoo). Outside MENA: UK, US, Brazil, Mexico, France, Germany, Spain, Italy, India, Indonesia. New markets activated monthly.
Yes — every state transition (sent, delivered, read, replied, button tapped) fires as a webhook. Read receipts respect the user's privacy preference; if they've disabled them on the handset, you get delivered but never read. Typing indicators are inbound-only — the platform doesn't expose 'mark as typing' yet.
The platform carries a 99.99% uptime SLA. If the Jibe hub goes degraded, the capability cache flips to 'unknown' and every send falls back to SMS within 30 seconds — your campaign keeps shipping. We don't queue and wait. Postmortems for every sev-1 are published within 5 business days.
Yes — the Bulk SMS composer splits the audience and you choose RCS-rich vs SMS-only per variant. Delivery, open, click, and reply rates land in the same dashboard so you can compare apples-to-apples. Most customers see 2–3× engagement on the RCS variant in MENA markets.
Question not here? Ask our engineering team
RCS sits alongside A2P SMS messaging in the BroadNet channel stack, with automatic fallback to bulk SMS and the WhatsApp Business API where RCS isn't available.
Comparing vendors? Read our Best RCS provider buyer's guide.
No grey routes: a direct operator bind wherever one is commercially available, otherwise a labelled partner-managed route. One API to every channel, on a network built since 2003.
We'll handle the agent registration, the brand kit submission and the carrier provisioning. You ship rich messages in weeks, not quarters.
Resources
RCS Messaging datasheet
Go deeper on the concepts behind this product.