{"id":1185,"date":"2026-10-27T05:55:22","date_gmt":"2026-10-27T05:55:22","guid":{"rendered":"https:\/\/blog.easify.app\/blogs\/?p=1185"},"modified":"2026-10-27T05:55:22","modified_gmt":"2026-10-27T05:55:22","slug":"10dlc-rejection-reasons","status":"publish","type":"post","link":"https:\/\/blog.easify.app\/blogs\/10dlc-rejection-reasons\/","title":{"rendered":"10DLC Rejected? Common Reasons and How to Fix Each One"},"content":{"rendered":"

A 10DLC rejection means a reviewer turned down your brand or campaign registration. Most rejections point to a fixable gap (an EIN that doesn’t match your legal name, a vague consent description, a missing privacy policy), and you can resubmit once it’s fixed. Three kinds can’t be fixed by resubmitting the same campaign.<\/p>\n

This post lists the common rejection reasons, what each one means, the fix, and whether you can resubmit. It also shows what a rejection looks like when Easify registers for you.<\/p>\n

What a 10DLC rejection tells you<\/h2>\n

Every business that texts US numbers from a regular 10-digit number registers twice: once as a brand<\/strong> (who you are, checked against your tax records) and once per campaign<\/strong> (what you send, to whom, and how they agreed). A rejection can happen at either step, so first check which one failed.<\/p>\n

Each provider labels rejections in its own way, but the reasons behind them follow the same industry and provider norms. Match your rejection by the reason, not the label.<\/p>\n

EIN mismatch and business identity rejections<\/h2>\n

These rejections mean your business details don’t match official records. A tax ID mismatch stops the brand itself, so you can’t create a campaign until it passes. A name mismatch or too many brands on one EIN rejects a campaign because of the brand behind it.<\/p>\n

\n\n\n\n\n\n\n\n
Reason<\/th>\nWhat it means<\/th>\nThe fix<\/th>\nResubmit?<\/th>\n<\/tr>\n<\/thead>\n
Tax ID data mismatch<\/td>\nThe EIN doesn’t match the legal company name, the EIN is invalid, or an SSN was entered instead of an EIN.<\/td>\nCopy the EIN and legal name exactly from your IRS letter, then resubmit. If they already match, appeal with the document.<\/td>\nYes<\/td>\n<\/tr>\n
DBA name doesn’t match legal name<\/td>\nThe campaign, website or sample messages use a trade name that isn’t on the brand registration.<\/td>\nUse the exact legal name, add your DBA to the brand, and make the website and samples name the same business.<\/td>\nYes<\/td>\n<\/tr>\n
Excessive EIN<\/td>\nThe same EIN is behind too many brand registrations, with no clear business reason.<\/td>\nRemove duplicate brands and run new campaigns under your existing approved brand. Fix the brand first, then resubmit.<\/td>\nAfter the brand is fixed<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

How to fix an EIN mismatch<\/h3>\n

Check what you typed before you assume a tax problem. Work through these in order:<\/p>\n

    \n
  1. Find your IRS confirmation letter: the CP 575 notice or a 147C letter. Providers check against the name on these, not the name on a W-9.<\/li>\n
  2. Enter the legal name character for character, including “LLC” or “Inc.” and the same punctuation.<\/li>\n
  3. Enter the 9-digit EIN, not a Social Security number.<\/li>\n
  4. Put your customer-facing name in the DBA field, not the legal name field.<\/li>\n
  5. If the EIN is only weeks old, the records may not have caught up yet. Keep the IRS letter ready for a manual review.<\/li>\n<\/ol>\n

    Campaign rejections: when campaign vetting fails<\/h2>\n

    “Campaign vetting failed” means the brand passed but a reviewer rejected what you plan to send. Most vetting rejections come down to two things: how people consent, and what your website shows.<\/p>\n

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Reason<\/th>\nWhat it means<\/th>\nThe fix<\/th>\nResubmit?<\/th>\n<\/tr>\n<\/thead>\n
    Invalid campaign description<\/td>\nThe description doesn’t say who sends, who receives, and why, or it doesn’t match the samples.<\/td>\nName your business, the recipients and the purpose in plain words. Remove personal details.<\/td>\nYes<\/td>\n<\/tr>\n
    Opt-in error<\/td>\nThe reviewer can’t see who opts in, where, or how consent is collected.<\/td>\nList every opt-in method with a public link or a hosted screenshot. Keep consent specific to this campaign.<\/td>\nYes<\/td>\n<\/tr>\n
    Message flow or call to action incomplete<\/td>\nThe consent path is described too briefly to verify, or a keyword opt-in leaves out the keyword or number.<\/td>\nDescribe each opt-in path end to end. Any consent checkbox must be optional and unchecked. Show frequency, “message and data rates may apply”, STOP and HELP.<\/td>\nYes<\/td>\n<\/tr>\n
    Compliant privacy policy required<\/td>\nNo privacy policy found, more than one, or one that allows sharing mobile numbers for marketing.<\/td>\nPublish one public policy that says mobile numbers and consent aren’t shared with third parties for marketing.<\/td>\nYes<\/td>\n<\/tr>\n
    Terms and conditions URL required<\/td>\nThe submission has no link to your terms and conditions, which many providers now require.<\/td>\nPublish a terms page that loads without a login and submit its HTTPS link.<\/td>\nYes, as a new submission<\/td>\n<\/tr>\n
    Invalid website URL<\/td>\nThe site was down, the URL was wrong, or the site shows no way to opt in.<\/td>\nMake the site public and working. For a pre-launch site, link a public screenshot of the opt-in.<\/td>\nYes<\/td>\n<\/tr>\n
    Opt-out error<\/td>\nThe submission doesn’t show how people stop messages, or the opt-out reply doesn’t confirm it.<\/td>\nDescribe how to opt out and add an opt-out reply that names your brand and confirms no more texts will come.<\/td>\nYes<\/td>\n<\/tr>\n
    Sample messages don’t match use case<\/td>\nSamples are missing, vague, or about something other than the campaign.<\/td>\nWrite at least two real samples. Put variables in [brackets]. Include your business name and an opt-out line in at least one.<\/td>\nYes<\/td>\n<\/tr>\n
    Public URL shortener in samples<\/td>\nA sample uses a shared shortener such as bit.ly, or an unsecured link.<\/td>\nUse your own domain, over HTTPS, or a branded short link.<\/td>\nYes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Rejections you can’t fix by resubmitting<\/h2>\n

    Three kinds of rejection are about the use case itself, not the paperwork. Editing the same campaign won’t clear them. Your options are an appeal, if you think the reviewer got it wrong, or a new campaign with a materially different use case.<\/p>\n