RCS (Rich Communication Services) upgrades the native messaging app on Android with your verified brand name, logo, images, carousels and tappable buttons. Talkloo lets you send RCS through the same API and dashboard as your SMS and WhatsApp traffic – and silently falls back to SMS for any handset that cannot receive RCS.
RCS Business Messaging (RBM) is the business version of Rich Communication Services, the successor to SMS built into Android Messages and, since 2024, supported on iPhone as well. Unlike SMS, an RCS message shows a verified sender name and logo, can include high-resolution images, carousels, suggested replies and action buttons, and reports read receipts. Talkloo provides RCS as a native channel: you send one message, Talkloo checks whether the handset supports RCS, delivers the rich version where it can and a plain SMS everywhere else.
Talkloo handles agent registration, brand verification, capability checks and fallback so your team only has to design the message.
Talkloo registers your RBM agent and manages brand verification so recipients see your name, logo and a verification badge instead of a short code.
Send image or video cards with titles, descriptions and up to four action buttons, or scrollable carousels of products, flights or appointments.
Every send starts with a capability lookup. RCS-capable devices get the rich message; everything else receives the SMS variant of the same template.
Replies and button taps land in the Talkloo unified inbox or your webhook, where a human agent, Flow Builder journey or AI agent can continue the conversation.
Verification takes days, not months, because Talkloo manages the carrier and Google RBM onboarding for you.
Provide legal entity details, logo and sample messages. Talkloo creates and submits your RBM agent for verification.
Build rich cards and carousels in the template editor; each template automatically gets an SMS fallback version.
Call POST /v1/messages with channel "rcs" or launch a campaign from the dashboard. Talkloo checks capability and routes accordingly.
Compare read rates and button taps between RCS and SMS recipients in the same report.
RCS uses the same messages endpoint as every Talkloo channel. Describe the rich card in JSON, supply the SMS fallback text, and the platform does the rest.
POST /v1/messages
{
"channel": "rcs",
"to": "+447700900123",
"content": {
"richCard": {
"title": "Your order has shipped",
"description": "Arriving Thursday. Tap to track.",
"media": "https://cdn.yourbrand.com/box.jpg",
"suggestions": [
{ "type": "openUrl", "text": "Track order", "url": "https://yourbrand.com/t/A-10432" },
{ "type": "reply", "text": "Change address" }
]
}
},
"fallback": { "channel": "sms", "text": "Your order A-10432 shipped. Track: https://yb.co/t/A10432" }
}Product launches and offers with hero imagery and a Buy button instead of a shortened link.
Shipment cards with tracking buttons and reschedule replies that post back to your system.
Confirm, reschedule or add-to-calendar with a tap; reminders go out on SMS if RCS is unavailable.
Boarding passes, gate changes and upgrade offers as rich cards.
Verified sender badge cuts phishing confusion for transaction alerts and fraud checks.
Suggested replies route customers into AI or live-agent conversations inside the messaging app.
The three mobile messaging channels Talkloo runs side by side. Most customers use all three with fallback rules.
| RCS | SMS | WhatsApp Business | |
|---|---|---|---|
| Reach | RCS-capable Android + iOS handsets, else SMS fallback | Every mobile phone | Users with WhatsApp installed |
| Sender identity | Verified name, logo, badge | Sender ID / number | Verified business name |
| Media | Images, video, carousels, buttons | Text only (160 chars) | Images, docs, buttons, lists |
| Opt-in rules | Consent required | Consent required | Opt-in + Meta template approval |
| Read receipts | Yes | No | Yes |
| Typical use | Promotions, notifications, support | OTP, alerts, universal reach | Conversational support, notifications |
SMS is a 160-character text channel with no branding or media. RCS is the next-generation messaging standard that adds verified sender identity, images, carousels, suggested replies, read receipts and typing indicators inside the same native messaging app. Talkloo sends RCS where the handset supports it and SMS everywhere else.
Apple added RCS support to iOS in 2024. Availability of RCS Business Messaging on iPhone depends on the carrier and region, which is why Talkloo performs a per-recipient capability check and falls back to SMS automatically.
No. RCS is a channel on your existing Talkloo account. Talkloo registers and verifies your RBM agent and bills RCS messages alongside SMS, WhatsApp and email on one invoice.
Talkloo detects that during the capability check and sends the SMS fallback text from the same template. You see one delivery report that shows which channel actually delivered.
Typically one to two weeks depending on the carrier and country. Talkloo prepares and submits the agent, brand assets and sample messages on your behalf.
Yes. RCS is available as a message node in Flow Builder, and suggested-reply taps can branch the journey just like keyword replies on SMS or button taps on WhatsApp.
Talkloo handles verification, capability checks and fallback. You get richer messages and better read rates on day one.