Why Your 10DLC Registration Got Rejected

Your 10DLC registration got kicked back. Annoying, but it's not a black box... the reviewers tell you exactly what to fix. The catch is that the guidance you read going in doesn't cover half of what gets flagged. So the first rejection always lands as a surprise, and usually on language you were sure was fine..

We've taken two clients through this recently. One in telehealth, one in commercial water filtration. Completely different businesses, and the rejections rhymed. That's the useful part... this isn't about your industry, it's about your language. First, some context that explains why the review feels the way it does.

You're not really registering with HubSpot

HubSpot doesn't run SMS. Twilio does, and HubSpot files your brand and campaign registration with The Campaign Registry through them.

Which means three parties sit between you and a delivered text. HubSpot owns the interface. Twilio owns the connection and its own messaging policy, including a forbidden-categories list that applies to you regardless of what HubSpot allows. And the carriers own the final yes.

This matters practically. When your registration comes back rejected, the feedback originates several layers down and gets passed back up. It reads terse because it is terse. It's also why "but HubSpot let me set it up" isn't an argument that goes anywhere.

Marketing SMS and transactional SMS are two different products

This is the distinction that causes more rejections than anything else, and HubSpot's own structure reflects it. There are two separate setup paths, two separate registrations, and two separate numbers.

Marketing SMS is promotional. Offers, product news, campaign sends, anything encouraging a purchase. It runs through workflows and requires explicit marketing opt-in.

Transactional SMS is operational. Order confirmations, appointment reminders, shipping updates, password resets. Different consent basis, different registration.

HubSpot built the marketing side first and it's still the mature product. Transactional came later. If you're setting up now, treat them as genuinely separate builds rather than two settings on one thing.

The failure mode is teams who think of SMS as one channel, write consent language covering both, and submit it as a marketing campaign. Carriers call that mixed-use and reject it. Which is reason number one.

1. "Informational" is a dirty word

One client's opt-in checkbox said "marketing and informational text messages." Seemed comprehensive. It's the fastest way to get flagged as mixed-use, because carriers scan for anything outside marketing or promotional and reject it.

Strip the consent language to marketing only:

I agree to receive recurring automated marketing text messages from [Brand] at the mobile number provided. Consent is not a condition of purchase.

If you also send transactional SMS, register it separately. Don't bundle.

2. Implied consent won't pass where explicit is required

"By submitting this form you agree to receive texts" is implied consent. Carriers want an affirmative action tied specifically to SMS. A checkbox, unchecked by default, with the consent language sitting right next to it.

HubSpot's own messaging team calls missing or unclear consent details the number one cause of 10DLC rejections.

3. Your sample messages have to actually be marketing

Here's a sample that got rejected:

[Brand]: Thanks for your interest in [Brand]. I just left you a voicemail and wanted to reconnect. Please call me back when you have a chance. To opt out, reply STOP.

Reads friendly. Also reads transactional. That's a service follow-up, and carriers don't care what checkbox the contact clicked. They read the content.

Marketing messages promote something. Offers, product information, promotional content. This is the shape that clears:

[Brand]: Hi [first name], enjoy a limited-time offer on [product] this month. [Benefit line]. Learn more: [url] Reply STOP to opt out, HELP for help.

If your sample sounds like a rep chasing a lead, it's the wrong sample. Which is also a hint about what the tool is for.

4. "See our Terms of Service" isn't enough

One client's form disclosure referenced Terms and Privacy Policy as plain text. Rejected. Both have to be live, clickable, inline hyperlinks inside the disclosure itself. Not links parked in the footer.

5. Verbal opt-ins need the full URLs spoken aloud

If reps collect SMS consent on the phone, "you can find our Terms on our website" doesn't meet the standard. The script needs the URLs said out:

You can find our Terms of Service at [brand] dot com slash terms-and-conditions, and our Privacy Policy at [brand] dot com slash privacy-policy.

Clunky. Say it anyway. And log the consent... date, time, phone number, which rep, and confirmation the script was read.

6. The no-sharing clause is non-negotiable

Every Privacy Policy behind a registered marketing SMS campaign needs this concept in it. HubSpot's guidance specifies that your Privacy Policy must not state SMS opt-in data is shared with third parties, and if data sharing appears elsewhere in the policy, you need a disclaimer stating that text messaging originator opt-in data and consent will not be shared with any third parties, excluding aggregators and providers of the text message services.

Paraphrase it loosely and you'll be resubmitting. Keep the words.

What changed recently

HubSpot now sets the marketing campaign use case up automatically, and they require examples attached for every opt-in method you select. Screenshots for keyword campaigns, online forms, offline forms, and scripts.

Checking the box without the evidence is its own rejection now.

Who's actually judging you

Worth understanding, because it explains the tone of the feedback.

The CTIA principles aren't federal regulation, and no agency enforces them directly. Carriers enforce them operationally by filtering, throttling, or blocking, and The Campaign Registry implements them as the practical gatekeeper for A2P traffic. A campaign that fails CTIA standards fails registration, which means your messages never deliver.

So this isn't a legal review. It's a delivery review, run by people who've seen every trick and read your submission literally.

What HubSpot SMS actually costs

Worth knowing before you spend three weeks on registration.

The Marketing SMS add-on runs $75 a month for 1,000 message segments, with each additional block of 1,000 at $25 a month. Unused segments don't roll over.

Segments, not messages. Standard SMS is 160 characters, and anything longer splits into multiple segments. A 200-character message costs you two. Emoji and special characters can drop the limit further. So a team sending five messages to a list of 250 contacts can burn the base allotment in a single campaign.

Run the math at your real volume. A campaign sending two segments to 5,000 contacts is 10,000 segments, which is the base tier plus nine add-on blocks. That's $300 a month for one monthly send.

The add-on also requires Marketing Hub Professional or Enterprise. Starter isn't eligible. So the real floor is the Hub subscription plus $75, which puts native SMS meaningfully north of what the add-on price suggests.

A few other limits worth knowing upfront: US-based numbers only, sending to US and Canada numbers only, one number per account, and a forbidden-categories list that rules out certain industries entirely.

None of that makes it a bad product. It makes it a specific product, built for scheduled marketing sends to an opted-in list. If what you actually need is reps having two-way conversations from deal records, that's a different tool and you should figure that out before registration, not after.

Pricing as of August 25, 2026. Check HubSpot's pricing page before you budget.

If you're in a regulated industry, there's a second stack

Everything above is carrier and TCPA compliance, and it applies to everyone.

If you're in healthcare, HIPAA sits on top of it with its own authorization requirements. Clearing 10DLC doesn't clear that. Different rules, different records, both required.

What we'd do differently

Decide upfront whether you're running marketing SMS, transactional SMS, or both, and register them separately from the start. Trying to cover both in one campaign creates a documentation trap where your Privacy Policy and Terms have to describe every message type separately, and every mention of "informational" or "order updates" becomes another rejection risk.

Then model your actual segment volume before you commit. Character count times send frequency times list size. Do that math once and it changes what you build.

And ask your HubSpot rep to pre-review your exact language and sample messages before you resubmit. Three rounds of async feedback beat one more full rejection cycle.

Resources

• HubSpot: Set up SMS messaging for marketing communications. The registration flow and timelines.

• HubSpot: Set up SMS messaging for transactional communications. The separate path, and the one people miss.

• HubSpot Community: New 10DLC SMS registration requirements. Posted by HubSpot's messaging team, the most current source on what carriers want.

• Twilio: A2P 10DLC documentation and Messaging Policy. The layer underneath HubSpot, including forbidden categories.

• CTIA: Messaging Principles and Best Practices. The standards carriers enforce.

• The Campaign Registry. Where brand and campaign registration lives.

• FCC: 47 CFR 64.1200. The TCPA delivery restrictions.

Plan around six to eight business days for 10DLC registration, and eight to twelve weeks for short codes. Build that into your launch timeline before you promise anyone a send date.

Every rejection on this list came from language somebody thought was safe. Carriers read literally, so write for that reader and the review gets short.

Current as of August 25, 2026. Carrier requirements and pricing both change, and this one moves faster than most.