RCS Campaign Compliance

This guide helps you create compliant RCS campaigns for carrier and Google approval. All RCS campaigns require explicit user consent, clear agent behavior descriptions, and proper keyword responses.

---

CTA Language (Opt-In Disclosure)

The ctaLanguage field contains the required text that appears next to your opt-in checkbox. This checkbox must be unchecked by default.

---

Opt-In Terms and Conditions

The optInTermsAndConditions field describes how you acquire user consent. Include the method and any relevant URLs.

Your description should include:

1. How users opt in (paper form, website, app, etc.)
2. Where the opt-in form lives (URL or physical location)
3. What users agree to when opting in
4. How consent is recorded (submission method)

---

Carrier Description

The carrierDescription field explains your agent’s purpose to carriers during review. Be specific about your target audience and message types.

Your description should include:

1. Who you’re messaging (target audience)
2. What industry/use case your messages serve
3. What types of messages users will receive

---

Use Case Behavior

The useCase.behavior field provides a detailed summary of what your brand is and how the RCS agent will be used.

Your behavior description should include:

1. What your brand/company does
2. The agent’s primary purpose (onboarding, support, notifications, etc.)
3. Types of content delivered (operational updates, educational content, etc.)
4. Message frequency and what triggers messages

---

Expected Agent Responses

The expectedAgentResponses field lists 1-5 example messages your agent might send to users. These help reviewers understand your agent’s communication style.

Requirements:

• Provide 1-5 example responses
• Show the variety of messages your agent sends
• Include responses for different scenarios (help, booking, confirmations, etc.)

---

Agent Triggers

The agentTriggers field explains how and when your agent sends messages. Describe the full flow from initial contact to ongoing interactions.

Your description should include:

1. How the first message is delivered (user subscription, action, etc.)
2. Whether messages follow a schedule or are triggered by user actions
3. Any external triggers (reminders, system events, etc.)

---

Interaction Description

The interactionDescription field describes all agent interactions, including primary and secondary use cases.

Your description should include:

1. Primary interactions (main purpose of the agent)
2. Secondary interactions (supporting features)
3. Other interactions (additional capabilities)

---

Demo Trigger

The demoTrigger field provides instructions for external reviewers to test your agent. This helps carriers verify your agent works correctly.

Your instructions should include:

1. How to trigger the agent (inbound text message, keyword, etc.)

---

Keyword Response Messages

Configure automatic responses for when users text keywords to your RCS agent. These are required for compliance.