10DLC Registration Isn't Consent: How to Wire A2P Brand, Campaign and STOP Into Your AI Receptionist Stack (2026)

Short answer: A2P 10DLC registration tells US carriers who you are and what you text. TCPA consent is a separate legal requirement about whether you may message that person at all. FCC order 26-67 then changes how STOP works once it takes effect. If you run an AI receptionist that also sends missed-call texts, you need all three wired into one stack: brand and campaign at the carrier layer, consent records in the CRM, and opt-out handling that reaches every workflow.

At Wrk Less we see the same mix-up on almost every build: a green registration checkmark treated as consent. Registration is deliverability infrastructure. Consent is permission. Mixing them up is how texts get blocked, or how you keep texting someone who already said stop.

This is how we build these systems, not legal advice. Have counsel review your message wording and consent language.

What is A2P 10DLC, in plain English?

Twilio's A2P 10DLC docs put it cleanly: Application-to-Person messaging is SMS or MMS where a person gets a message from an application, not from another person. 10DLC is a standard US 10-digit local number used for that traffic. US carriers built the A2P 10DLC program so commercial texts on local numbers are verified and consensual.

Telnyx's 10DLC overview adds the operating reality. Registration runs in a fixed order: brand, then campaign, then campaign review, then number assignment. Nothing commercial should send until the campaign clears. Unregistered 10DLC traffic has been blocked outright since February 3, 2025, according to that same overview. Your dashboard can still say "sent" while the handset gets nothing.

Toll-free and short codes sit outside 10DLC. Most small businesses we work with keep a local 10DLC number so the same line can take AI receptionist calls and send the text-back.

Brand vs campaign: what carriers actually check

Twilio splits registration into two records:

1. Brand — who is sending. Legal name, tax ID (or sole-proprietor path), address, website. The name has to match IRS records.
2. Campaign — what you send and how people opt in, opt out and get help. Sample messages, use-case type, consent description.

Telnyx's reviewer checklist is the same idea: live website with a privacy policy, three to five sample messages that match what you will actually send, and an opt-in process the reviewer can verify. Campaigns whose samples promise appointment reminders and then blast a sale get rejected. CTIA's Messaging Principles and Best Practices are the industry baseline carriers point to for consent, content and opt-out handling.

For missed-call text-back plus appointment reminders, we register a customer-care or mixed use case whose samples match the live templates. Marketing gets its own campaign and its own prior express written consent. Promo language in a "reminder" campaign fails review and turns the message into telemarketing under the TCPA.

Registration is not TCPA consent

This is the line owners miss.

Layer	What it answers	Who enforces it	What "pass" looks like
A2P 10DLC brand + campaign	Who are you, and what texts will you send?	Carriers via The Campaign Registry and your provider	Numbers attached to an approved campaign; traffic delivers
TCPA / state consent	May you message this person for this purpose?	Courts, FCC, state AGs (and plaintiffs)	Timestamped consent matched to message type
Opt-out handling (STOP)	Did you stop when they asked?	Same legal stack, plus carrier filtering	Suppression in every workflow within the deadline

A green brand status does not mean the caller who just rang your shop consented to marketing. A missed phone call is not a written marketing opt-in. Our missed-call text-back guide covers why the first automatic reply should stay informational: business name, how can we help, no promo. Marketing needs its own prior express written consent under the FCC's telemarketing rules.

Florida shops get a second track: the Florida Telephone Solicitation Act covers texts by name. Keep the automatic reply narrow, and make sure STOP stops every workflow.

Where FCC 26-67 fits

On September 30, 2026 the FCC adopted order FCC 26-67, released October 1. Nixon Peabody's October 7 alert summarizes the practical shift: informational opt-outs can be category-scoped, and businesses may designate an exclusive opt-out method (IVR/keypress, standardized reply keywords, or a designated website/phone) if they disclose it clearly on every call or text. Marketing opt-outs still kill all marketing. If reply text is your exclusive method, naming one keyword such as "Reply STOP to opt out" can satisfy disclosure, but you still must honor all seven standardized keywords: stop, quit, end, revoke, opt out, cancel, unsubscribe.

Not effective yet. The amendments take effect 30 days after Federal Register publication. As of mid-October 2026 that publication has not happened, so plan the wiring now and keep honoring the current "any reasonable means" / 10-business-day rules until the Public Notice lands. We break the full rule change down in The FCC Just Rewrote the Opt-Out Rules.

How we wire AI receptionist + text-back + CRM together

A typical Wrk Less build looks like this:

1. Voice on a dedicated or shared line. Retell (or a GoHighLevel native voice agent when that fits) answers, discloses it's AI where required, and handles recording notices when calls are recorded. See our disclosure rules.
2. Missed or abandoned call → one informational text. A webhook into n8n checks CRM opt-out fields, then sends through a Messaging Service whose numbers sit on an approved 10DLC campaign. Details live on our missed-call capture page and in the Retell webhook handoff write-up.
3. Consent fields by category. Appointment reminders, billing notices, and marketing are separate CRM fields. A marketing STOP never has to guess which bucket to clear.
4. One inbound STOP handler. Twilio or Telnyx inbound webhooks hit a single workflow that matches all seven keywords, updates every category that applies, and blocks that number in every sender. After FCC 26-67 is effective, the same handler can map category-scoped informational stops while still treating marketing as all-or-nothing.
5. Delivery failure alerts. Registration removes the unregistered block. It does not disable spam filters. We alert on failed delivery webhooks so a filtered template gets fixed in hours, not months.

After-hours AI answering follows the same pattern: overnight calls can book or take a message, and any follow-up text still checks the same consent and campaign records.

What registration fees look like (provider pass-through)

Fees move, and Wrk Less does not set them. Telnyx's published pass-through baseline is useful for planning: EIN brand registration $4.50 one-time, campaign review $15 per submission, standard campaign $10 per month, low-volume mixed $1.50 per month, optional standard vetting $41.50 per request (Telnyx, What Is 10DLC). Carrier per-message surcharges stack on your provider's SMS rate. Confirm live numbers in your console before you budget.

Checklist before you turn on missed-call text-back

• Legal brand name matches the EIN filing (or you used the sole-proprietor path correctly)
• Campaign use case matches the live message content, not your industry label
• Sample messages include brand name, HELP, STOP, and "message and data rates may apply" language your provider requires
• Every sending number is attached to the approved campaign
• First missed-call text is informational only; marketing consent is a separate written capture
• CRM stores consent by message category with timestamps
• One webhook handler recognizes all seven STOP keywords and suppresses across every workflow
• AI receptionist disclosure and recording notices are in the voice script
• Delivery-failure webhooks page someone, not just a log
• Counsel has reviewed category map and opt-out disclosures ahead of FCC 26-67's effective date

Ready to wire registration, consent and STOP together?

If your AI phone agent and text-back live in different tools that do not share opt-outs, that is the gap we close. Wrk Less builds the AI receptionist, missed-call capture and CRM sync so brand registration, consent fields and STOP handling sit in one place.

Book your AI systems assessment and we will map your current numbers, campaigns and consent records on the call. Or contact Wrk Less if you already know which workflows are leaking opt-outs.