# RCS Business Messaging with verified branded senders - Canonical URL: https://www.broadnet.me/products/rcs-messaging - Language: en - Last updated: 2026-10-20 - Publisher: BroadNet (https://www.broadnet.me) - Markdown version of the page above, generated from the rendered page. RCS Business Messaging · Google RBM partner SMS, upgraded, with your brand verified. 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. [Verify my brand for RCS](https://www.broadnet.me/contact?topic=rcs-verification&product=rcs-messaging) [Check RCS country availability](https://www.broadnet.me/contact?topic=rcs-availability&product=rcs-messaging) Official Google RCS Verified Sender RBM Partner · Agent ID provisioned ![The BroadNet snow leopard beside rich branded message cards with images and buttons](https://www.broadnet.me/marketing/generated/viz-rcs.png) BroadNet · rich messaging POST /rcs/message/sendbulk 1,000+ Operator connections 200+ Countries 99.99% SLA 01 / 04 Verified Branded sender Business name, logo and verification tick on every message 02 / 04 Read Receipts from the handset Sent, delivered and read, with a webhook on every transition 03 / 04 Replies Suggested replies & actions Reply chips plus dial, link and location actions 04 / 04 Fallback Automatic SMS Handsets without RCS receive the message as SMS From submit to verified card ## Your verified agent, on the handset, branded and verified. 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. 1. 01 · Compose POST /rcs/message/sendbulk 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. gateway send 2. 02 · Edge Capability check MSISDN lookup against the RCS capability cache. If the handset can't render RCS, message auto-falls back to SMS on the same submit. capability check 3. 03 · Hub Google RCS hub Direct bind to Google's Jibe platform with verified-agent credentials. Brand logo and badge present from the first render. Jibe bind 4. 04 · Carrier MNO RCS Operator-side RCS messaging stack delivers to the handset's Messages app. Read receipt, typing indicator, suggested-reply tap all flow back. carrier RCS 5. 05 · Signals Engagement events Delivered, read, replied, button tap — each as a webhook to your endpoint. Same event schema as SMS DLR plus rich-event fields. webhook 6. ← read · reply · tap · webhook 01 · Compose POST /rcs/message/sendbulk 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. gateway send 02 · Edge Capability check MSISDN lookup against the RCS capability cache. If the handset can't render RCS, message auto-falls back to SMS on the same submit. capability check 03 · Hub Google RCS hub Direct bind to Google's Jibe platform with verified-agent credentials. Brand logo and badge present from the first render. Jibe bind 04 · Carrier MNO RCS Operator-side RCS messaging stack delivers to the handset's Messages app. Read receipt, typing indicator, suggested-reply tap all flow back. carrier RCS 05 · Signals Engagement events Delivered, read, replied, button tap — each as a webhook to your endpoint. Same event schema as SMS DLR plus rich-event fields. webhook Developers ## Send your first RCS message in one request. 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. - Bearer-token auth · POST /rcs/message/sendbulk - Multipart form: destinationNo, messageType, content - Same account and Bearer token as SMS and WhatsApp [Build a live request](https://www.broadnet.me/tools/api-request-builder) POST · api.broadnet.me/rcs/message/sendbulk Example ``` 1# Send an RCS message (non-RCS handsets fall back to SMS)2curl -X POST https://api.broadnet.me/rcs/message/sendbulk \3 -H "Authorization: Bearer $BROADNET_TOKEN" \4 -F messageType=TEXT \5 -F destinationNo=+447700900123 \6 -F content="Your order has shipped. Track it in the app." ``` Capabilities ## Everything the standard supports — provisioned, routed and observable. 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. ### Verified branded sender 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. - Google-managed verification - Logo, brand colour, description - Verified blue tick on every send ### Rich cards & carousels 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. - Single card or 10-card carousel - Image, title, description, 4 actions - Tall or short card layouts ### Suggested replies Quick-reply chips beneath the message — up to eleven per send. Customers tap instead of typing. Replies route straight back through the API. - Up to 11 reply chips - Dial, open URL, view location actions - Conversational handoff to your bot ### Read receipts True delivery and read signals from the handset — not gateway approximations. Power journeys that wait for the customer to actually see the message. - Sent · Delivered · Read - Webhook on every transition - Per-recipient timestamps ### Typing indicators 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. - Outbound typing events - Inbound typing webhooks - Auto-clear on send ### Logo display 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. - 224×224 colour logo - Light & dark mode variants - Notification icon support RCS vs SMS ## Why RCS, where it's available. 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. SMS fallback automatic on unsupported handsets Dimension RCS via BroadNet SMS Brand, not a number Verified business name, logo, colour and blue tick render in the conversation list. 11-character alphanumeric sender — no logo, no verification signal. Inline rich media Image banners, carousels, action chips and maps render in the thread. 160-character plain text. Media requires an external link. True delivery telemetry Handset-level sent, delivered and read receipts via webhook. Gateway-level DLR only. Read state is unknowable. Suggested replies Tap-to-reply chips drive 4–6× the response rate of SMS in our routes. Free-text response. Higher friction, lower completion. Coverage ## Live in 12 markets — and expanding. Verified sender provisioning through Google RBM in each market below. New markets onboarded on request — typical lead time four to six weeks. [Request a new market](https://www.broadnet.me/contact?topic=rcs-availability&product=rcs-messaging) ![United Arab Emirates](https://www.broadnet.me/assets/flags/ae.svg) United Arab Emirates Etisalat, du ![Saudi Arabia](https://www.broadnet.me/assets/flags/sa.svg) Saudi Arabia STC, Mobily, Zain ![Egypt](https://www.broadnet.me/assets/flags/eg.svg) Egypt Vodafone, Orange, Etisalat ![Jordan](https://www.broadnet.me/assets/flags/jo.svg) Jordan Zain, Orange, Umniah ![Qatar](https://www.broadnet.me/assets/flags/qa.svg) Qatar Ooredoo, Vodafone ![Oman](https://www.broadnet.me/assets/flags/om.svg) Oman Omantel, Ooredoo ![Kuwait](https://www.broadnet.me/assets/flags/kw.svg) Kuwait Zain, STC, Ooredoo ![Bahrain](https://www.broadnet.me/assets/flags/bh.svg) Bahrain Batelco, STC, Zain ![Turkey](https://www.broadnet.me/assets/flags/tr.svg) Turkey Turkcell, Vodafone, Türk Telekom ![United Kingdom](https://www.broadnet.me/assets/flags/gb.svg) United Kingdom EE, Vodafone, O2, Three ![Germany](https://www.broadnet.me/assets/flags/de.svg) Germany Deutsche Telekom, Vodafone, O2 ![India](https://www.broadnet.me/assets/flags/in.svg) India Jio, Airtel, Vi Customer stories ## What verified RCS does that plain SMS can't. Gulf real-estate developer Real estate · GCC AE **Challenge** A property-launch SMS flyer felt like a marketing blast and converted poorly into booked viewings. **Approach** An RCS carousel of available units, each with photos and a 'Book viewing' button, replaced the text-only push, with the verified brand identity rendered in conversation. Digital marketing lead (reference under NDA) Southern African retailer Retail · Southern Africa ZA **Challenge** An Android-dominant customer base had no easy two-way service path without forcing app installs. **Approach** Suggested replies routed common intents like 'Track my order' directly into the existing customer-service bot. Customer experience lead (reference under NDA) Southeast Asian ecommerce marketplace E-commerce · APAC ID PH **Challenge** A mixed Android and iOS base across several markets meant either building a routing layer or sending two messages. **Approach** Capability lookup at submit time picks RCS for Android and auto-falls back to SMS for iPhones using one API. Customer experience lead (reference under NDA) 1 API RCS + SMS 0 Routing code Carrier-grade scale · by the numbers ## The reach your RCS traffic inherits. 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. Reach 200+ countries Direct to the operator in 86 countries, labelled partner routes elsewhere. Network 1,000+ operator connections Direct operator interconnects wherever commercially available. Scale 300M+ messages a day Application-to-person traffic carried across the BroadNet network. Heritage 2003 operating since Two decades of carrier-grade messaging delivery. Google RBM Partner Audited brand & content review GDPR & UAE PDPL EU + GCC data residency on request ISO/IEC 27001 Information security management Per-market opt-in Local DNCR & STOP keyword handling Questions buyers ask ## RCS, answered honestly. 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](https://www.broadnet.me/contact) RCS sits alongside [A2P SMS messaging](https://www.broadnet.me/products/a2p-sms) in the BroadNet channel stack, with automatic fallback to [bulk SMS](https://www.broadnet.me/products/bulk-sms) and [the WhatsApp Business API](https://www.broadnet.me/products/whatsapp-business-api) where RCS isn't available. Comparing vendors? Read our [Best RCS provider](https://www.broadnet.me/compare/best-rcs-provider) buyer's guide. Carrier-grade delivery ## Delivered to 200+ countries, direct to the operator in 86. 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. 200+ Countries 1,000+ Operator connections 300M+ Msgs·day [Talk to sales](https://www.broadnet.me/contact) Verification: ~2–4 weeks ## Get your brand verified on Google RCS. We'll handle the agent registration, the brand kit submission and the carrier provisioning. You ship rich messages in weeks, not quarters. [Verify my brand for RCS](https://www.broadnet.me/contact?topic=rcs-verification&product=rcs-messaging) [Check RCS country availability](https://www.broadnet.me/contact?topic=rcs-availability&product=rcs-messaging) $ curl -X POST https://api.broadnet.me/rcs/message/sendbulk -H "Authorization: Bearer $BROADNET_TOKEN" -F messageType=TEXT -F destinationNo=447700900123 -F content=… [Full API reference /developers/api](https://www.broadnet.me/developers/api) Resources RCS Messaging datasheet [Download datasheet· PDF, 99 kB](https://www.broadnet.me/resources/datasheets/broadnet-rcs-messaging-datasheet.pdf) [Product datasheets](https://www.broadnet.me/resources) ## Related guides & answers Go deeper on the concepts behind this product. - [What is RCS Read](https://www.broadnet.me/answers/what-is-rcs) - [RCS vs SMS — compared Read](https://www.broadnet.me/answers/rcs-vs-sms) - [How does RCS Business Messaging work Read](https://www.broadnet.me/answers/rcs-business-messaging) - [RCS vs WhatsApp — compared Read](https://www.broadnet.me/answers/rcs-vs-whatsapp) - [What is RCS Business Messaging (RBM) Read](https://www.broadnet.me/answers/what-is-rcs-business-messaging) - [What is RCS MaaP (Messaging as a Platform) Read](https://www.broadnet.me/answers/what-is-rcs-maap)