Who this applies to#
- The agent includes the user-facing messaging experience and the code and infrastructure supporting it
What RCS agent requires#
- Each agent must declare a use case: OTP, transactional, promotional, or multi-use. The use case cannot be changed after submission for launch
- Google's launch checklist calls for an implemented and tested STOP flow, complete agent information, a working website, and privacy-policy and terms links
- The launch submission must include a preview video demonstrating the declared messaging use case and STOP behavior
What this does not require#
- Approval covers supported users on approved networks, not every RCS user worldwide
Common mistakes#
- Choosing a use case without comparing it with the actual planned messages
- Treating an agent's use case and billing category as the same setting
- Recording only the attractive message flow and leaving STOP untested
RCS agent checklist#
- Compare the intended messages with the declared use case before submission
- Confirm that the website, privacy policy, and terms links work
- Test the opt-out flow from a recipient's device
- Record the declared use case and STOP behavior for reviewers
- Record which networks have approved the agent
Commonly confused with#
OnVoard's take#
Start with the messages the agent will actually send. Test STOP. Routes fail. Then record the recipient's whole path, including the request to stop. Give the launch reviewer enough evidence to assess the real experience, not just its most polished screen.