Skip to main content
RCS-Campaigns
Guide

How to get an RCS Business Messaging agent verified and launched

Every business sender on RCS, which Google calls an agent, has to pass brand verification and launch approval before it can message customers. This guide covers what each step checks and what to prepare, with links to Google's documentation.Updated November 10, 2026 · Based on Google's RCS for Business documentation

In short

RCS Business Messaging (RBM), which Google's documentation now calls RCS for Business, lets a brand message customers from a verified sender called an agent. A registered RBM partner creates the agent, fills in the brand's information, and submits a launch request. The brand then confirms the agent (brand verification), and Google, the carriers, or both review it (launch approval). Once approved, the agent can reach RCS users on the approved carrier networks (Verify and launch your agent).

Who is involved

  • The brand is the business whose name and logo customers see. An authorized representative of the brand confirms the agent during verification (Brand verification).
  • The agent is the brand's sender. The messaging app shows its name, logo, description, contact information, and URLs (Create an agent).
  • The RBM partner is an organization registered with Google to build and run agents. A partner can create agents for brands it manages and send messages through them, so a business can launch through a messaging provider that is already a partner (Register as a partner).
  • Carriers are the mobile networks an agent launches on. On Google-managed networks, Google runs the review for the carrier. Carrier-managed networks run their own (Verify and launch your agent).

The process, step by step

  1. 1

    Create the agent

    In the RCS for Business Developer Console (or through the API), the partner enters the brand, agent name, hosting region, billing category, and use case (Create an agent).

  2. 2

    Fill in the agent information

    Display name, description, logo, banner, brand color, contact details, and Privacy Policy and Terms of Service links. The agent has to be complete before it can be submitted for verification and launch (Edit agent information).

  3. 3

    Submit the verification information

    Name the brand contact, and add a verification token or supporting documents where a carrier needs them. This has to happen before the first launch request, and agent information can't be edited after it is submitted (Brand verification).

  4. 4

    Test the agent and build the opt-out flow

    Google's prerequisites include testing the agent and its infrastructure and implementing the STOP (opt-out) flow before you ask for launch (Launch approval).

  5. 5

    Submit a launch request

    Answer the launch questionnaire and choose the carrier networks. The request starts brand verification and a review of the agent's assets (Launch approval).

  6. 6

    Brand verification

    An authorized representative of the brand confirms the agent's information and the partner's right to manage it (Brand verification).

  7. 7

    Launch approval

    Google, the carriers, or both review and approve the agent and its launch information (Verify and launch your agent).

  8. 8

    Go live

    You get a confirmation email and the Launch page shows a status per carrier. Google says the agent is reachable about 30 minutes after its status changes to Launched (Launch approval), and Google Messages then shows a verification checkmark next to the agent's name (Brand verification).

What brand verification checks

Brand verification confirms that the brand stands behind the agent. Google describes it as an authorized brand representative verifying your agent information and your right to manage the agent as a messaging partner (Brand verification). In practice:

  • It starts with the launch request. You submit the verification information before the first launch request and can edit it until then, but not after. Verification itself happens once the launch request is in.
  • The brand contact has to reply. For Google-managed launches, the brand contact receives an email from rbm-support@google.com asking them to approve brand use for the agent. Google says the reply is required and that a faster reply speeds up approval (Launch approval).
  • Google-managed verification happens once. After the brand verifies an agent, it counts as verified for all future Google-managed launches. On carrier-managed networks, each carrier may contact the brand as part of its own review.
  • Some carriers require a verification token. A token is issued by a Verification Authority, and the agent ID, name, logo, and banner must exactly match the values in it. Google says RCS apps will eventually check tokens directly and that agents launched earlier will need one; it hasn't published dates for this.
  • The result is visible. Once an agent is verified and launched, Google Messages shows a checkmark next to its name, and the conversation details page names the entity that verified it.

Launch approval and carriers

You choose carrier networks in the Select carriers form on the Launch page of the Developer Console. Each network is one of two kinds (Verify and launch your agent):

  • Google-managed: Google handles brand verification and launch approval for the carrier. You first need a launch on at least one carrier-managed network in the same country, and this doesn't transfer across countries.
  • Carrier-managed (marked with an info icon): the carrier runs its own approval process and may have extra requirements. Some reject a launch if they have no contract with you, and Google advises checking each carrier's criteria directly.

Google's documentation gives one explicit timeline: a Google-managed launch takes 1–3 business days if the brand approves within 24 hours, the website, Privacy Policy, and Terms of Service links are accurate and publicly accessible, and every field in the agent experience section is filled in with a preview video or detailed transcripts (Launch approval). It gives no timeline for carrier-managed networks. The questionnaire can't be edited once submitted, and if another carrier starts supporting RCS for Business after your launch, reaching it takes a new launch request.

What to prepare

Google asks for the following across agent creation, the agent profile, verification, and the launch questionnaire. Carrier-managed networks can ask for more.

Decided when the agent is created

  • Brand and agent name.
  • Hosting region: North America, Europe, or Asia Pacific. It sets where the agent operates and stores data, and can't be changed after the agent is created.
  • Billing category: Conversational (multi-turn conversations) or Non-conversational (messages that don't expect frequent replies).
  • Use case: OTP, Transactional, Promotional, or Multi-use. It can't be changed once the agent is submitted for launch.

Source: Create an agent

Agent information

  • Display name, usually the brand name.
  • Description: a short description or tagline, with no script, HTML, JSON, or template code.
  • Brand color with at least a 4.5:1 contrast ratio against white.
  • Logo: 224 × 224 px, shown as a rounded square. Leave space around it and avoid a transparent background, which can disappear in dark mode.
  • Banner image: 1440 × 448 px, shown when a user opens the business information.
  • Contact details: at least one of a phone number, website, or email for Google-managed launches. Google recommends all three, and the email should belong to an individual at the brand.
  • Privacy Policy and Terms of Service URLs: required for launch, and the links must be valid.

Source: Edit agent information

Verification information

  • A brand contact: an employee of the brand with the authority to verify the agent, with an individual email address rather than a distribution list.
  • A verification token, where a carrier requires one.
  • Optional supporting documents such as an authorization letter: PDF only, up to 5 files of 50 MB each.

Source: Brand verification

Launch questionnaire

  • Agent information and points of contact (name, email, and phone number).
  • The use case. Every description must match the use case chosen when the agent was created.
  • Opt-in: how you get users' consent. The questionnaire marks this field optional, but the Acceptable Use Policy requires consent before you message anyone.
  • Triggers: the event or user action that starts the first message, and when and why it is sent.
  • Interactions: a step-by-step transcript with the exact message text, buttons, suggested replies and actions, rich cards, and media links. This is where your sample messages go.
  • Opt-out: the supported keywords (STOP is required) and the exact confirmation message.
  • Optional screenshots and an agent preview video at publicly accessible URLs.
  • The carrier networks to launch on.

Source: Launch approval, Acceptable Use Policy

Use cases and content rules

Every agent has one predefined use case, and it decides what the agent may send. Some rules vary by country, so check the ones for the countries you plan to launch in (Agent use cases and business rules).

Use caseWhat it sendsWhat it can't include
OTPOne-time passwords to authenticate an account or confirm a transaction.Product information or notifications, offers, promotions, discounts, or upgrades.
TransactionalNotifications, updates, or alerts about a customer's existing products or services, such as purchase confirmations or shipping updates.Offers, promotions, discounts, or upgrades for new or existing products or services.
PromotionalSales, marketing, and promotional messages to new or existing customers, such as offers and abandoned-cart reminders.OTP or 2FA codes for account login, or time-sensitive product, service, or transaction information.
Multi-useConversations that combine transactional and promotional messages.OTP or 2FA for login, password resets or other secure account access, and conversations that are only transactional or only promotional.

In some countries a multi-use agent can launch with only one of its two use cases active, but Google requires the second to be implemented and proven to RCS for Business support within six months of launch.

Common reasons for rejection or delay

Google doesn't publish a single list of rejection reasons. The items below are requirements its launch documentation says a submission has to meet, so missing one is a likely cause of a rejection or a slower review.

The agent isn't ready

Google expects an agent that can talk to non-test users, lets them opt out, and lets reviewers walk through its flows. If it can't do those things, Google says it isn't ready to launch (Launch approval).

Missing or unclear agent experience fields

The trigger, interaction, and opt-out descriptions are required, and the flows have to be shown with a preview video or detailed transcripts. Google's 1–3 business day estimate for Google-managed launches depends on this section being complete (Launch approval).

Website or policy links that don't work

The website, Privacy Policy, and Terms of Service links must be working and publicly accessible (Launch approval).

A slow or unreachable brand contact

The brand contact's reply is required, and Google says faster replies speed up approval (Launch approval). Use an individual's email, not a distribution list (Brand verification).

Flows that don't match the use case

Launch descriptions must match the use case chosen when the agent was created (Launch approval), and each use case has content it can't include (Agent use cases and business rules).

Content the policy prohibits

The Acceptable Use Policy prohibits categories such as tobacco and political content, and restricts regulated goods and services (Acceptable Use Policy).

Carrier requirements

Some carrier-managed networks reject a launch when they have no contract with the partner, and some carriers require a verification token whose agent ID, name, logo, and banner exactly match the agent (Verify and launch your agent, Brand verification).

No carrier-managed launch in the country yet

A Google-managed launch needs the agent to be live on at least one carrier-managed network in the same country first (Verify and launch your agent).

How message content rules apply after launch

The launch review is based on the conversations you describe. The interactions transcript, with exact message text, buttons, rich cards, and media, works as your set of sample messages, and it has to match the agent's use case (Launch approval).

After launch, the Acceptable Use Policy keeps content tied to that registration:

  • Content can change only within the registered use case category and what users consented to.
  • Only message users who have opted in, and honor every opt-out request.
  • A brand may have only one agent sending the same content type to the same user.
  • Prohibited content includes tobacco, political content, and misleading content. Regulated goods and services, such as alcohol, gambling, and healthcare products, are restricted.
  • Google can suspend an agent as soon as it becomes aware of a violation, and repeated violations can lead to an account suspension.

Changes to a launched agent's information need each carrier's approval (Edit agent information). Plan for phones that can't receive RCS too: Google says that when a device doesn't support RCS, the agent should fall back to another channel such as SMS (How it works), so keep an SMS version of each message.

Where RCS Campaigns helps

Brand verification and launch approval are decided by Google and the carriers, so RCS Campaigns can't guarantee approval. It helps with the templates you send, the sender connection, and tracking approvals.

Templates for the use case you register

The library has 500+ RCS templates across 80+ industry categories, plus multi-step conversation flows. Templates follow the structure, branding, and opt-in patterns of campaigns that have already been approved, so you can start from one that fits your agent's use case and describe the same flows in your launch questionnaire. Browse templates by use case.

Sender setup through your provider

You connect the RCS-capable provider you use (supported providers) instead of building the connection yourself. On the Pro plan you can bring your own Twilio account: the Twilio card under Integrations takes the Messaging Service that owns your sender and, if you send RCS, your RCS sender ID, and a Verify sender button checks that the sender can send from that account (Connect your own Twilio account).

Approval tracking

Templates are submitted for approval from the template editor. A status badge shows where each one stands, such as Pending approval, Approved, or Rejected with the reason next to it, and Studio → Submissions lists every template's status in one table (Submit a template for approval).

One approval gate, and help with reviewer flags

A template has to be approved before it can send, and sends through the agent API pass the same approval gate as sends from the app. If a reviewer flags a submission, the team helps you resolve it with your provider (how approval support works).

Start from a template that fits your agent's use case.

Sign up to get started

RCS approval: common questions

What is an RCS agent?
In RCS Business Messaging, the agent is the business sender a customer sees in their messaging app: a display name, logo, banner, description, brand color, and contact details. A Google-registered RBM partner creates the agent for a brand it manages, picks its use case, and submits it for verification and launch.
What does RCS brand verification check?
Brand verification confirms that an authorized representative of the brand approves the agent's information and the partner's right to manage the agent on the brand's behalf. It happens after a launch request is submitted: Google, the carriers, or both contact the brand contact named in the verification information, and that person has to reply. Once an agent is verified and launched, Google Messages shows a checkmark next to its name.
Who approves an RCS Business Messaging agent?
It depends on the carrier network. On Google-managed networks, Google handles brand verification and launch approval on the carrier's behalf. Carrier-managed networks run their own review, can have extra requirements, and some reject a launch if they have no contract with the partner. Before a Google-managed launch, the agent must already be launched on at least one carrier-managed network in the same country.
How long does RCS agent approval take?
Google's launch documentation says Google-managed launches take 1 to 3 business days when the brand approves within 24 hours, the website, Privacy Policy, and Terms of Service links work and are public, and every field in the agent experience section of the launch questionnaire is filled in, with a preview video or detailed transcripts. Google gives no time for carrier-managed reviews, which follow each carrier's own process. Once the launch status changes to Launched, Google says the agent is reachable after about 30 minutes.
Can I change an agent after it is submitted or launched?
Only in limited ways. Google's documentation says agent information can't be edited after the verification information is submitted, the launch questionnaire can't be edited after it is submitted, the use case can't change once the agent is submitted for launch, and the hosting region can't change after the agent is created. After launch, each carrier has to approve changes to the agent's information, and agents can't be deleted.
Do I need to register with Google as an RBM partner?
Not necessarily. Partners register with Google to build and run agents, and Google's documentation says a partner can create agents for brands it manages and send messages through them. A business can therefore launch through a messaging provider that is already a registered partner, which creates the agent and submits it for launch.
Why do RCS agent launches get rejected or delayed?
Google doesn't publish a single list of rejection reasons, but its launch requirements point to the usual causes: an agent that isn't fully tested or has no working STOP flow, missing or unclear trigger, interaction, and opt-out descriptions, website or policy links that don't load publicly, a brand contact who doesn't reply, flows that don't match the declared use case, content that the Acceptable Use Policy prohibits, and carrier requirements such as a contract or a verification token.

Sources

Checked on November 10, 2026. Google updates these pages, so check the current version before you submit.

  1. Verify and launch your agent · Google for Developers
  2. Brand verification · Google for Developers
  3. Launch approval · Google for Developers
  4. Create an agent · Google for Developers
  5. Edit agent information · Google for Developers
  6. Agent use cases and business rules · Google for Developers
  7. Acceptable Use Policy · Google for Developers
  8. Register as a partner · Google for Developers
  9. How it works · Google for Developers
  10. Submit a template for approval · Business Messaging help center
  11. Connect your own Twilio account · Business Messaging help center