Who this applies to#
- Google's brand verification checks the agent's information and whether the partner is authorized to manage the agent for that brand
What RCS verified sender requires#
- Submit verification information before requesting the agent's first launch
- Brand verification and launch approval are both parts of Google's agent launch process
Google Messages
Google documents a verification checkmark next to the agent's name after verification and launch. This description is specific to Google Messages
What this does not require#
- Verification information is submitted once per agent, not for every carrier launch. Individual carriers may still contact the brand during their reviews
- Verification does not replace the requirement to obtain recipient consent before solicitation
Common mistakes#
- Treating a visible verification mark as evidence that the recipient opted in
- Expecting brand verification to replace each carrier's launch review
- Promising the same visual verification treatment in every messaging client
RCS verified sender checklist#
- Check that the brand representative can confirm the agent's information and authorization
- Submit verification information before the first launch request
- Track verification and launch approval separately
- Inspect the sender display in Google Messages after launch
- Review recipient permission separately from sender verification
Commonly confused with#
OnVoard's take#
Start with a launch record that answers 2 different questions: who approved this agent, and which recipients agreed to hear from the brand? Assign an owner to each answer. A screenshot of the sender name is useful evidence for only part of that review.