Category
Systems & Compliance
Publish Date
1 November 2026
The reminder fired on time. The homeowner never got it. When a solar dealer's texts stop landing, look at registration first and consent second: a business number that isn't registered for A2P 10DLC, or an opt-in nobody can verify.
Why your texts aren't landing
Picture a dealer who switches the ads on in a new state. Leads come in, the booking flow fires its confirmation texts, and the closers' calendars start to fill. Then the no-shows start. The setter calls one of them: “Did you get our text?” And the homeowner's like, “What text?”
The first place to look is registration. A2P 10DLC is the standard US carriers put in place so business texting from ordinary local numbers is verified and consensual. That's how Twilio describes it, and Twilio's error documentation says it blocks messages to US numbers sent from a 10DLC number that isn't tied to an approved A2P 10DLC campaign. So on a platform like that, it's not that your texts are slow, right? They're not going anywhere.
The second place to look is consent. Registration helps, and Twilio says registered traffic sees lower message filtering and higher throughput, but a registered number can still get filtered. HighLevel's guide to failed texts lists what can get a message filtered: content, sender identification, consent, links, prohibited content, spam signals and carrier rules. And CTIA's Messaging Principles and Best Practices, the wireless industry's voluntary guidance for business texting, says senders shouldn't text opt-in lists that were rented, sold or shared, and that an opt-in applies only to the sender it was given to. A bought list fails that before the first message goes out.
Registration gets you through the door. Consent decides whether you get to stay.
What A2P 10DLC actually is
A2P means application to person: software texting a human, not you texting your cousin from your own phone. 10DLC is the 10-digit long code, an ordinary local number. Put them together and you've got your CRM texting homeowners from a local number, which is exactly what a solar dealer's booking flow does all day.
Registration runs in order. First the brand, which is who's sending: your dealership, its legal name, its tax ID and its business details, so the carriers know you're a legitimate sender. You don't file this with the registry yourself. The Campaign Registry, which describes itself as the backbone of the 10DLC messaging ecosystem, only takes brands through a registered provider, so it goes in through your texting platform.
Then the campaign, which is what you'll send. HighLevel's registration guide puts it plainly: explain who sends the messages, who receives them, what messages are sent and how contacts opt in. You add realistic sample messages, the address of the page where people opt in, and links to your privacy policy and terms. And the campaign comes after the brand is approved, not alongside it.
The brand says who you are. The campaign says what you'll text, who to, and how they said yes. That's it.
The day zero rule
A common mistake isn't technical at all. It's order. A dealer builds the funnel, the calendars and the automations, gets the ads ready, and only then opens the registration form.
Everything else in a launch moves at your pace. You can build a page in an afternoon. Registration doesn't work like that. Once you submit, the campaign sits with reviewers who have no idea your ads go live next week, and if it comes back rejected, you fix what they flagged and go again.
Now what's that going to do? The ads are spending, homeowners are booking, and the confirmation text that should've landed the minute they booked never went. Your setter's calling people who've half forgotten the form. They're going to be like, “Who's this? What form did I fill in?”
So the rule is simple. Registration starts the day the business details land, not the day the build finishes. Run them side by side and neither waits on the other. Start registration last and its whole wait lands on top of your launch, right when the leads are freshest. Day zero. Simple as that.
The Day-Zero Registration Sequence
This is the Empire OS order for getting texting approved before a dealer's funnel goes live. It's the order we follow on our own number, and it runs like this.
First, collect the business identity: the legal name, the tax ID and a support email on the business's own domain. HighLevel's list of campaign rejections includes a contact email on a personal domain like Gmail or Yahoo, so sort that out before anything else.
The next thing is the pages the reviewers check, built before you register. The opt-in form carries a consent line that names your dealership, with appointment messages and promotional messages as 2 separate checkboxes and neither one ticked in advance. That same rejection list covers each of those: marketing consent that isn't collected separately, a pre-selected checkbox, and texting consent bundled into mandatory terms. The privacy policy says mobile information isn't shared with third parties for marketing, and the terms carry the STOP and HELP language.
Then register: the brand first, then the campaign, with a description specific enough that a reviewer can picture the conversation. Who gets the messages, say homeowners who asked for a solar consultation on your form. What the messages say: confirmations and reminders, plus promotional messages for the people who ticked that box. And how consent was collected. The sample messages have to match that description.
While it's pending, follow-up messages go by email only, your setters keep calling, and every text automation sits built but paused.
Lastly, the day the campaign's approved, switch every text automation on in one pass and log the date. One pass, because a half-switched build is how you end up with reminders firing and confirmations not. Then run a test contact through the whole flow that same day, so you see the confirmation land on a real phone before a homeowner needs it.
Registration isn't consent
One thing to be clear on. Registration gets your messages through the carriers' door. It doesn't decide who you're allowed to text. In the US that's the job of the consent rules: the TCPA, the FCC's rules under it, and state laws on top. In Texas, for example, a sales text has counted as a telephone solicitation under the state's telephone solicitation law since 1 September 2025. And build it so a STOP reply suppresses every channel, not just the one the homeowner replied on.
This is education for US dealers, not legal advice. Have your counsel read your consent line, your privacy policy and your campaign description before you submit, and check them again on a schedule, because the rules move.
Get it built before the first ad
You can run this yourself. Collect the identity, build the pages, register in order, follow up by email while you wait, and switch the texts on in one pass.
Or we can build it for you. Empire OS builds the consent capture and the texting registration into the funnel, so your team only contacts homeowners through a flow built to the rules, and your counsel still rules on the rules. It's all built inside your own CRM and accounts, so the records stay with your dealership. The sit system's confirmations and reminders then run inside the same consent rules, by the homeowner's state.
What you're after is qualified homeowner appointments sitting on your closers' calendars, market after market, from a flow you own, with texts that actually land.
If that's where you want to get to, book a call below and we'll see how we can help.
