RCS for Business: Access, Roles & Permissions
TL;DR
Google's RCS for Business (formerly RCS Business Messaging) separates the brand that owns an agent, the partner or RCS Solution Provider that builds and operates it, and the carriers it launches on. Brands cannot self-onboard — Google moved to a partner-only model. The documented role model is thin (a Partner Account Owner and a Technical Point of Contact), going live requires brand verification and launch approval, and the operating partner typically holds the credentials.
On this page
Three parties: brand, agent, partner
RCS for Business separates three parties: the brand that owns an agent (the programmatic sender that represents the brand in Google Messages), the partner or developer — typically an RCS Solution Provider — that builds and operates the agent, and the carriers on whose networks the agent launches.
Partners register in the developer console using an individual, corporate-domain Google Account (not a consumer Gmail or a group account) (Google — Register as a partner).
A partner is required
Google fully transitioned to a partner/aggregator model — legacy standalone brand onboarding was deprecated and its docs removed. Brands access RCS for Business only through a certified partner or CPaaS (Twilio, Sinch, Infobip and others).
This puts RCS in the same "mandatory intermediary" category as Apple Messages for Business and KakaoTalk: there is a REST API, but a brand cannot self-onboard to it.
Roles are thin
The documented in-console role model is minimal. There is a Partner Account Owner — who can create and manage agents and API credentials, and whose email is recorded as the agent_owner in carrier billing — and a Technical Point of Contact named to handle deployed-agent issues.
Google does not publish a fine-grained owner/admin/agent/analyst permission matrix, so beyond these named contacts the internal seat model is lightly documented (Google — Brand verification).
Verification, launch, and the credentials
Because the partner operates on the brand's behalf, going live requires brand verification: an authorized brand representative confirms the agent's details and the partner's right to manage it. The agent then seeks launch approval, which is either Google-managed or carrier-managed, and moves from Pending to Launched per carrier. Once approved, a verified checkmark appears beside the agent in Google Messages.
In practice the operating partner holds the technical/API credentials to send through the agent, while the brand authorizes that relationship and can revoke it by withdrawing its verification.
Frequently asked questions
Can a brand connect to RCS for Business directly?
No. Google deprecated standalone brand onboarding and moved to a partner-only model. Brands reach RCS for Business through a certified RCS Solution Provider or CPaaS, which holds the technical credentials and operates the agent.
What roles exist in the RCS for Business console?
Only a Partner Account Owner (creates and manages agents and credentials) and a Technical Point of Contact are documented, plus a brand-side authorized representative who confirms the agent during verification. Google publishes no granular multi-role permission matrix.
Was this called something else before?
Yes — "RCS Business Messaging (RBM)." Google rebranded it to "RCS for Business" and reorganized the launch flow across 2024–2025, so older RBM documentation may not match current console terminology.
Related
Business Messaging: Access, Roles & Permissions Across Platforms
Every major messaging platform gates business access differently. The single most important difference is who holds the technical keys: some platforms (Apple, Google RCS, KakaoTalk, Viber) require an approved intermediary you cannot bypass, while others (Telegram, LINE, WhatsApp, Zalo) let a business hold its own API credentials. Role models range from granular named matrices (WhatsApp, LINE, Zalo) to almost none (Telegram, where possessing the token is control). Asian platforms additionally gate account creation on a registered legal entity.
Read →What is Apple Messages for Business?
Apple Messages for Business is a channel that lets customers start a conversation with a verified company directly in the Messages app on their Apple devices. There is no separate Apple business chat app and no direct Apple API for brands — a company registers its brand with Apple, connects an Apple-approved Messaging Service Provider (MSP), and that provider carries messages between Apple and the company’s systems.
Read →Viber Business Account: Access & Permissions
On Viber (Rakuten Viber), business presence centers on a verified Business Account and the Viber Business Messages service. Every business account must be approved by Viber and pass brand verification, and Business Messages is applied for and operated through an official partner (BSP). Viber publishes no named multi-role hierarchy — the documented model is minimal: a bot administrator, with authorization effectively resting on a secret token, and team management pushed onto the partner platform.
Read →What is a Unified Inbox?
A unified inbox consolidates conversations from multiple communication channels — messengers, email, and more — into a single interface, so you can triage, read, and reply across all of them without switching apps and without losing track of who said what.
Read →Last updated