Executive Summary
Accounting firms text clients about appointment reminders, document requests, e-signature links, and filing deadlines. During tax season, volume spikes. US local numbers through practice platforms require A2P 10DLC Brand and Campaign registration. Keep tax marketing (for example, “refund advance promos” from partners) off informational Campaigns unless you have proper marketing consent and packaging.
Short answer: Register 10DLC before tax season. Use care/account Campaigns for reminders and doc requests; Marketing Campaigns for promotional offers. Plan throughput with your CSP—do not assume buying more numbers raises caps.
Who This Is For / Who It Is Not For
Who this is for
- CPA firms, EAs, bookkeeping practices
- Multi-office accounting groups
- Practice-management vendors supporting SMS
Who this is not for
- IRS or government agency messaging programs
- Pure email-only client portals
Definitions
| Term | Accounting SMS meaning |
|---|---|
| Doc request text | Ask client to upload W-2s/1099s |
| Deadline reminder | Filing or payment due notices |
| Referral promo | Marketing content |
| Seasonal spike | Jan–Apr volume surge |
Use-Case Map
| Message | Campaign | Consent |
|---|---|---|
| Appointment reminder | Customer Care | Engagement letter / booking disclosure |
| Document request | Customer Care / Account | Client relationship disclosure |
| E-sign link | Customer Care | Avoid sensitive data in body |
| Tax-season tip newsletter | Marketing | PEWC |
| Partner fintech offer | Marketing / possibly prohibited | Counsel + CSP content rules |
Seasonal Throughput Planning
Confirm CSP caps early. If volume will exceed Low-Volume bands, discuss Standard Brand and vetting options. TCR FAQ: more numbers ≠ more throughput. Stage sends across days rather than one giant Monday blast when constrained.
Sample Messages
[Firm Name]: Reminder—your appointment is [date] at [time]. Reply STOP to opt out, HELP for help. Msg & data rates may apply.
[Firm Name]: Please upload requested tax documents securely via [portal link]. Reply STOP to opt out, HELP for help.
Never put SSNs or full account numbers in SMS.
Decision Framework
- Inventory SMS templates before January.
- Register Brand/Campaigns by November–December buffer.
- Separate marketing offers.
- Test STOP and portal links.
- Brief seasonal staff on approved templates only.
Risk and Failure Modes
| Risk | Mitigation |
|---|---|
| Late registration in March | Pre-season gate |
| SSN in texts | Template ban + DLP |
| Partner spam offers | Contract controls |
| Personal cell workarounds | Policy + approved app |
Implementation Checklist
| Step | Owner | Artifact |
|---|---|---|
| Pre-season registration | Ops | Brand/Campaign IDs |
| Template scrub | Privacy | Approved library |
| Throughput confirm | Messaging | CSP email |
| Staff attestation | Managing partner | Log |
Soft CTA
Use MyTCRPlus tools to preflight before peak season.
FAQ
Do accountants need 10DLC?
Yes for US local A2P SMS via software (or use another approved path).
Can engagement letters cover SMS?
If they clearly disclose SMS programs—still prefer explicit SMS language and records.
Are refund-related partner texts allowed?
Content and partner rules vary; confirm CSP prohibited categories and counsel guidance.
Key Takeaways
- Register before tax season spikes.
- Keep sensitive data out of SMS bodies.
- Separate marketing.
- Confirm throughput with CSP.
- Train seasonal staff.
Extended Implementation Playbook
This playbook converts the principles in the article into a sequenced project plan your team can execute without guessing.
Phase 0 — Discovery (week 1)
Interview every team that can trigger an SMS. Export template lists from each vendor. Classify each template as marketing, informational, or conversational care. Identify which legal entity owns each sending number. Capture current consent language screenshots. Produce a gap list: unregistered numbers, missing privacy URLs, bundled checkboxes, and vendors without STOP webhooks.
Phase 1 — Foundations (weeks 2–3)
Publish or repair website privacy and SMS terms. Align legal name and tax ID documents for Brand registration. Select Brand type with your CSP based on expected volume—without inventing universal fee or MPS figures. Draft Campaign descriptions using the who/who/why test. Write message flows that narrate the real opt-in path. Prepare sample messages with brand identification and STOP language.
Phase 2 — Registration (weeks 3–5)
Submit Brand; resolve verification issues immediately. Submit Campaign(s); respond to rejection reasons with packaging fixes rather than argument. Associate numbers only after approval. Configure HELP/STOP replies and test from multiple carrier handsets. Confirm CSP-stated throughput for planning.
Phase 3 — Controls (weeks 5–6)
Connect all vendors to a central suppression list. Enforce template governance so production copy cannot drift silently from registered samples. Train staff with send permissions. Stand up weekly metrics: delivery failures, STOP rate, HELP volume, and exception counts. Create an incident severity model for post-STOP sends and unregistered traffic.
Phase 4 — Scale (ongoing)
Expand locations or programs only after soft-launch metrics stabilize. Revisit packaging when adding loyalty vendors, franchise markets, or new promo calendars. Schedule quarterly counsel review for consent language and state overlays. Re-verify Brand data after mergers, rebrands, or address changes.
RACI snapshot
| Activity | Compliance | Marketing | Engineering | Counsel | CSP admin |
|---|---|---|---|---|---|
| Consent copy | A | R | C | C | I |
| Campaign packaging | R | C | I | C | A |
| Number association | C | I | R | I | A |
| STOP propagation | A | I | R | I | C |
| Incident response | A | C | R | C | C |
Evidence you should be able to produce in 24 hours
- Brand ID and Campaign IDs
- Live privacy and SMS terms URLs
- Opt-in screenshot with version date
- Consent record sample with timestamp and disclosure hash
- STOP log showing suppression timestamps across systems
- Current sample message library
If you cannot produce these, you are not ready for aggressive growth sends—regardless of how polished the marketing calendar looks.
Executive talking points
- Registration identifies us to carriers; it does not create recipient consent.
- Throughput and fees are provider-specific; we will not quote invented industry averages.
- STOP must work everywhere we can send, not only in the primary ESP.
- Template drift is a first-class risk and will be gated like a production change.
Adapt timelines to your CSP review queues. This playbook is operational guidance, not a guarantee of approval timelines or legal safe harbor.
Extended Implementation Playbook
This playbook converts the principles in the article into a sequenced project plan your team can execute without guessing.
Phase 0 — Discovery (week 1)
Interview every team that can trigger an SMS. Export template lists from each vendor. Classify each template as marketing, informational, or conversational care. Identify which legal entity owns each sending number. Capture current consent language screenshots. Produce a gap list: unregistered numbers, missing privacy URLs, bundled checkboxes, and vendors without STOP webhooks.
Phase 1 — Foundations (weeks 2–3)
Publish or repair website privacy and SMS terms. Align legal name and tax ID documents for Brand registration. Select Brand type with your CSP based on expected volume—without inventing universal fee or MPS figures. Draft Campaign descriptions using the who/who/why test. Write message flows that narrate the real opt-in path. Prepare sample messages with brand identification and STOP language.
Phase 2 — Registration (weeks 3–5)
Submit Brand; resolve verification issues immediately. Submit Campaign(s); respond to rejection reasons with packaging fixes rather than argument. Associate numbers only after approval. Configure HELP/STOP replies and test from multiple carrier handsets. Confirm CSP-stated throughput for planning.
Phase 3 — Controls (weeks 5–6)
Connect all vendors to a central suppression list. Enforce template governance so production copy cannot drift silently from registered samples. Train staff with send permissions. Stand up weekly metrics: delivery failures, STOP rate, HELP volume, and exception counts. Create an incident severity model for post-STOP sends and unregistered traffic.
Phase 4 — Scale (ongoing)
Expand locations or programs only after soft-launch metrics stabilize. Revisit packaging when adding loyalty vendors, franchise markets, or new promo calendars. Schedule quarterly counsel review for consent language and state overlays. Re-verify Brand data after mergers, rebrands, or address changes.
RACI snapshot
| Activity | Compliance | Marketing | Engineering | Counsel | CSP admin |
|---|---|---|---|---|---|
| Consent copy | A | R | C | C | I |
| Campaign packaging | R | C | I | C | A |
| Number association | C | I | R | I | A |
| STOP propagation | A | I | R | I | C |
| Incident response | A | C | R | C | C |
Evidence you should be able to produce in 24 hours
- Brand ID and Campaign IDs
- Live privacy and SMS terms URLs
- Opt-in screenshot with version date
- Consent record sample with timestamp and disclosure hash
- STOP log showing suppression timestamps across systems
- Current sample message library
If you cannot produce these, you are not ready for aggressive growth sends—regardless of how polished the marketing calendar looks.
Executive talking points
- Registration identifies us to carriers; it does not create recipient consent.
- Throughput and fees are provider-specific; we will not quote invented industry averages.
- STOP must work everywhere we can send, not only in the primary ESP.
- Template drift is a first-class risk and will be gated like a production change.
Adapt timelines to your CSP review queues. This playbook is operational guidance, not a guarantee of approval timelines or legal safe harbor.
Extended Implementation Playbook
This playbook converts the principles in the article into a sequenced project plan your team can execute without guessing.
Phase 0 — Discovery (week 1)
Interview every team that can trigger an SMS. Export template lists from each vendor. Classify each template as marketing, informational, or conversational care. Identify which legal entity owns each sending number. Capture current consent language screenshots. Produce a gap list: unregistered numbers, missing privacy URLs, bundled checkboxes, and vendors without STOP webhooks.
Phase 1 — Foundations (weeks 2–3)
Publish or repair website privacy and SMS terms. Align legal name and tax ID documents for Brand registration. Select Brand type with your CSP based on expected volume—without inventing universal fee or MPS figures. Draft Campaign descriptions using the who/who/why test. Write message flows that narrate the real opt-in path. Prepare sample messages with brand identification and STOP language.
Phase 2 — Registration (weeks 3–5)
Submit Brand; resolve verification issues immediately. Submit Campaign(s); respond to rejection reasons with packaging fixes rather than argument. Associate numbers only after approval. Configure HELP/STOP replies and test from multiple carrier handsets. Confirm CSP-stated throughput for planning.
Phase 3 — Controls (weeks 5–6)
Connect all vendors to a central suppression list. Enforce template governance so production copy cannot drift silently from registered samples. Train staff with send permissions. Stand up weekly metrics: delivery failures, STOP rate, HELP volume, and exception counts. Create an incident severity model for post-STOP sends and unregistered traffic.
Phase 4 — Scale (ongoing)
Expand locations or programs only after soft-launch metrics stabilize. Revisit packaging when adding loyalty vendors, franchise markets, or new promo calendars. Schedule quarterly counsel review for consent language and state overlays. Re-verify Brand data after mergers, rebrands, or address changes.
RACI snapshot
| Activity | Compliance | Marketing | Engineering | Counsel | CSP admin |
|---|---|---|---|---|---|
| Consent copy | A | R | C | C | I |
| Campaign packaging | R | C | I | C | A |
| Number association | C | I | R | I | A |
| STOP propagation | A | I | R | I | C |
| Incident response | A | C | R | C | C |
Evidence you should be able to produce in 24 hours
- Brand ID and Campaign IDs
- Live privacy and SMS terms URLs
- Opt-in screenshot with version date
- Consent record sample with timestamp and disclosure hash
- STOP log showing suppression timestamps across systems
- Current sample message library
If you cannot produce these, you are not ready for aggressive growth sends—regardless of how polished the marketing calendar looks.
Executive talking points
- Registration identifies us to carriers; it does not create recipient consent.
- Throughput and fees are provider-specific; we will not quote invented industry averages.
- STOP must work everywhere we can send, not only in the primary ESP.
- Template drift is a first-class risk and will be gated like a production change.
Adapt timelines to your CSP review queues. This playbook is operational guidance, not a guarantee of approval timelines or legal safe harbor.
Extended Implementation Playbook
This playbook converts the principles in the article into a sequenced project plan your team can execute without guessing.
Phase 0 — Discovery (week 1)
Interview every team that can trigger an SMS. Export template lists from each vendor. Classify each template as marketing, informational, or conversational care. Identify which legal entity owns each sending number. Capture current consent language screenshots. Produce a gap list: unregistered numbers, missing privacy URLs, bundled checkboxes, and vendors without STOP webhooks.
Phase 1 — Foundations (weeks 2–3)
Publish or repair website privacy and SMS terms. Align legal name and tax ID documents for Brand registration. Select Brand type with your CSP based on expected volume—without inventing universal fee or MPS figures. Draft Campaign descriptions using the who/who/why test. Write message flows that narrate the real opt-in path. Prepare sample messages with brand identification and STOP language.
Phase 2 — Registration (weeks 3–5)
Submit Brand; resolve verification issues immediately. Submit Campaign(s); respond to rejection reasons with packaging fixes rather than argument. Associate numbers only after approval. Configure HELP/STOP replies and test from multiple carrier handsets. Confirm CSP-stated throughput for planning.
Phase 3 — Controls (weeks 5–6)
Connect all vendors to a central suppression list. Enforce template governance so production copy cannot drift silently from registered samples. Train staff with send permissions. Stand up weekly metrics: delivery failures, STOP rate, HELP volume, and exception counts. Create an incident severity model for post-STOP sends and unregistered traffic.
Phase 4 — Scale (ongoing)
Expand locations or programs only after soft-launch metrics stabilize. Revisit packaging when adding loyalty vendors, franchise markets, or new promo calendars. Schedule quarterly counsel review for consent language and state overlays. Re-verify Brand data after mergers, rebrands, or address changes.
RACI snapshot
| Activity | Compliance | Marketing | Engineering | Counsel | CSP admin |
|---|---|---|---|---|---|
| Consent copy | A | R | C | C | I |
| Campaign packaging | R | C | I | C | A |
| Number association | C | I | R | I | A |
| STOP propagation | A | I | R | I | C |
| Incident response | A | C | R | C | C |
Evidence you should be able to produce in 24 hours
- Brand ID and Campaign IDs
- Live privacy and SMS terms URLs
- Opt-in screenshot with version date
- Consent record sample with timestamp and disclosure hash
- STOP log showing suppression timestamps across systems
- Current sample message library
If you cannot produce these, you are not ready for aggressive growth sends—regardless of how polished the marketing calendar looks.
Executive talking points
- Registration identifies us to carriers; it does not create recipient consent.
- Throughput and fees are provider-specific; we will not quote invented industry averages.
- STOP must work everywhere we can send, not only in the primary ESP.
- Template drift is a first-class risk and will be gated like a production change.
Adapt timelines to your CSP review queues. This playbook is operational guidance, not a guarantee of approval timelines or legal safe harbor.
Disclaimer
Informational only—not legal, tax, or CPA professional advice.