RCS brand verification (Google developer docs)

google‘s guide to verifying an RCS agent before it can launch. The clearest statement in this wiki of how a channel establishes who is allowed to message on a brand’s behalf.

What verification is for

The stated purpose: an authorized brand representative confirms the agent’s information and the messaging partner’s right to manage it. Two separate assertions, and the second is the load-bearing one — the channel is guarding against a partner speaking as a brand without permission.

The submission takes contact details for a brand employee with authority to verify, plus optional supporting documents (up to five PDFs, 50 MB each) such as authorization letters. It is submitted once per agent through the Developer Console, before the first launch request, and cannot be modified after that request goes in.

The authorization email

Google’s documentation is specific that the representative’s address should be an individual, not a distribution list, because that address receives a mandatory authorization request the brand must answer to confirm the partner may act for them. A shared inbox breaks the accountability the step exists to create.

Google-managed vs carrier-managed

Under a Google-managed launch the brand is contacted once, at the initial request; the agent is then approved for all future Google-managed launches. Under a carrier-managed launch, individual carriers may contact the brand separately under their own approval procedures — so a multi-carrier rollout can mean repeated brand contact.

After approval, Google Messages shows a verification checkmark beside the agent’s name as proof of sender authenticity (sender-verification).

Tier

T1. First-party process documentation. Procedural rather than promotional, and the most concrete account of an approval gate the wiki currently holds.

Related

rcs-business-messaging · sender-verification · rcs-business-messaging-docs · business-solution-provider · google · synthesis