Frequently Asked Questions

Rich Communication Services (RCS) is a communication protocol that upgrades traditional SMS messaging with enhanced features. Unlike SMS, which is limited to 160 characters of text, RCS supports rich media sharing, read receipts, typing indicators, group chats, and business messaging features. RCS messages can be sent over Wi-Fi or mobile data, not just cellular networks, and offer a much more interactive experience similar to modern messaging apps.

RCS is supported on Android devices through apps like Google Messages and Samsung Messages. Most major carriers worldwide now support RCS, including AT&T, T-Mobile, Verizon in the US, and numerous international carriers.

Apple has announced it will begin supporting RCS in iOS in 2024, which will significantly expand the protocol's reach. Until then, messages between Android and iOS devices default to SMS/MMS.

To check if your device and carrier support RCS, open your messaging app settings and look for "Chat features" or "RCS messaging" options.

Key features of RCS include:

• High-resolution photo and video sharing (up to 105MB)
• Read receipts and typing indicators
• Enhanced group chat functionality
• Rich business messaging with verified sender information
• Interactive elements like buttons and suggested replies
• Location sharing
• Messaging over Wi-Fi or mobile data
• End-to-end encryption (in implementations like Google Messages)

For a detailed breakdown of features, visit our Features page.

In most cases, you don't need to download a separate app to use RCS. Many Android phones come with RCS-compatible messaging apps pre-installed, such as Google Messages or Samsung Messages.

If your device doesn't have an RCS-compatible messaging app, you can download Google Messages from the Play Store. Once installed, you'll need to set it as your default messaging app and enable chat features in the settings.

For iPhone users, RCS support is expected to be added to the Messages app in iOS 18 in 2024. Until then, iPhone users cannot send or receive RCS messages.

RCS security depends on the implementation. Google's implementation of RCS in its Messages app includes end-to-end encryption for one-on-one conversations, providing a high level of security and privacy. This means that only the sender and recipient can read the messages, and they can't be intercepted or read by third parties, including Google or carriers.

However, not all RCS implementations include end-to-end encryption, and group chats currently don't have this level of protection in most implementations. The GSMA's Universal Profile specifications don't mandate encryption, making it an optional feature for carriers and messaging apps.

Compared to SMS, which has no encryption for message content, RCS is generally more secure, especially when using implementations with end-to-end encryption.

Businesses can leverage RCS Business Messaging (RBM) to create rich, interactive customer experiences. Key business applications include:

• Customer service with interactive menus and rich media support
• Marketing campaigns with product carousels and call-to-action buttons
• Transactional messages with order confirmations and tracking information
• Appointment scheduling with calendar integration
• Interactive surveys and feedback collection

Businesses can implement RCS through direct integration with platforms like Google's Jibe, through RBM solution providers, or via CPaaS providers that offer RCS as part of their omnichannel messaging solutions.

For detailed information on business implementation, visit our RCS for Business page.

When you send an RCS message to someone who doesn't have RCS capabilities (either due to device, carrier, or app limitations), the message automatically falls back to SMS or MMS format. This ensures that your message still reaches the recipient, albeit without the rich features of RCS.

You'll typically see a different indicator in your messaging app for messages sent as SMS/MMS versus those sent as RCS. For example, in Google Messages, RCS messages appear in blue bubbles with "Chat message" status, while SMS messages appear in light blue or green bubbles with "SMS" or "Text message" status.

This fallback mechanism ensures backward compatibility with the entire mobile ecosystem during the transition period to widespread RCS adoption.

RCS messages are sent over your mobile data connection or Wi-Fi, not through the traditional SMS network. This means:

• RCS messages don't count against your SMS/text messaging allowance on your cellular plan
• RCS messages do use a small amount of mobile data when sent over cellular networks (similar to other messaging apps)
• When connected to Wi-Fi, RCS messages use your Wi-Fi data and don't impact your mobile data allowance

The amount of data used by RCS messaging depends on the content being shared. Text-only messages use very little data, while sharing high-resolution photos or videos will use more data, comparable to other messaging apps like WhatsApp or Telegram.

Yes, RCS messages can be backed up, but the backup capabilities depend on the messaging app you're using:

• Google Messages: RCS messages can be backed up to Google's servers with end-to-end encryption. You can restore these messages when setting up a new device.
• Samsung Messages: RCS messages can be backed up through Samsung Cloud or Smart Switch when transferring to a new Samsung device.
• Other messaging apps: Backup capabilities vary by app and implementation.

When messages are encrypted end-to-end, the backup process typically preserves this encryption to maintain message security.

The costs for implementing RCS Business Messaging typically include:

• Setup fees: One-time costs for agent registration and brand verification
• Per-message fees: Charges for each RCS message sent, which are typically higher than SMS due to the enhanced capabilities
• Platform fees: Monthly or annual fees for using an RBM platform or partner service
• Integration costs: Technical resources required to implement the RCS API

Pricing structures vary widely depending on the provider, message volume, geographic reach, and level of service. Generally, businesses can expect to pay more per message than standard SMS, but the enhanced engagement and conversion rates often justify the higher cost.

Many RBM partners offer tiered pricing plans based on volume, with costs decreasing as message volume increases.

While RCS is designed to be the successor to SMS, a complete replacement is likely to take many years due to several factors:

• The global ubiquity of SMS and its infrastructure
• The gradual nature of technology transitions in the telecom industry
• The need for backward compatibility during the transition period
• Varying rates of RCS adoption across different regions and carriers

In the near to medium term, RCS and SMS will coexist, with RCS being used when available and SMS serving as a fallback. The addition of RCS support to iOS devices in 2024 marks a significant milestone that will accelerate adoption, but SMS will likely remain as a basic fallback option for many years to come, particularly for simple notifications and in regions with slower technology adoption.

Yes, RCS is designed to work internationally between compatible devices and carriers. The GSMA's Universal Profile provides a global standard for RCS implementation, enabling cross-border and cross-carrier compatibility.

When traveling internationally:

• RCS will work when connected to mobile data or Wi-Fi
• No additional roaming charges apply specifically for RCS (beyond standard data roaming fees)
• If RCS is unavailable due to network limitations, messages will fall back to SMS

The international availability of RCS depends on local carrier support. The protocol is widely supported in North America, Europe, and parts of Asia, with growing adoption in other regions.