Who this applies to#
- Google's RCS for Business platform connects business agents with users on supported devices
What RCS for Business requires#
- Google requires notice and consent before soliciting users through RCS for Business
- Brands must honor consent withdrawal across all their promotional agents
- An agent needs brand verification and launch approval from Google, carriers, or both
- A Google-managed launch requires an existing launch on a carrier-managed network in the same country
What this does not require#
- Launch approval does not make every phone reachable. Unsupported devices need another delivery approach, and launch coverage depends on approved networks
- Brand verification does not replace the separate requirement for recipient consent
Common mistakes#
- Assuming that a successful launch establishes worldwide reach
- Testing rich messages without testing an unreachable recipient
- Treating sender verification as the recipient's permission to receive a message
RCS for Business checklist#
- Identify the countries and networks the agent is approved to serve
- Check how consent is collected before solicitation
- Test what happens when a recipient cannot receive the RCS message
- Check permission separately for any fallback channel you intend to use
- Test how a promotional opt-out reaches the brand's other promotional agents
OnVoard's take#
Test failure first. Reach varies. Check fallback. Start with an unreachable recipient and a request to stop messages. Decide how those cases should behave before polishing the rich cards. Keep a clear record of the approved networks so a successful test is not mistaken for a wider launch.