This article explains the information carriers require before approving and launching an RCS Agent.
Important: Incomplete or inconsistent information is the most common reason for RCS agent delays or rejections. Make sure all details below are accurate and consistent with your brand.
1. Branding Information
Carriers require clear identification of the business behind the RCS agent.
- Legal name of the brand’s parent company
- Website of the brand’s parent company (must be publicly accessible)
- Brand name as it should appear to end users
2. Brand Point of Contact
This contact is used by carriers or aggregators for verification questions.
- Full name
- Job title
- Business email address
3. Agent Experience & Messaging Behavior
Proof of Opt-In (Required)
You must explain how users consent to receive RCS messages from your brand.
- The opt-in source must belong to the same brand registered for the RCS agent
- If opt-in occurs via a website, provide the exact URL
- If opt-in occurs via a mobile app, provide the app name and store listing URL
Note: Opt-in data from a different brand or partner will result in rejection.
Actions That Trigger MT Messages
Identify the events that cause mobile-terminated (MT) messages to be sent to users.
- Purchase confirmations
- Order or delivery notifications
- Reservation confirmations or reminders
- Promotional campaign triggers
You must also specify the time interval between the triggering event and when the message is sent.
Interaction Types
Define how users are expected to interact with your RCS agent.
- Primary interactions (e.g., notifications, confirmations, promotions)
- Secondary interactions (e.g., replies, button clicks, follow-up messages)
Proof of Opt-Out Handling
Explain what happens when a user opts out of receiving messages.
Critical Requirement:
If a user replies with STOP, no additional messages may be sent unless the user explicitly opts back in.
If a user replies with STOP, no additional messages may be sent unless the user explicitly opts back in.
- Your agent must recognize STOP in English
- Your agent must also recognize STOP in every language used for RCS communications
- Provide the opt-out confirmation message sent to the user
4. Usage & Traffic Expectations
Carriers use this information to assess capacity and compliance risk.
- Expected message traffic spikes (peak days/times)
- Estimated number of users per month
- Estimated number of messages per month
- Average interactions per user per campaign
5. Campaign Start Date
Provide the planned launch date for your RCS campaign or agent.
Tip: If your campaign date is flexible, indicate an estimated range rather than a fixed day.