RCS onboarding and brand verification

The onboarding journey at a glance

1. Define the use case. Decide whether the agent is for OTPs, transactional updates, promotions or multiple uses. This affects review and how messages are categorised.
2. Create the agent. Prepare the display name, description, logo, banner image, brand colour, phone number, website and email customers will see, plus links to your privacy policy and terms.
3. Submit verification information. Provide the contact details of a brand employee who can confirm the agent, and optionally upload supporting documents such as an authorisation letter.
4. Complete pre-launch tasks. Test the agent, implement opt-out handling, and record a short video of the agent's messaging use case that clearly shows the STOP flow.
5. Request launch. Choose the countries and carriers, answer the launch questionnaire and submit.
6. Respond to verification. Google, carriers or both contact the brand contact to confirm.
7. Go live. After approval, Google notes the agent becomes reachable on that carrier about 30 minutes after its status changes to Launched.

What you need to register

To register your RCS agent, keep these details ready. Having them complete is the quickest way through review.

Please note: Share documents with our team during onboarding. Please don't send them through the website enquiry form.

What brand verification checks

Brand verification confirms two things: that the agent's information (name, logo and so on) is accurate, and that the messaging partner is authorised to manage the agent for the brand. It is a prerequisite for launch. Once verified and launched, Google Messages shows a verification mark beside the agent name, and the agent's details page shows who verified it.

Verification information is submitted once per agent, before the first launch request, regardless of how many carriers the agent later launches on. It can't be edited after the launch request is submitted, so check it carefully.

Who should be the brand contact?

Someone employed by the brand with authority to approve the agent. Google asks for an individual's email address rather than a distribution list, because a mandatory authorisation request is sent to it. For Google-managed launches the email comes from rbm-support@google.com with a subject beginning “Please approve brand use for RCS Business Messaging agent”. Replying quickly is one of the biggest factors in launch speed.

Verification tokens

Google's documentation notes that some carriers will require a verification token from a recognised Verification Authority, and that the agent's name, logo and banner must match the token exactly. Timelines for this requirement are announced by Google; we'll tell you if it applies to your launch.

What reviewers look for

• A working public website, plus active links to a privacy policy and terms of service.
• A preview video that matches the declared use case and demonstrates the STOP (opt-out) flow.
• Clear answers about what triggers messages, how users opt in, and the exact opt-out reply.
• Agent information that is accurate and consistent with the brand.

How long it takes

Google states that Google-managed launches take 1–3 business days when the brand approves within 24 hours and all assets are accurate and publicly accessible. Carrier-managed launches follow each carrier's own process, and some carriers require a direct agreement before approving. Preparation time on your side — gathering assets, legal pages and the preview video — often matters more than review time.

Common causes of delay

• The brand contact doesn't see or answer the approval email.
• The privacy policy or terms link is missing or broken.
• The preview video doesn't show opt-out, or shows a different use case from the one declared.
• Logo or name doesn't match the brand's public identity.

How RCS Message.in helps

We help you prepare the agent details and assets, explain what the brand contact will receive, test the agent with you and track launch status. If you are ready to begin, start onboarding or contact our team.