RCS (Rich Communication Services) is a carrier-backed messaging standard that runs inside the default texting app on a phone and replaces plain SMS with richer features: high-resolution images and video, read receipts, typing indicators, suggested replies, and verified business sender profiles. It falls back to SMS when the recipient or network does not support it, so a message still arrives either way.
The short version: RCS is what SMS would look like if it were designed today. It keeps the universal, phone-number-based reach of texting, but the payload is closer to what people expect from a chat app.
How does RCS differ from SMS?
SMS is old and deliberately simple. A single message is capped at 160 characters of GSM-7 text, there is no native concept of read state, and anything richer than text is handed off to MMS. If you want the longer version of how that works, see what does SMS mean.
RCS keeps the same addressing model (you still send to a phone number) but moves the transport to IP. That change is what unlocks the richer feature set. The practical differences:
| Capability | SMS | RCS |
|---|---|---|
| Addressing | Phone number | Phone number |
| Message length | 160 chars per segment | No practical hard limit |
| Rich media | Via MMS only | Native images, video, audio |
| Read receipts | No | Yes, on supported clients |
| Typing indicators | No | Yes |
| Suggested replies / buttons | No | Yes |
| Verified sender branding | No | Yes (RBM) |
| Transport | Carrier signalling | IP, with SMS fallback |
The fallback behaviour matters more than it sounds. Because RCS degrades to SMS, you do not have to choose one or the other at send time. The richer experience appears where it can, and a usable text appears everywhere else.
What is RCS Business Messaging (RBM)?
RCS Business Messaging is the business-facing side of the standard. Instead of a message arriving from an anonymous number, it arrives from a verified sender profile: a brand name, a logo, and a verification mark, with the brand's identity checked before the profile goes live.
That verification is the part worth paying attention to. SMS has no equivalent, which is part of why SMS phishing (smishing) works as well as it does. With RBM, the sender is a known, vetted entity, and the messaging app shows that to the recipient. Alongside branding, RBM supports the interactive pieces (suggested replies, action buttons, carousels) that turn a one-way alert into something closer to a conversation.
Is RCS encrypted?
It depends on the client. The messaging app many Android users have, Google Messages, applies end-to-end encryption to RCS conversations between users on that app. RCS as a standard does not mandate end-to-end encryption everywhere, and business (RBM) traffic is generally not end-to-end encrypted in the same way person-to-person chats are. So "RCS is encrypted" is true for some conversations on some clients, and it is worth being precise rather than treating it as a blanket guarantee.
Which phones and carriers support RCS?
On Android, RCS has been the default messaging experience for some time, supported across major carriers through Google Messages. The larger shift is on the Apple side: Apple added RCS support starting with iOS 18, so iPhones can now send and receive RCS messages rather than dropping to SMS for cross-platform texts.
Two honest caveats. First, support depends on the combination of device, operating system version, carrier, and the messaging app in use, so coverage is not uniform. Second, RCS between an iPhone and an Android phone is still RCS, not iMessage; the blue-bubble experience is separate. The takeaway for a business sender is that RCS reach is large and growing, but you should always assume SMS fallback is part of the delivery path.
When should a business use RCS?
The same places SMS already earns its keep, with a better experience where it lands:
- One-time passcodes and verification. A branded, verified sender reduces the ambiguity that makes SMS codes easy to spoof. If you are designing this flow, Bird Verifications handles the delivery and channel logic.
- Transactional notifications. Order confirmations, shipping updates, and appointment reminders can carry images, maps, and action buttons instead of a bare link.
- Conversational support. Typing indicators and suggested replies make a support thread feel like a real conversation rather than a relay of texts.
The recurring theme is trust and richness on a channel people already read. SMS open rates are high because the inbox is small and personal; RCS keeps that property and adds context.
FAQ
Is RCS the same as iMessage or WhatsApp?
No. iMessage is Apple's proprietary protocol; WhatsApp is a separate over-the-top app you install and that runs on its own account system. RCS is a carrier standard tied to your phone number and built into the default messaging app. WhatsApp offers similarly rich messaging and its own verified WhatsApp business profiles, but it reaches only people who use the app, whereas RCS aims for the universal reach of texting with SMS as the floor.
Do I need a separate number or app to receive RCS?
No. RCS uses your existing phone number and the default messaging app. If your device and network support it, RCS turns on within the app you already text from; if not, you receive the SMS fallback without doing anything.
What happens if the recipient does not support RCS?
The message is delivered as SMS (or MMS for media). This is built into how business RCS platforms route messages, so a send does not fail just because the recipient is on an older device or an unsupported network.
Where Bird fits
Bird treats RCS and SMS as one messaging surface: you describe the message and the recipient, and the platform sends RCS where it is supported and falls back to SMS where it is not. That keeps your code simple while giving recipients the richer, verified experience whenever their phone can show it.