RingCentral Compliance Guide

RingCentral Customer Care
Campaign Guide

Master the strict requirements for the "Customer Care" use case. Learn how to separate support from marketing to avoid 10DLC rejections.

What is "Customer Care" in RingCentral?

In the RingCentral ecosystem, the Customer Care use case (often grouped with "Conversational") is strictly defined as messaging that supports an existing customer relationship or transaction. It is NOT for customer acquisition or re-engagement.

The Marketing Trap

The #1 reason RingCentral Customer Care campaigns are rejected is the inclusion of "soft marketing." Words like "upgrade," "discount," "save," "check out," or "refer" will trigger automatic content filters.

Core Characteristics

Initiation

Typically initiated by the customer (inbound) or triggered by a specific customer action (transaction).

Content

Factual, support-oriented, and reactive. Answers questions or provides status updates.

Consent

Can often be implied from the transaction context (e.g., "Text me support"), but opt-out is still required.

Dos and Don'ts

Compare these compliant and non-compliant samples to understand the boundary line.

✅ Compliant Sample
"Hi [Name], this is [Brand] Support. We received your ticket #1234 regarding billing. An agent is reviewing it now. Reply STOP to opt out."
  • Identifies Brand
  • Directly addresses a request
  • Clear opt-out language
❌ Rejection Trigger
"Hi [Name], thanks for contacting [Brand] Support. While you wait, check out our new summer sale at [Link]! 20% off today only."
  • "Summer sale" = Marketing
  • "20% off" = Marketing
  • Missing STOP language

Specific RingCentral Requirements

RingCentral imposes specific validation rules for Customer Care campaigns that differ slightly from general TCR guidance.

Help Keyword Mandate

Even if it's a support campaign, you MUST include "Reply HELP for help" instructions in your sample messages or campaign description. RingCentral validators check specifically for this.

Link Hygiene

Avoid public URL shorteners (bit.ly, tinyurl). Use your full domain or a branded shortener. Links must lead to pages related to the support topic (e.g., knowledge base, account portal), NOT sales pages.

Registration Steps

Follow this workflow in the RingCentral Admin Portal.

1

Navigate to Admin Portal > Phone System > Regulations > 10DLC Registration.

2

Under "Campaigns", click Register New Campaign.

3

Select "Customer Care" from the Use Case dropdown. (Note: Avoid "Conversational" unless it is strictly peer-to-peer with zero automation).

4

In the "Campaign Description" field, explicitly state: "This campaign is for responding to customer inquiries and support tickets initiated by the customer."

5

Enter 3 unique sample messages that follow the "Compliant Sample" guidelines above.

Validate Before You Submit

Don't risk a $15 rejection fee. Use our Message Validator to scan your Customer Care samples for hidden marketing language.

Run Message Validator

RingCentral Care FAQ

Can I ask for a review in a Customer Care message?
It's risky. "How was our service?" is generally okay, but "Rate us and get 10% off" is marketing. Keep feedback requests strictly about the support quality, not incentives.
Does Customer Care allow high throughput?
Typically, no. Customer Care use cases are usually approved for lower throughputs (e.g., 60 messages/minute) because they are assumed to be manual or reactive, not bulk broadcasts.
What if I have both support AND marketing messages?
You must register a "Mixed" or "Marketing" campaign. Or, better yet, register two separate campaigns in RingCentral and assign different phone numbers to each to protect your support line's deliverability.

This content provides general information about RingCentral Customer Care campaigns and TCR compliance. It does not constitute legal advice. Compliance requirements vary based on message content and carrier policies. Organizations should consult qualified legal counsel for guidance on TCPA/CTIA compliance. MyTCRPlus does not provide legal advisory services.