This document covers frequently asked questions about brand verification. To
start the verification process, proceed to
[Submit verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt#submit-verification-information).

## What is brand verification?

It's when an authorized brand representative verifies your agent information and
your right to manage the agent as a messaging partner. This is a prerequisite
for launch. After an agent completes the verification process and launches,
Google Messages automatically displays a verification checkmark next to the
agent's name to prove sender authenticity.

Additionally, the Conversation Details Page for the agent includes a
verification item that indicates the sender has been verified as well as the
entity that verified them.

## What information is needed for verification?

- **Brand contact information** : You'll need to provide the contact information for an employee at the brand who has the authority to verify the agent information and your right to manage the agent. For details on who qualifies as a brand POC and which email address is acceptable, see [Submit verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt#submit-verification-information).
- **Verification tokens** : Optional. Verification tokens aren't currently required in any country. In the future, certain carriers will require a valid verification token issued by a recognized Verification Authority to launch. For more information, see [What is a verification token?](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt#verification-tokens).
- **Supporting documents** : You can also upload supporting documents, such as authorization letters, directly to the [RCS for Business Developer Console](https://business-communications.cloud.google.com/). Uploading these documents can help streamline the agent approval process. For more information, see [Submit verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt#submit-verification-information).

## What is a verification token?

A verification token is a Base64-encoded string issued by a Verification
Authority (VA) whose tokens are accepted in your target region.

You can specify verification tokens using the RBM Management API or directly in
the [RCS for Business Developer Console](https://business-communications.cloud.google.com/console/partner-console).

> [!NOTE]
> **Note:** Verification tokens are currently **optional** in all countries. You can launch agents without a token. The **Verification token** section is visible in the Developer Console for all partners so that you can learn about verification tokens and prepare for future requirements.

### Upcoming launch requirements

At a later date, requesting a launch on certain carriers will fail unless a
valid token issued by a verification authority is provided. When you submit a
token, the agent ID, agent name, logo, and banner must exactly match the
corresponding values embedded within the token.

Additionally, RCS clients will eventually begin validating verification tokens
directly. To prevent a degraded user experience, you will need to update all of
your previously launched agents to include a valid verification token. The
exact timeline for these requirements will be announced in a future update.
For the latest information, see
[Coming soon](https://developers.google.com/business-communications/rcs-business-messaging/whats-new/coming-soon.md.txt).

## When do I need to submit the verification information?

You must submit verification information before you submit your agent for its
first launch.

## Do I have to submit verification information for every launch?

No, you only need to submit verification information once per agent, regardless
of how many carriers you launch on. It doesn't matter if the carriers follow a
[Google-managed or carrier-managed launch process](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch.md.txt#google-managed-vs.).

## When does verification happen?

Brand verification happens after you submit a launch request. Here's the
workflow:

1. You [submit verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt#submit-verification-information) (this only happens once: prior to your first launch request).
2. You [complete the prerequisites for launch](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/launch-approval.md.txt#prerequisites) and [submit a launch request](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/launch-approval.md.txt#submit-launch-request).
3. During the launch approval process, Google, carriers, or both reach out to your brand contact for verification.

## How often will the brand be contacted for verification?

This depends on which carriers you've selected for launch.

- [**Google-managed launches**](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch.md.txt#google-managed-vs.): The brand will be contacted once, during your first launch request on any carrier with a Google-managed launch process. Once verified, the agent is considered verified for all future Google-managed launches.
- [**Carrier-managed launches**](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch.md.txt#google-managed-vs.): The brand may be contacted by each carrier as part of their individual launch approval process.

## Submit verification information

> [!NOTE]
> **Note:** To verify your agent using the RBM Management API, refer to the [Submit verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/agents.md.txt#submit_verification_information) and [Look up an agent's verification status](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/agents.md.txt#look_up_an_agents_verification_status) documentation.

To submit verification information:

1. In the [RCS for Business Developer Console](https://business-communications.cloud.google.com/), navigate to the **Verification** page.
2. Fill out the information and click **Update agent verification info**.

   You can edit the verification information before submitting a launch
   request, but not after.

   > [!IMPORTANT]
   > **Important:** Please provide an individual brand representative's email address rather than a distribution list. We use this address to send a mandatory authorization request, where the brand must confirm that you're permitted to manage the agent on their behalf. This is a required step for launch reviews, particularly on Google-managed carriers.

3. Optional. In the **Supporting documents** section, click **Upload file** to
   add any documents, such as authorization letters, that confirm your authority to
   manage the agent. Follow these requirements:

   - **File type**: PDF
   - **Max file size**: 50MB
   - **Quantity**: Up to 5 files. Avoid file duplications.

   > [!NOTE]
   > **Note:** To upload supporting verification documents using the Business Communications API, use the [`attachments.create`](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/attachments/create.md.txt) API method.

   Please follow carrier guidelines on which documents are relevant and
   necessary for launching on their network.
4. Click **Proceed** to confirm that Google, carriers, or both should email
   your brand contact to verify your agent. This will happen after you submit
   a launch request, as part of the approval process.

5. To submit a launch request, click **Go to Launch**.

> [!NOTE]
> **Note:** You can upload or delete files as needed before submitting a launch request. But after the launch request is submitted, you can no longer add or delete files.