This page provides information about the upcoming changes for RCS for Business.

## Upcoming enforcement of verification tokens

### Effective date: To be announced

Verification tokens are currently **optional** in all countries. You can launch
agents without a token. At a later date, providing a **valid verification
token** will become a requirement when requesting an agent launch on certain
carriers. If a token is missing or invalid, the launch request will fail.

Additionally, RCS clients will begin validating verification tokens directly. If
a verification token is missing or invalid, the chatbot verification experience
may be degraded in a way that is specific to the RCS client. Action will be
required to maintain a seamless chatbot verification experience for existing
agents.

### What you need to do

- **Prepare for launch requirements**: Ensure your integration is ready to pass verification tokens when requesting launches on supported carriers.
- **Update existing agents**: To prevent a degraded user experience, you need to update all of your previously launched agents to include a valid verification token.

For more information about tokens and how to specify them, see the updated
[Brand verification](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt#verification-tokens)
guide.