Get started with branded RCS messaging
Unlike SMS, MMS, or RCS messaging between users, RCS business messaging does not rely on a phone number to send messages. Instead, RCS messages are sent using an RCS Sender (also known as an "RCS agent"). Messages sent from different RCS Senders are shown to users in separate conversation threads, similar to SMS or MMS messages sent from different phone numbers.
In this tutorial, you'll learn the setup and configuration required to send and receive branded RCS messages:
- Create an RCS Sender and send test messages
- Submit compliance for carrier approval
- Update Messaging Service configuration
To learn more about RCS, see RCS Business Messaging.
- RCS messaging is not available in all countries. See Regional Availability.
- Programmatic access for creating RCS Senders and onboarding at scale is not available.
Before you set up RCS, you will need to:
- Sign up for a Twilio account and upgrade to a paid account.
- Set up Messaging Services with a phone number for SMS or MMS.
- Not all phone numbers can receive RCS messages. Messaging Services allow messages to be sent using SMS or MMS when RCS messages fail or cannot be used.
Follow these steps to set up and configure RCS messaging with Twilio.
Allow four to six weeks (or longer if you plan to launch in multiple regions) to complete the setup process.
- Go to the RCS Senders page in the Twilio Console and click Create RCS Sender.
- Accept the terms and conditions, provide a display name, and click Continue.
(information)
Creating multiple Senders for the same brand?
When creating multiple RCS Senders for the same brand (for example, "Owl Homes"), use unique display names for each Sender so users can tell them apart in their Messaging app. (for example, "Owl Homes Support" and "Owl Homes Promotion"). Carriers typically do not approve RCS Senders with the same display name and logo.
- On the Public details page, provide the following information. Carriers in some countries have Special Considerations regarding a Sender's public display.
Field | Description | Requirements | Device Support |
---|---|---|---|
Display name | Name shown to users | Unique per RCS Sender | iOS & Android |
Description | Brief summary of Sender including how users will interact with your Sender. | Some content, such as HTML, JSON, Unix commands, or escaped characters, is not allowed. | iOS & Android |
Logo image | Brand logo in conversations | JPEG, JPG, or PNG image of 224 x 224 pixels with a max size 50kB. URL must be publicly accessible. | iOS & Android |
Banner image | Banner at top of conversation | JPEG, JPG, or PNG image of 1140 x 448 pixels with a max size 200kB. URL must be publicly accessible. | Android only |
Accent color | Color of certain elements displayed | Can match brand colors. Minimum 4.5:1 contrast ratio to white. | Android only |
Contact details | One or more phone, email, or website (each with a label) | At least one phone number or email is required. Phone numbers must be formatted in E.164. | iOS & Android |
Privacy policy URL | Link to brand privacy policy | May need to be accessible in country's offical language. | iOS & Android |
Terms of service URL | Link to brand terms of service | May need to be accessible in country's offical language. | iOS & Android |
- Click Next to save the RCS Sender. Test how the RCS Sender is displayed on your device.
- Click Add device to test this sender and enter your phone number.
- You will receive an RCS message from the "RBM Tester Management" Sender. Tap Make me a tester to accept the invite.
- Once the invite is accepted, send a test RCS message to see how the RCS Sender is shown to users. To receive inbound messages, use the Configure tab to set your Sender's webhooks.
- Click Done to finish creating the RCS Sender.
- To continue to edit and refine the RCS Sender, click View Sender. You can continue to explore RCS by sending RCS messages to phone numbers added as test devices.
- Before you may message phone numbers not added to your Sender as a test device, carriers must approve the RCS Sender. If you have already tested RCS and are ready to submit it for approval to use in production, go to the Carrier Approval tab and submit the required compliance information.
-
Go to the RCS Sender's Carrier Approval tab and click Continue setup.
-
After submitting the compliance information, you won't be able to edit your Sender's public display details. Click I understand to continue.
-
Complete the compliance form.
Provide compliance information about your business and messaging use case(s):
- Select the countries where you want to launch the RCS Sender.
- Campaign Review: Provide a video showing sample campaign messages, including a functional opt-out flow. To avoid future re-approvals, include both promotional and transactional sample content, even if you plan to start with only one.
- User interaction: Describe how users interact with the RCS Sender, including opt-in processes and message triggers.
- Authorized representative: Provide contact information for someone who can represent the RCS Sender's brand.
Info
We will email the person listed under Authorized representative to provide status updates and to request additional information required by carriers. If you are an ISV submitting an RCS Sender on behalf of your customer's brand, enter your own contact information in this field. After we contact you, you must supply your customer's contact information. Carriers require this information for brand authorization and approval.
-
Review the warning and click Submit to send the RCS Sender to Twilio and carriers for approval.
(warning)Public display details locked after submission
Once you submit the RCS Sender for carrier approval, you can no longer edit your Sender's public details in the Twilio Console. Any changes after submission require manual updates through Twilio Support and may require downtime.
-
Provide additional carrier compliance information (if applicable):
- Depending on carrier requirements within your selected countries, Twilio might request additional compliance information. You may also receive verification emails from a third party (Aegis or Google for example) with instructions to verify you have authorization to operate an RCS Sender for the brand submitted.
- Monitor approval status:
The RCS Sender shows as Under Review during the approval process. Approval timelines vary by carrier. At any point, you can reply to the initial support ticket created when you submitted your Sender if you need an update. You can start using the RCS Sender in production when one carrier is live/approved in a given country.
- Add the RCS Sender to a Messaging Service:
Once at least one carrier has approved, configure the RCS Sender for production use:
- Go to the Messaging Services page in the Twilio Console.
- Either:
- Go to the RCS Sender's Configuration tab and assign it to a Messaging Service, or
- Go to your Messaging Service's Sender Pool tab and add the RCS Sender
You can associate only one RCS Sender with a Messaging Service.
- Set up Advance Opt-Out handling for the RCS Sender:
- Go to the Messaging Services page in the Twilio Console.
- Click your Messaging Service and select Opt-Out Management from the sidebar.
- Configure opt-out keywords and responses in the local language of your target regions.
- Click Enable Advanced Opt-Out.
To learn more about Advanced Opt-Out, see Customizing Users' Opt-in and Opt-out Experience with Advanced Opt-Out.
To learn how to send and receive branded RCS messages, see Send and receive branded RCS messages.
To stop using RCS, you can either send messages through a different Messaging Service or remove the RCS Sender from the Messaging Service.
To remove the RCS Sender from the Messaging Service:
- Navigate to the Messaging Services page in the Twilio Console.
- Select the Messaging Service associated with the RCS Sender, then click Sender Pool in the sidebar.
- Click Remove to delete the RCS Sender from the Messaging Service.
Alternatively, you can set the Messaging Service to None
on the RCS Sender's Configuration tab.