RCS (Rich Communication Services) is a messaging channel that delivers branded, interactive experiences in your customers' native messaging app. When you send from a registered RCS sender, messages appear with your brand name, logo, and colors. Recipients do not need to download a separate app, but have access to an experience that is more interactive than SMS.
# In this article
# How RCS works in Iterable
With RCS, you can create rich layouts that stay in the native messaging thread:
- A card combines media, a title, a description, and buttons in one unit.
- A carousel presents two to 10 cards that recipients swipe through.
- Quick reply buttons send predefined text back to your sender so you can branch a journey without asking recipients to type a reply (reducing the risk of typos and increasing the likelihood of a successful reply).
To learn how to build these layouts, see Creating RCS Templates.
# RCS vs SMS
RCS is a separate channel from SMS and has several key differences that elevate the customer experience:
- Sender IDs: RCS uses a verified brand identity and an instantly recognizable sender profile with your brand name, logo, and colors.
- Content: RCS messages can include rich layouts and quick replies, while SMS is limited to text (SMS) or media (MMS).
- Engagement Metrics: RCS provides additional engagement data such as read receipts.
# RCS sender registration
When you set up RCS, you register an RCS sender. This sender is your brand identity and is used to send RCS messages. Each RCS sender is a distinct profile with an attached brand identity, logo, and colors. You can create multiple RCS senders to send messages to different audiences or for different sender use cases.
When your profile is ready, you submit an application for carrier approval for each destination country you will send to. After approval, you can start creating RCS templates, campaigns, and journeys.
To learn all about RCS sender registration, see RCS Sender Registration Overview.
# RCS subscription management
RCS message types use an opt-in subscription policy. Users must be subscribed to an RCS message type and have a phone number on their profile before you can send to them.
Iterable does not automatically handle STOP, HELP, or START keywords for RCS.
Use journeys to process inbound RCS Reply (rcsReceived) events, update
subscriptions, and send confirmation messages. See
Sending RCS from a Journey.
# RCS fallback
Iterable does not automatically send a fallback message when RCS delivery fails. Use a journey to send a message on another channel after a failed RCS send. See Sending fallback campaigns for users who cannot receive RCS.
# Supported countries
The following countries are supported for RCS:
- United States
- Brazil
- Canada
- Colombia
- France
- Germany
- Italy
- Mexico
- Spain
- United Kingdom
NOTE
You must create a separate sender for each country and use case that you want to submit for approval. A sender can be associated with only one country and a specific supported use case.
# Current feature limitations
The following Iterable features are not currently available for RCS:
- Campaign Alerts
- Channel Optimization
- Double Opt-In
- Experiments
- Frequency Management, including Ignore Frequency Cap
- Send Time Optimization
- Smart Opt-In
# Get started with RCS
Learn about RCS basic requirements and functionality before you start sending messages.
- Setting up RCS — Start sender registration, create RCS message types, configure subscriptions, and set up reply handling.
- Best Practices for RCS Compliance — Opt-in, HELP and STOP copy, and sending-time rules.
- Creating RCS Templates — Text, cards, carousels, and quick replies.
- Sending RCS Campaigns — Blast, triggered, and API sends.
- Sending RCS from a Journey — Tile events, fallback, and STOP/HELP replies.
- RCS Audience and Segmentation — Who can receive RCS and how to build event-based audiences.
# Terms to know
# RCS sender
Your verified brand identity for RCS. Recipients see your brand name, logo, and colors instead of a phone number.
# Destination
A country you submit for carrier approval on an RCS sender. External review starts when the destination status is Pending.
# Sender use case
The messaging purpose registered for a sender: Promotional, Transactional, or Multi-use. The sender use case shapes carrier approval and opt-out expectations. It does not restrict which Iterable message types you select on a template, but the sender use case should match the type of messages you plan to send.
# Test number
A phone number you add to a sender to verify that RCS messages deliver correctly before submission. Test numbers must be verified before you can use them. Add them while the sender is in Draft status; they become unavailable once the sender reaches Partially approved. See RCS Registration: Testing a sender.