How to Onboard an RCS Agent with YakChat | Yakchat Help

How to Onboard an RCS Agent with YakChat

This article provides detailed steps and requirements for onboarding an RCS (Rich Communication Services) Agent with YakChat. It explains the role of an RCS Agent, required brand information, compliance guidelines, and carrier-specific onboarding processes for the US and Canada.

RCS Onboarding Guidelines

Follow these steps and guidelines to set up an RCS Agent for your organization through YakChat.

Step 1: Understand RCS Agents

  1. An RCS Agent is a verified, branded profile representing your business in the RCS ecosystem.
  2. This profile includes your brand name, logo, design elements, and verified details for customer trust and recognition.

Step 2: Review Onboarding Timelines and Process

  1. YakChat partners with Twilio as the official RCS Service Provider.
  2. All submissions and approvals pass through Twilio, Google, and carrier reviews.
  3. Onboarding typically takes 4-6 weeks per brand due to manual validation by multiple parties.

Note: This process ensures authenticity and integrity across mobile networks and platforms.

Step 3: Gather Core Brand Information

  1. Display Name - The name shown to users (must be unique per sender).
  2. Brand Description - Brief overview of your business or messaging profile.
  3. Logo Image - JPG/PNG, 224x224 px, <50KB.
  4. Banner Image - JPG/PNG, 1440x448 px, <200KB.
  5. Accent Color - Hex code with minimum 4.5:1 contrast ratio.
  6. Contact Details - At least one phone number (E.164 format) or email address.
  7. Privacy Policy URL - Published in the primary region language(s).
  8. Terms of Service URL - Published and accessible.

Step 4: Fulfill US Carrier-Specific Requirements

Additional information is needed for AT&T, Verizon, and T-Mobile approvals:

  1. Campaign Description and expected message types.
  2. Opt-in and opt-out message samples.
  3. Existing messaging programs (Short Code, Toll-Free, or 10DLC) and monthly SMS volume.
  4. Estimated RCS traffic and existing website traffic data.

Note: Onboarding for the US and Canada involves separate submissions for each country.

Step 5: Fulfill Canadian Carrier Requirements

  1. Campaign and use case descriptions.
  2. Opt-in details and sample keyword-triggered messages.
  3. Company legal information and expected RCS traffic.

Step 6: Provide Message Trigger and Use Case Details

  1. Message Trigger Description - Explain when and why messages are sent (max 1000 characters).
  2. Use Case Description - Primary and secondary use cases, expected interactions (max 1000 characters).
  3. Use Case Video - Include a 30-90 second video URL showing consent, sample messages, and opt-out process.

Step 7: Meet Compliance Requirements

  1. Follow CTIA Short Code Guidelines for opt-in, privacy, and terms.
  2. Ensure proper disclosures, consent collection process, and links to Terms and Privacy Policy.
  3. Include specific language in the Privacy Policy to protect opt-in data (e.g., messaging consent data is not shared or sold).
  4. Include program name, frequency, STOP/HELP instructions, privacy link, and liability disclaimer in the Terms of Service.

Tip: Incomplete or inaccurate documentation can delay approval. Review all requirements carefully before submission.

Onboarding Form

Complete this onboarding form link here and coordinate with one of our Support team members for assistance.


Related Articles