RCS Onboarding Guidelines

To send messages using RCS, RCS application needs to be created and launched on technology provider as well as all Carriers in the countries where your business is planning to operate and send messages.

RCS messages between a user and a RCS application appear in an RCS-enabled messaging app, such as iMessage or Google Messages, on the user's device. The messaging app displays branding and profile information for your RCS application, including name, logo, description, contact information, and URLs.

You could create a single RCS application for your business that allows users to interact with various departments. Alternatively, you could create separate RCS applications for each department.

To create and launch this RCS application, we need details about your business and the messages that you plan to send. Please find the data that is required and some guidelines on what we are looking for.

RCS Onboarding Guidelines

Field Name	Tooltip / Description
Display Name	Name of the RCS app shown to users in their messaging app; must be your customer-facing brand name exactly as users recognize it; avoid generic names like “Support” or “Notifications”; should match your website and branding; names that look misleading, too generic, or unrelated to your brand are commonly rejected This should not be blank, no spaces and can be up to 40 characters long.
Description	Clearly defined overview of the type of messages that will be sent on the RCS application (e.g., OTPs, order updates, account alerts, offers); should help users immediately understand why they are receiving messages; avoid vague text like “We provide updates” or promotional phrases; max 100 characters; should align with selected use case. This helps set user expectations about the capabilities and purpose of the RCS application.
Brand Name	This is name of Business, Organization or Group that is represented by the agent. This information may be shared with carriers for the purpose of receiving launch approval for the agent.
Billing Category	This defines how messages that are sent from RCS application are charged. Currently, only non-conversational is supported in Connect platform. Non-Conversational: Messages are billed per message basis. This is ideal for messages which are not expected to get many responses from users. Conversational: Messages are billed by considering conversations (interactions within 24hr window). Outside this window are billed as per message.
Region	Region where the RCS app is provisioned; should match your primary user base and business operations.
Use Case	Select the category that best represents the actual messages you will send: OTP: One-time passwords required to securely authenticate an account or confirm a transaction. Transactional: service-related updates triggered by user activity (e.g., order confirmation, delivery updates, account alerts). Promotional: marketing messages like offers, discounts, campaigns to new or existing customers. Multi-use: Conversations that combine transactional and promotional messages, such as sending an account notification followed by a discount offer or upgrading to a new product or service.
Color	Primary color used for buttons and UI elements in the conversation; must be a valid HEX code (e.g., #0F62FE); should align with your brand’s primary color and ensure readability (Black will be used as default). Minimum 4.5:1 contract ratio.
Large Banner	The banner image displays when a user views your business information; must be 1440×448 px in JPG or PNG format.
Logo	Official brand logo shown in the messaging app or chat; must be 224×224 px in JPG or PNG format.
Label for Phone number	Display label for the phone number, Customer Care Number.
Phone Number	Customer-facing support number shown in the RCS business profile; Up to 3 numbers can be added.
Label for Website	Display label for the website.
Website	Official website of the business; Up to 3 websites can be added.
Label for Email	Display label for the Email, for example Customer Care Email.
Email	Brand or Business email displayed to users; Up to 3 Emails can be added.
Privacy Policy URL	Your company’s public facing privacy policy web link.
Terms of Service URL	Your company’s public facing terms and conditions web link.
Test Numbers	Numbers to be invited to test the RCS Text Service. International format (+15551234567).
Brand Website	Required in RBM console as part of verification / launch.
Brand Contact Name	Name of Contact within the organization who is responsible for the agent.
Job title	Title of Contact within the organization who is responsible for the agent.
Brand Contact Email	Email of Contact within the organization who is responsible for the agent.
Legal Company Name	Registered legal name of your company.
Tax Identification	Required except for sole proprietors. National tax ID associated with your company’s legal name. For US, must be US IRS FEIN (EIN).
Tax ID Country	Required except for sole proprietors. Please provide the country associated with the above tax ID (ISO country code, US territories should specify US).
Stock Exchange Info	Required for public companies only, not applicable for non-public companies. Please provide: Stock Exchange: The primary home country stock exchange abbreviation. Stock Symbol: Primary home country stock symbol associated with Stock Exchange.
Proof of Ownership / Authorization letter	Legal documentation to attest that an aggregator has the right to represent your brand for the purpose of business messaging is required. Please share with your account manage a separate PDF document (max 10 MB) with this attestation. The letter must be: Officially signed Dated On letter head of brands legal company. Include the title of the responsible party at the brand.
Org Contact Name	Name of Contact within the organization who is responsible for the agent.
Org Contact Title	Title of Contact within the organization who is responsible for the agent.
Org Contact Email	Email of Contact within the organization who is responsible for the agent.
Opt-in Details	Explanation of how users explicitly consent to receive messages (e.g., website form, app signup, SMS keyword); must be user-initiated and clearly described; implicit or unclear consent leads to rejection.
Trigger	Short name/identifier for what initiates messaging (e.g., Login OTP, Order Confirmation, Delivery Update, Promotional Campaign); should be specific and reflect actual event.
Trigger Description	Detailed explanation of what event triggers messages; must clearly describe the exact user/system action (e.g., “User attempts login and requests OTP”, “User completes purchase on website”); should not be vague like “when needed”.
Interaction Description	Describes how the RCS app interacts with users after sending messages; must clearly explain whether the experience is one-way (no replies expected) or two-way (user can respond and receive further messages); if two-way, must describe what happens when a user replies (e.g., chatbot flow, human agent escalation); should reflect actual conversation flow, since RCS is designed as an interactive messaging channel.
Opt Out Description	Exact message and mechanism used when a user opts out of communication; must include the specific keyword or action (e.g., STOP) and the system response message confirming opt-out; Google explicitly requires that the opt-out flow is implemented and demonstrated during review; unclear or missing opt-out handling is a major rejection reason.
Access Instructions	Instructions for how reviewers (and users) can access and test the RCS app; must clearly describe how a user enters the messaging flow (e.g., “Sign up on website → receive first message”, “Send keyword to initiate flow”); should include any prerequisites (test account, steps to trigger message).
Experience Video Uris	Links to videos demonstrating the actual user experience (end-to-end flow); should show real or near-real flows including message receipt and interaction; helps reviewers understand use case clearly; recommended for complex or conversational use cases.
Experience Screenshot Uris	Links to screenshots of actual messages and flows (e.g., OTP message, order update, rich cards); should reflect real content and branding; must match sample experience described in other fields.
Launch Countries and Carriers	List of countries and (if applicable) carriers where the RCS app will be launched.
Use Case (Detailed)	Detailed explanation of how the RCS app will be used; must include: trigger events (e.g., login, purchase), types of messages sent, sequence of communication, and whether users can respond; should be written as a clear real-world flow, not generic statements.
Brand Details	Description of the brand being represented; should include what the business does, services offered, and how it relates to messaging use case; must align with website and branding assets.
Rights to Branding	Confirmation that you have legal rights to use the brand name, logo, and assets; must be true and verifiable; using third-party or unauthorized branding will lead to rejection.
Traffic Estimate	Estimated volume of messages (e.g., daily/monthly users, number of messages per event); should be realistic and aligned with use case; helps reviewers assess scale and compliance risk.