Executive Summary
Bandwidth 10DLC registration follows the industry Brand + Campaign model through Bandwidth as your CSP connected to The Campaign Registry. Bandwidth publishes its own fee schedule, use-case list, and campaign best practices. Notably, Bandwidth documentation has stated it does not currently support Sole Proprietor Brands/Campaigns—plan an EIN-based Brand instead. Always verify live Bandwidth support articles for current dollar amounts; figures below are attributed to Bandwidth’s published fee page and can change.
Short answer: Register Brand then Campaign in Bandwidth’s 10DLC tools, follow their best-practice fields, associate numbers after approval, and budget using Bandwidth’s current fee article—not a universal industry price list.
Who This Is For / Who It Is Not For
Who this is for
- Direct Bandwidth messaging customers
- ISVs building on Bandwidth APIs
- Ops comparing CSP fee pages
Who this is not for
- Brands not on Bandwidth (use your CSP’s guide)
- Sole props seeking Sole Proprietor Brands on Bandwidth (unsupported per their docs—confirm live)
Definitions
| Term | Bandwidth 10DLC context |
|---|---|
| Brand registration | One-time Brand create/verify in Bandwidth/TCR path |
| Campaign monthly fee | Recurring fee by use-case class per Bandwidth schedule |
| DCA / review | Downstream review partners in the chain |
| Import/move Campaign | Bandwidth process to bring Campaigns across |
Bandwidth-Published Fee Snapshot (Verify Live)
Per Bandwidth’s 10DLC fees article (check the page for updates; amounts are Bandwidth-specific):
| Fee type (Bandwidth-published) | Amount (USD) | Frequency |
|---|---|---|
| Brand Registration | $9 per brand | Non-recurring |
| Brand Registration Sole Proprietor* | $8 per brand | Non-recurring |
| Brand Reverify (optional) | $9 per brand | Non-recurring |
| Low Volume/Class T Campaign | $3 per campaign | Monthly |
| Sole Proprietor Campaign* | $4 per campaign | Monthly |
| Charity Campaign | $6 per campaign | Monthly |
| Emergency Campaign | $10 per campaign | Monthly |
| Standard Campaign | $20 per campaign | Monthly |
| Special Campaign | $20 per campaign | Monthly |
| Agents & Franchises Campaign | $60 per campaign | Monthly |
| Third-Party Brand Vetting (optional) | $83 per brand | Non-recurring |
| Enhanced Vet (optional) | $203 per brand | Non-recurring |
| Vetting Appeal | $22 each | Non-recurring |
| Political Vet | $132 each | Non-recurring |
| Failed Political Vet | $44 each | Non-recurring |
*Bandwidth’s fees page states it does not currently support Sole Proprietor brands or campaigns, even though Sole Proprietor line items appear in the table—plan an EIN Brand. Bandwidth also states campaigns (except Political) have an initial 3-month commitment billed even if canceled early. Authentication+ Verification fees and effective dates appear on the live page—confirm before budgeting. Carrier-specific surcharges are documented in separate AT&T/T-Mobile/Verizon articles. All amounts are Bandwidth-specific and subject to change; verify the live article.
Do not treat these as universal carrier law. Other CSPs publish different schedules. Carrier pass-throughs may also apply.
Registration Steps on Bandwidth
- Gather legal name, EIN, website, support contacts.
- Create Brand in Bandwidth 10DLC UI/API.
- After verification eligibility, create Campaign with description, CTA/message flow, samples, attributes.
- Follow best practices.
- On approval, associate numbers per Bandwidth docs on register/import/move.
- Monitor statuses and remediation tickets.
Decision Framework
- Confirm Bandwidth supports your entity type (EIN Brand).
- Pick use case from Bandwidth’s use-case article.
- Budget using live fee page + pass-throughs.
- Package samples/CTA before submit.
- Soft-launch after number association.
Risk and Failure Modes
| Risk | Mitigation |
|---|---|
| Assuming Sole Prop works | Read Bandwidth limitation; obtain EIN if needed |
| Stale fee quotes in decks | Link live article; date-stamp |
| Inconsistent samples | Follow Bandwidth do/don’t table |
| Import mistakes when switching | Use official import/move guide |
Implementation Checklist
| Step | Owner | Artifact |
|---|---|---|
| Read live fees page | Finance | Dated screenshot |
| Brand create | Admin | Brand ID |
| Campaign create | Compliance | Campaign ID |
| Number association | Messaging | Map |
| Post-launch monitor | Ops | Weekly report |
Soft CTA
Regardless of CSP, preflight packaging with MyTCRPlus tools. MyTCRPlus is not a Bandwidth affiliate substitute for Bandwidth support.
FAQ
Does Bandwidth support Sole Proprietor 10DLC?
Bandwidth fee/docs have stated they do not currently support Sole Proprietor brands/campaigns—confirm on the live page.
Where are Bandwidth 10DLC fees?
https://www.bandwidth.com/support/en/articles/12823086-10dlc-fees — verify before budgeting.
How long does approval take?
Varies; Bandwidth and upstream reviewers set timing—ask your Bandwidth contact for current expectations.
Can I move a Campaign to Bandwidth?
See Bandwidth’s register/import/move article for supported paths.
Key Takeaways
- Bandwidth is a CSP path into TCR for 10DLC.
- Use Bandwidth’s live fee and use-case docs—amounts change.
- Sole Proprietor may be unsupported—plan EIN Brands.
- Follow Bandwidth best practices for CTA/samples.
- Import/move carefully when changing providers.
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. Fees and support policies are Bandwidth’s—confirm on their site. Not legal advice.