5 Reasons Your 10DLC Campaigns Get Rejected (and How to Fix Them!)

Getting your 10DLC (10-digit long code) campaigns approved for A2P (application-to-person) messaging can be a frustrating process. Don’t worry, you’re not alone! In this post, we’ll uncover the top-5 reasons why your campaigns might be getting rejected and how to turn those rejections into approvals ✅. This post was inspired by a YoutTube video on our channel, you can check it out Here.

First, a quick 10DLC recap:

10DLC numbers are standard US phone numbers used for business texting. A2P messaging is when an application sends a message to a person’s mobile device. To send these messages, you need to register your brand (company) and campaign(s) (use case) with The Campaign Registry (TCR).

Now, let’s dive into those pesky rejection reasons:

#5: EIN Mismatch

This is a common issue during the brand verification stage. Make sure the EIN you provide matches your company’s legal name and the IRS database. You can find your EIN on your W-2, SS-4, or W-9 forms. If you’re part of a larger organization, use the parent company’s legal name and add your subsidiary as a ‘DBA’ and use their EIN.

• Pro Tip: When dealing with subsidiary companies, remember the phrase “register the brand, not the brand behind the brand.” This means the entity that is sending the messages is the entity that needs to be registered.

#4: Missing Use Case in Website CTA

When someone opts in to receive messages on your website, your call-to-action (CTA) must clearly state the type of messages they’re consenting to (e.g., marketing, customer care).

• Pro Tip: If your campaign is a mixed use campaign, and marketing is one of the uses, then you must have marketing listed as a separate use case (and get separate approval).

#3: Mismatched Email Domains

Your support email domain should match your website domain. Using generic email addresses like Gmail or Yahoo might lead to rejection.

• Pro Tip: You must also do this in your “help” message (if you’ve included a support email rather than a support number).

#2: Privacy Policy Issues

Your website’s privacy policy must explicitly state that you limit sharing SMS opt-in data with third parties for marketing and promotional purposes. You can either state that you don’t share this data at all or specifically exclude SMS opt-in data from any data sharing.

• Pro Tip: Ensure that your privacy policy is linked within your website CTA. This creates a clear and traceable path for reviewers.

#1: Incomplete Website CTA

Your website CTA needs to include the following six elements:

• Who: Your legal company name
• What: The type of messages
• When: Message frequency
• Where: Link to your privacy policy
• How: Instructions for getting help and opting out (e.g., “text HELP” or “STOP”)
• Cost: Either the specific cost or “message and data rates may apply”

Pro Tip: Double-check all information for accuracy and clarity before submitting your campaign for approval.

By addressing these common issues, you’ll increase your chances of getting your 10DLC campaigns approved and avoid the frustration of rejections. If you have any questions or need assistance, reach out to your messaging provider or consult with a 10DLC expert.