Compliance

The Compliant Texting Playbook: A2P 10DLC, Explained for Advisors

The Swivel Team May 14, 2026 6 min read

Your clients already live in their text messages. They reply to a "your application is ready to sign" text in minutes, while the same note sits unread in their inbox for days. Texting works. But business texting in the US runs on rules that personal texting doesn't — and if you ignore them, your messages get filtered, blocked, or flagged in a regulated industry where every communication is on the record. The good news: the rules are straightforward once someone explains them in plain English. Here's the playbook.

What A2P 10DLC Is — and Why It Exists

A2P 10DLC stands for "application-to-person, 10-digit long code." Translated: it's the framework US mobile carriers use for business texting sent from a normal 10-digit phone number — the kind your clients see every day, not a short code or a 1-800 line.

Here's the part that trips advisors up. The carriers (Verizon, AT&T, T-Mobile, and the rest) now require any business sending application-to-person texts to register first. Registration tells the carriers who you are, what kind of messages you send, and that you're a legitimate business rather than a spammer. It exists because carriers spent years drowning in scam and spam texts, and 10DLC is how they cleaned it up.

What happens if you skip it? Unregistered business texts get filtered or blocked outright. You hit "send," your client never sees it, and you have no idea the message didn't land. For an advisor chasing a signature or confirming a meeting, silent failure is the worst outcome there is.

The registration itself is a one-time setup: you provide your business details (legal name, EIN, website) and describe how you'll use texting. It's paperwork, not a hurdle — and it's the price of admission for reliable delivery. A good platform handles this with you instead of leaving you to decode carrier portals on your own. Swivel's built-in texting walks you through 10DLC registration as part of getting set up, so your number is properly registered before you send a single message.

Consent: Get the Opt-In Before You Text

Registration gets your messages through the carriers. Consent keeps you compliant and keeps your clients happy.

The rule is simple: get permission before you text someone for business. Consent — also called opt-in — means the person agreed to receive texts from you. That can come from a checkbox on your intake form, a line on your engagement agreement, a reply of "YES" to a confirmation text, or a verbal okay you log. What matters is that you can show the person said yes.

A few practices that keep you on solid ground:

  • Capture opt-in explicitly. A form field or signed disclosure beats "they gave me their cell, so I assumed it was fine."
  • Tell them what to expect. Appointment reminders, paperwork notifications, the occasional update — set expectations up front.
  • Honor opt-outs immediately. If someone replies STOP, the texting stops. No exceptions.
  • Track consent per contact. You need to know who said yes, not just that "clients in general" agreed.

Swivel manages SMS opt-in at the contact level, so each client record carries its own consent status. You're never guessing whether a given person is cleared to receive a text.

Archiving: Texts Are Business Records Now

Here's where the regulated part of your world meets the texting part. When you text a client about their annuity application, their beneficiary change, or their next review, that message is a business communication — and in a regulated industry, business communications are records you may need to produce.

That means the casual, disappearing nature of personal texting is exactly the wrong model. You can't have client conversations vanishing into a personal phone with no trail. You need every message captured, stored, and tied to the right client.

This is the single biggest reason not to run client texting off your personal cell:

  • No archive. Personal texts aren't retained in any system you control.
  • No client record. A text on your phone isn't logged against the client it concerns.
  • No oversight. Nobody — not a compliance reviewer, not future you — can reconstruct what was said.

Swivel archives messages for compliance and logs every text to the client record automatically. The conversation lives where the rest of the client's file lives, so the message about their application sits right next to the application itself. When you need to show what was communicated and when, it's there.

(One light note: this is practical compliance hygiene, not legal advice. Your firm's compliance team or BD/RIA has its own requirements, so confirm the specifics with them.)

The Practical Playbook

Put it together and compliant texting comes down to a handful of moves you set up once and then run on autopilot:

  • Register for 10DLC first. Get your business and number registered before you send. This is your delivery foundation.
  • Collect opt-in, every time. Bake consent into your intake and engagement process so it's automatic, not an afterthought.
  • Use templates for the repeatable stuff. Appointment reminders, paperwork-ready alerts, and review nudges go faster and stay consistent when you're not writing them from scratch.
  • Keep one-to-one and broadcast separate. Conversational texts — answering a client's question, confirming a time — are a different tool than broadcast campaigns sent to a list. Swivel gives you both: one-to-one and broadcast texting in one place, so you use the right mode for the moment.
  • Archive everything. Make sure every message lands on the client record and in your archive without you lifting a finger.

None of this is exotic. It's a setup checklist plus a platform that enforces the good habits for you, so you get the reply rates of texting without the delivery and compliance headaches.

Texting is one of the fastest ways to reach the clients you serve — when it's done right. Register, get consent, keep your modes straight, and archive it all, and you turn a compliance minefield into a routine that just works. If you'd like to see compliant texting built directly into your CRM, take a tour of Swivel.

See Swivel in action.

A quick walkthrough built around the way you sell annuities and serve clients.

← More from the blog