SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

RCS Messaging Best Practices and FAQ

RCS Messaging is currently in Public Beta, so not all features and regions will be available during the initial launch. 

What is RCS?

RCS stands for Rich Communication Services, a protocol used for a better P2P messaging experience and richer A2P business messaging. RCS messages are delivered directly to the Messages app, where SMS is also delivered. Unlike WhatsApp or Facebook Messenger, a separate app is not required. You may see other providers mention A2P RCS as “RCS Business Messaging”, abbreviated to RBM, but it’s all the same channel and technology.

What phone numbers are compatible with RCS?
Unlike SMS where you send messages from a phone number, RCS Business Messaging (A2P RCS) uses a verified RCS Sender. While you don't send messages from a phone number, you can display one or more contact phone numbers in your RCS Sender's branded profile that consumers can see by tapping on the Sender's display name. This profile also can show your business description, emails, websites, privacy policy and terms of service.

The below article provides more information on Twilio’s RCS offering, Twilio’s RCS resources, and answer the common questions about the public beta release.

What is the benefit of using RCS?

For a full overview of what RCS is and what the benefits of using it compared to other messaging channels see What is RCS and the Benefits of Using RCS section of our blog post. 

What regions and carriers currently support RCS?

Support for RCS globally is expanding – please see our RCS Product Documentation for the latest status on what regions and countries are supported. 

What devices support RCS?

Android Devices - RCS is supported on most Android devices through the Google Messages app and by most major mobile carriers. This means most Android users can access these enhanced messaging features.

iOS Devices - As of iOS 18, Apple supports RCS. However, support can vary based on country and carrier. Here are key points to remember:

  • RCS between people (P2P) is different from RCS Business Messages (A2P). Just because your device can send RCS messages to others doesn’t mean it will receive RCS Business Messages.
  • Device support also depends on both Apple and your mobile carrier.

How to Check RCS Business Message Support on iOS

rcs_ios_settings.png

To see if your iPhone can receive RCS Business Messages:

  • Open the Settings app.
  • Navigate to Apps > Messages > RCS Messaging.
  • Ensure the option for RCS Business Messages is visible and toggled on.

If you do not see the menu for RCS Messaging, or the toggle for RCS Business Messages, then your carrier has disabled RCS Business Messages on iOS.

Does RCS support media?

RCS supports media with images, video and audio content globally. When you send media messages through Messaging Services, Twilio will automatically deliver RCS media messages to compatible devices. Devices that cannot receive media via RCS will still receive MMS messages where supported or a link to the media. For more information on RCS media support see

Send an RCS message containing media. For a full list of what media types RCS supports see RCS-supported media formats.

RCS also supports media via rich messaging through Content Templates including media, carousels, and cards.  For more information see Send an RCS message containing rich content.

Does RCS support Group Messaging?

There is no support for group messaging with an RCS Sender at this time. 

Are there any throughput restrictions or daily caps on your RCS traffic?

RCS currently supports athroughput of 100 messages per second.

How much does RCS cost?

Prices vary by country or region. Most Basic Message prices match the SMS prices in the region. Please speak with your account executive for more information. 

Message Category Definition
Outbound – Basic Message Mobile-terminated text messages up to 160 UTF-8 characters.
Outbound – Single Message

• Mobile-terminated text messages greater than 160 UTF-8 characters, up to the max message length.

• Media and rich content will be charged at this rate, once supported by Twilio.

Inbound Message Any mobile-originated message including text and media, once supported.

 

Additional Pricing Considerations:

  • RCS messages are charged only when they have reached "DELIVERED" or "READ" status. 
  • Unlike SMS, RCS messages do not require segmentation. Messages greater than 160 characters are maintained as a single message and charged one fee. 
  • Consistently with SMS, RCS messages to and from North-American end-users will incur both a message fee and carrier fee. Otherwise, RCS messages will only incur a message fee.

What compliance considerations apply to RCS vs. other messaging channels?

Please review and make sure to follow Acceptable Use Policy, Messaging Policy, and the Forbidden Message Categories in the US and Canada. All rules applicable to SMS and MMS also apply to RCS. In addition, as Twilio utilizes Google’s platform for RCS Business Messaging, please review and make sure to follow the Google Business Communications Acceptable Use Policy.
Prohibited categories for RCS include:

  • Counterfeit goods
  • Dangerous products or services
  • Products, services, or content that enable dishonest behaviors
  • Dangerous or derogatory content
  • Shocking content
  • Capitalizing on sensitive events
  • Animal cruelty
  • Adult or sexual content
  • Tobacco
  • Political content
  • Unauthorized content
  • Gambling or gambling-related activities
  • Firearms/weapons
  • Cannabis
  • Prescription drugs/medications
  • Alcohol

Are user-initiated messages supported with RCS?

No, not at this time. We are working with our ecosystem partners and hope to offer it in the future. 

How do I register for RCS?

Request access through your account representative or by filling out this request form. For more information on the registration process, please see the onboarding section of our product documentation. 

Does RCS require a Messaging Service?

Yes, to send traffic from your RCS Sender, you’ll need to add it to a Messaging Service as described in the docs. Your Messaging Service will automatically select your RCS Sender when sending to an RCS capable recipient. 

Where can I find the API documentation for RCS?

RCS is supported as part of Verify and the Programmable Messaging API via Messaging Services. You do not have to use a separate API. You can find information about Messaging Services here. RCS-specific documentation is available here

Can I register RCS Senders for my client businesses as an Independent Software Vendor (ISV)?

At this time, due to the manual registration process required for RCS Messaging, we are not supporting RCS Sender registration for client businesses. Twilio is working with our messaging partners to automate RCS Sender registration to support our ISV customers. In the meantime, you may request access for your brand to start testing. 

How can I tell if my RCS message was delivered?

RCS message statuses are visible in both your Messaging Logs, Messaging Insights, and when a Status Callback webhook is set on either your Messaging Service or RCS Sender.

For outbound messages sent using your RCS Sender, you can find the RCS Sender’s ID in the “From” field. RCS Sender IDs will start with “rcs”. 

In Messaging Insights, you view RCS traffic by filtering the Channel to RCS.

What happens if my end user's device is not RCS-capable?

Each time you request to send a message with the Programmable Messaging API, Twilio will check if the recipient's device is capable of receiving RCS messages. If the device is RCS-capable, Twilio will attempt to send the message as RCS. If it's not RCS-capable, Twilio will instead send the message as SMS using the SMS Senders in your Messaging Service’s Sender Pool. If there are multiple SMS Senders in the Sender Pool, Twilio will follow the existing Sender selection logic.

What happens if my RCS message is not delivered?

Twilio relies on our messaging partners to determine which devices are RCS capable. On some rare occasions, a device may be identified as RCS-capable, but RCS messages may not be delivered to it. At this time, undelivered RCS messages are not re-attempted on SMS and will show an undelivered status.

What are the most common RCS errors?

Please see below for some of the common RCS failures and recommended solutions. 

Error Code Description Recommendation  
ERROR: 21703 The Messaging Service does not have a phone number available to send a message. Make sure your Messaging Service has a registered RCS Sender added to it and a compliant SMS capable Sender for the destination country you’re sending to.  
ERROR 63036 The specified phone number cannot be reached by RBM at this time. Check if the device is switched off or RCS not enabled.  
ERROR: 63035 This operation is blocked because the RCS agent has not launched, the recipient has not accepted the invitation to become a tester, or the RCS sender only works in certain regions. Make sure you have completed the RCS onboarding process and confirmed that you are registered in the destination country.   
ERROR: 63001 Channel could not authenticate the request. Please see Channel specific error message for more information Contact Support for additional guidance.  

 

Have more questions? Submit a request
Powered by Zendesk