Skip to main content
Rich Communication Services (RCS) is the next generation of text messaging. Unlike traditional SMS, RCS enables branded sender identification, rich media content (images, videos, GIFs), and interactive messaging features like quick replies, carousels, and suggested actions.
Example of an RCS message showing branded sender identity and rich media content

​
Key benefits

  • Branding and verified sending Messages display your brand’s logo, colors, and identity directly in the conversation, increasing recognition and trust. Verified sender status ensures your messages come from your legitimate business.
  • Advanced engagement analytics Track who has read a message and use this data for segmentation and Journey orchestration.
  • Rich content Enhance your messages with images, videos, cards, and interactive elements that drive engagement.

​
Requirements

For more background on RCS, see these blog posts:

​
Set up RCS

1

Apply for an RCS sender

See Applying for an RCS sender below.
2

Select an RCS-enabled sender when sending a message

OneSignal dashboard showing an RCS-enabled sender selected for a message
If a recipient’s device or carrier does not support RCS, the message automatically falls back to SMS.
3

Access read analytics

RCS analytics include read rate, RCS read rate, campaign stats, and audience activity. See RCS analytics for more detail.
RCS analytics showing read rate, delivery breakdown, and campaign stats
4

Use read events to branch Journeys or create segments

Use a message event filter to create a segment from RCS read receipts, or use a Wait Until node or Yes/No branch node in a Journey to control flow based on read receipts.
Journey editor showing a Wait Until node configured to wait for an RCS read event
5

View RCS read events on the user profile

Click into a user’s profile to see the RCS read receipts for that user.

​
Applying for an RCS sender

Applying for an RCS sender typically takes 8-12 weeks.
1

Prepare your application with your OneSignal account manager

This includes brand assets, contact information, expected sending countries, opt-in/out flows, and sample campaigns. Make sure your SMS operations adhere to the Registration Requirements.
2

OneSignal submits your application to Google and relevant carriers for approval

Applications are final once submitted. You must reapply to make changes.

​
Types of RCS messages

RCS messages are grouped into four types. The type determines how your messages are billed.
TypeAudienceDescription
RichUSText-only messages, or a title with body text. Cannot include actions or media. Messages longer than 160 characters are broken into segments and charged per segment.
Rich MediaUSMessages that include any actions (quick replies, dials, or links), a title with actions, a title with media, standalone media, or carousel content.
BasicInternationalText messages up to 160 UTF-8 characters. Does not include any actions, media, or carousels.
SingleInternationalText messages greater than 160 UTF-8 characters, up to the max message length of 3,072 characters. Can also include actions, media, or carousels.
For full billing details, see Usage & billing.

​
RCS analytics

RCS introduces new reporting data within SMS Message Reports:
  • Breakdown of RCS Delivered vs. SMS Delivered
  • Read Rate: Reads / Delivered
  • RCS Reads: The number of recipients that read an RCS message.
See SMS Message Reports for the full analytics overview.
Full RCS analytics dashboard showing delivery breakdown, read rate, and RCS reads

​
FAQ

​
How does RCS compliance differ from SMS?

RCS compliance follows the same rules as SMS. No additional compliance steps are required.

​
How many RCS senders should I apply for?

Apply for one sender per brand. A single sender can be used for both promotional and transactional messages, so customers receive all communications from a unified branded identity.

SMS Message Reports

View delivery, read rate, and engagement analytics for SMS and RCS messages.

Usage & billing

Understand how RCS message types affect your invoice.