Cracking the Code: How to Get Your Shopify RCS Messaging Approved (and Avoid Carrier Rejections!)
Cracking the RCS Agent Description
The core issue bdotregan faced with the description field is that carriers aren't looking for marketing copy; they're looking for clear, concise, and purely transactional language. Think of it as a formal declaration of intent. Wsp's advice here is gold:
- Keep it Strict and Transactional: Your description should tell carriers exactly what kind of messages customers will receive and why. No fluff, no sales pitches.
- Follow this Template: Wsp provided a fantastic template that you can adapt. Remember that 100-character limit!
This RCS Business Messaging agent is used by [Business Name] to communicate with customers who have explicitly opted in. Messages include order updates, delivery notifications, booking confirmations, and customer support communications. All messages are service-related and are sent only after user consent. No unsolicited messages are sent.
If you *do* plan to send promotional messages (only to opted-in users, of course!), you'll need to add a very brief, clear statement:
Occasional promotional messages may be sent only to users who have explicitly opted in.
The trick here is to be as direct as possible. Carriers are trying to protect users from spam, so they want to ensure your agent is primarily for essential communications.
Your Privacy Policy: The Non-Negotiable Details
This is where many rejections happen, and again, the vagueness of the rejection makes it tough. Wsp laid out exactly what your privacy policy needs to include to satisfy carrier requirements. This isn't just general best practice; it's specific to RCS messaging.
1. Data Collection
You need to explicitly state what data you're collecting related to messaging. Don't assume. Clearly list:
- Phone numbers
- Opt-in information (proof of consent)
- Messaging interaction data (e.g., message delivery status, user replies)
2. Purpose of Data Usage
Explain *why* you're collecting this data. Again, be specific and tie it directly to the messaging service:
- Order notifications
- Customer support
- Service updates
- RCS messaging communication
3. Data Sharing Disclosure
This is a big one! Carriers need to know who else might see this data. You MUST include a statement like this:
We share necessary customer data with messaging providers, RCS platforms, and telecom carriers for the purpose of delivering messages.
This shows transparency and acknowledges the technical pipeline involved in sending RCS messages.
4. Opt-Out Method
Users need a clear, easy way to stop receiving messages. Your policy must state:
Users can opt out at any time by replying STOP or contacting support.
Make sure this is actually implemented in your messaging flow!
5. Contact Information
Finally, ensure your business email and a clear support contact method or page are easily found in your privacy policy.
Beyond the Text: General Compliance Tips
Wsp also shared some broader advice that's crucial for a smooth approval process:
Remove All Marketing Language
This ties back to the agent description. Carriers are hypersensitive to anything that looks like a promotional campaign. Avoid:
- Promotional tone
- Sales language
- Advertising claims
Your RCS agent isn't a billboard; it's a communication channel.
Make Opt-In Crystal Clear
Consent is paramount. Your opt-in flow on your website or wherever you collect consent needs to be unambiguous. Add a clear statement to your policy and ensure your process reflects:
Messages are only sent to users who have explicitly provided consent to receive communications.
This protects you and reassures the carriers.
The Resubmission Strategy: Patience is a Virtue
Once you've made all these changes, resist the urge to tweak things multiple times. Wsp advises:
- Submit Once: Make your changes, then submit.
- Avoid Repeated Changes: Don't make minor edits and resubmit immediately if you don't hear back. This can actually delay the process.
- Wait for Review: Give the carriers time to review. It can take a bit.
If All Else Fails: Escalate!
If you've followed all these steps and still get rejected, Wsp suggests requesting an escalation. Ask to have your case reviewed by the RCS compliance team or carrier review team. Specifically, ask them to review your agent description, privacy policy, and opt-in flow *together*. This can sometimes get you past a bottleneck with a standard reviewer.
It's clear from bdotregan's initial post that this process can feel like a black box, but Wsp's detailed breakdown really shines a light on what's needed. By being meticulously clear, transactional, and transparent in your descriptions and privacy policy, you significantly increase your chances of getting that RCS agent approved. It's all about playing by the carriers' rules, which are ultimately designed to protect consumers. Good luck, and let us know how these tips work out for you!
