Law Firm A2P 10DLC and STIR/SHAKEN: Register SMS and Voice Before Clients Stop Answering
Register A2P 10DLC brands and campaigns plus STIR/SHAKEN voice attestation so law firm SMS and calls deliver—without juggling Twilio consoles.
Your firm finally moved client texting off personal cell phones. Reminders go out. Paralegals reply from the matter file. Then, without warning, messages stop delivering, throughput throttles, or outbound calls show “Spam Likely” on client screens. The problem is rarely your copy. It is carrier compliance you were supposed to finish before scaling SMS and voice.
Partners and office managers search for law firm A2P 10DLC registration, legal practice SMS compliance, and STIR SHAKEN law firm phone setup when the channel they depend on quietly breaks. This guide explains what those programs require, how they fit a modern two-way SMS workflow, and how to register without living inside three Twilio tabs.
Why compliance blocks matter more for law firms
Law firms are not high-volume marketers, but they are high-trust communicators. Clients ignore unknown numbers, carriers filter unregistered business SMS, and ethics rules still expect you to show who contacted whom, when, and in what matter context.
| Symptom | Likely cause | Business impact |
|---|---|---|
| SMS fails or delays spike | Missing or rejected A2P 10DLC brand/campaign | Missed court reminders, intake follow-up gaps |
| Only some messages deliver | Number not on an approved messaging service | Inconsistent client experience by staff member |
| Calls go straight to voicemail | Low STIR/SHAKEN attestation | Clients think you are a robocaller |
| “Trial account” limits | Twilio sandbox rules still active | Cannot scale beyond test numbers |
If you already run two-way SMS tied to matters and client reminders, compliance registration is the infrastructure layer those workflows assume.
A2P 10DLC in plain language
Application-to-Person (A2P) 10-digit long code (10DLC) is the U.S. carrier framework for business texting from normal local numbers. Carriers and The Campaign Registry (TCR) want to know who is sending (the brand) and why (the campaign use case) before they grant throughput and deliverability.
Think of it in three layers:
- Trust Hub profile — Business identity, contact, and supporting details carriers review.
- Brand registration — Your firm (or parent entity) registered as an A2P sender.
- Campaign registration — The specific messaging purpose—client notifications, appointment reminders, two-way case updates—linked to your messaging service and phone numbers.
Getting any layer wrong produces rejections that look like “everything worked yesterday.” That is why a single compliance workspace beats ad hoc Console clicks spread across admin turnover.
STIR/SHAKEN for outbound voice
STIR/SHAKEN (often shortened to SHAKEN/STIR in carrier tooling) attests that your outbound caller ID is authorized to use the number displayed. Without it, mobile carriers increasingly label firm lines as potential spam, even for legitimate follow-up calls.
For law firms, voice attestation matters when:
- Clients do not recognize your main office number after a merger or area-code change.
- Staff place click-to-call from the case file and expect the client to answer.
- Voicemail callbacks depend on the client trusting the return number (voicemail transcription workflow).
STIR setup parallels SMS: a business profile, a trust product, and number assignment for Level A attestation. Voice and SMS compliance share paperwork; they should not share an improvised spreadsheet.
A practical registration sequence
Use this order to avoid rework:
1. Gather firm facts once
Collect legal business name, EIN, address, authorized representative, website, and a short description of how you text clients (reminders, portal links, status updates). Align names with how clients know you—DBA mismatches are a common rejection reason.
2. Create Trust Hub profiles
Register a customer profile (business identity) and an A2P profile bundle. Carriers evaluate these before brand approval. Starter vs secondary profile types depend on entity size; pick the policy that matches your structure.
3. Register the A2P brand
Submit the brand with the profile SIDs from step 2. Wait for approval before campaigns—premature campaign submission creates noise in your audit trail.
4. Register campaigns tied to real use cases
Describe each campaign honestly:
- Client care notifications — Hearing reminders, document requests, portal invites.
- Two-way conversational — Replies when clients text your firm number (if your carrier classification allows it on one campaign, follow Twilio guidance; some firms split transactional vs conversational).
Link campaigns to the messaging service that owns your firm numbers. Numbers purchased outside that service will not inherit campaign throughput.
5. Complete STIR/SHAKEN for voice numbers
After an approved business profile exists, create the STIR trust product, link it to the profile, and assign each outbound number for Level A attestation. Verify status per number before you announce a new client-facing line.
6. Document internal policy
Compliance registration is not a substitute for TCPA-aware consent and firm policy. Write who may text clients, what belongs in SMS vs the client portal, and how staff handle opt-out language. Registration tells carriers you are a legitimate business; your policies tell staff how to stay ethical.
How this connects to daily firm workflows
Compliance is invisible when it works—and expensive when it does not:
- Reminders — Email and SMS reminders depend on approved campaigns; a rejected campaign silently undermines no-show reduction.
- Matter-linked threads — Two-way SMS only scales if every firm number routes through registered messaging services.
- Click-to-call — Browser calling from the case file fails the “quick logistics” test if clients never pick up.
- Audit expectations — Audit trails prove staff actions; carrier registration proves you are authorized to use the channel.
Treat registration as onboarding work alongside buying numbers and training staff—not a one-time IT side quest after clients complain.
Common mistakes to avoid
- Registering under a personal name instead of the professional entity clients retain.
- Launching blast reminders before campaign approval, then blaming “Twilio bugs” when filters engage.
- Mixing marketing and case updates in one vague campaign description—carriers reject ambiguity.
- Forgetting new numbers after purchase; each line needs messaging-service and STIR assignment.
- Assuming personal-phone habits transfer—confidential strategy still belongs in privileged notes and calls, not compliance footnotes (case notes workflow).
How LawyerLink helps
LawyerLink (MyLawyerLink) embeds Twilio Compliance tooling where you already manage firm numbers—under Settings → Integrations → Twilio. The in-app Compliance widget walks through:
- Brands — Create Trust Hub profile bundles and submit A2P brand registration without leaving the platform.
- Campaigns — Register 10DLC campaigns linked to your messaging services and monitor status.
- STIR/SHAKEN — Create trust products, view onboarding readiness, and assign numbers for Level A attestation—including bulk assign when you add lines.
That sits beside the communication workflows you run every day: SMS threads on the matter, recorded calls and AI summaries, portal messaging, and team permissions so only authorized staff change compliance settings.
SMS failing silently or clients ignoring your caller ID? Sign up for LawyerLink to register A2P 10DLC and STIR/SHAKEN alongside your firm numbers—then keep every text and call tied to the case file clients trust.