U.S. Compliance Requirements
The CTIA and U.S. carriers have compliance requirements that must be met in order to launch a code or Agent on their network.
VIBES CONNECT ONE-SHEET COMPLIANCE GUIDE
CALL-TO-ACTION & MESSAGE COPY EXAMPLE GUIDE
DOCUMENTED COMPLIANCE REQUIREMENTS:
Google's Acceptable Use Policy- Google's AUP applies to all RCS programs
The CTIA Handbook - The requirements in this handbook apply to all U.S. messaging channels and are enforced by the U.S. carriers during provisioning. Aegis also issues with in market audits for live programs that are not in compliance with this handbook.
In addition to these published policies, some carriers also enforce unpublished requirements that apply to programs that will be running on their network.
ADDITIONAL COMPLIANCE RESOURCES:
KYC & Spam Mitigation Checks- This document outlines high risk content provider categories that are frequently impersonated by bad actors. For this reasons, programs that fall into those categories may no longer be accepted. Additionally, this document outlines the need for KYC brand vetting and checks suggested post launch.
Recommended Compliance Checks Post Launch This guide includes suggested compliance checks that Vibes recommends conducting post launch and any time a code receives an Unsolicited Message Audit (UMA) or Sev 0 violation.
Updated 24 days ago