Brand Verification Comes Before Your First RCS Launch

Brand verification is not a marketing badge a partner can toggle on. Google requires it before the first RCS for Business launch. An authorized brand representative verifies the agent information and the partner's right to manage the agent. Verification information is submitted once per agent, before the first launch request. After the agent completes verification and launches, Google Messages can display a verification checkmark next to the agent name. Conversation Details can also show that the sender was verified and which entity verified them. Partners cannot self-apply the badge.

That is the whole claim. Verification first. Launch next. Checkmark on Google Messages after launch. Pair MessageOS verified sender with Google's brand verification guide when you brief a brand or an agency.

RCS is live on all US carriers and on iOS and Android. That is channel availability, not a customer claim, and not a promise that every device gets a rich card. When the client can take it, RCS for Business gives you the power of an app with the reach of a text message: a verified sender, delivery receipts, read receipts, typing indicators, rich cards, and suggested replies and actions. Verification is how the inbox proves the brand behind those primitives.

What an agent is, and why verification attaches to it

An agent is a programmatic entity that represents a brand. The messaging app shows name, logo, description, contact information, and URLs. MessageOS explains the same idea on what is RCS for Business. Use case is locked when you submit for launch (OTP, transactional, promotional, or multi-use). Verification is separate from use case, but it sits on the same agent record. One agent. One verification submission before first launch. Do not treat the checkmark as a content-quality seal. It proves sender authenticity after launch on Google Messages, not that every message is marketing-safe.

Google's Acceptable Use Policy requires the publicly branded business name, accurate and up-to-date business information, and the legal business name of the brand that owns the agent when you create it. Name accuracy is part of trust. It is not optional copy polish.

Partners manage. Brands authorize. Google and carriers approve.

Businesses reach RCS for Business through a partner. Google's Find a partner page says partners provide the APIs and expertise and manage carrier connections. MessageOS talks as a partner, not as Google and not as a carrier. See the same partner-first framing on what is RCS for Business. The brand does not "turn on RCS in Google." The brand picks a partner. The partner creates the agent. An authorized brand representative confirms agent info and the partner's right to manage it. Google and/or carriers then contact the brand point of contact as part of launch. For Google-managed launches the brand is contacted once. For carrier-managed launches each carrier may contact the brand.

Do not invent timelines. The sourced rule is order of operations: submit verification once per agent before the first launch request, then launch, then the Google Messages checkmark can appear. Do not claim the checkmark on every client, every carrier, or before launch.

Trust signals are not the whole product

Google's trust and spam post frames verification as part of a regulated, scanned channel. Pair that with verified sender. Business RCS is not end-to-end encrypted. See security. It is not HIPAA compliant. Keep PHI out of the thread. For appointment patterns without PHI, use healthcare and RCS for healthcare.

Once the agent is live, events include DELIVERED, READ, and IS_TYPING, plus suggestion postbacks and unsubscribe. Those receipts and indicators are native Messages capabilities MessageOS teaches next to the verified profile on what is RCS for Business. Verification gets the brand into the inbox as authentic. Events tell operators what happened next.