A2P 10DLC registration explained: what it costs and how long it takes

The two registrations

Registration happens in two layers, and they are approved separately. The brand is your legal business identity — registered name, tax identifier such as an EIN, address, website, and a contact. This is matched against public business records, which is why a name that doesn't exactly match your EIN filing is a common failure point.

The campaign is what you intend to send: the use-case category, a description of the audience, how consent is collected, and sample messages. One brand can carry several campaigns. Registration is handled through The Campaign Registry, but you file through your messaging provider rather than directly.

What it costs and how long it takes

Published figures vary by provider, so treat any specific number as a reference point and confirm against your own provider's current pricing before you budget. Twilio's documentation is the most publicly detailed and gives a usable picture of the shape of the costs.

According to Twilio's A2P 10DLC documentation, a sole proprietor brand registration is a $4.50 one-time fee and a standard brand registration is $44 one-time, which includes the primary vetting fee charged by The Campaign Registry. Twilio's campaign vetting FAQ states that US A2P 10DLC campaign registrations are subject to a manual vetting process with a $15 campaign verification fee charged at the time of vetting, and that this fee is non-refundable — a denied campaign that you resubmit can incur further charges.

On timing, Twilio's guidance is that registration for standard use-cases generally completes within about five business days, and that you should contact support if vetting is still in progress after ten days. Plan a launch around a week or two of lead time, not an afternoon.

Beyond registration there are recurring costs: a monthly fee per campaign and per-message carrier fees layered on top of your normal messaging rate. These are the numbers that vary most between providers, and the ones most often left out of a comparison.

Why registrations get rejected

• Business details that don't match public records — a trading name where the legal name belongs, an old address, a mistyped EIN
• A use-case description that doesn't match the sample messages, or samples that are vaguer than what you'll actually send
• No described consent mechanism, or one that doesn't plausibly produce consent for the messages shown
• Sample messages missing business identification or opt-out language
• Choosing a use-case category that carries stricter scrutiny than your actual traffic requires

Registration is a carrier permission, not a legal one. An approved campaign says the carriers will carry your traffic. It says nothing about whether a given recipient agreed to receive it — that's a separate question, and it's the one the consent checklist covers.

After approval: throughput and ramp

Approval sets your throughput — how many message segments per second the carriers will accept from your number — based on brand type and vetting score, not on how much you'd like to send. A newly approved campaign pushing its full daily allowance on day one is exactly the pattern the registration system was built to catch, so volume that grows steadily is both safer and faster in practice.

Where SignalBack sits on this

To be exact about what exists: the free CSV audit is live, and sending infrastructure — email and SMS alike — is not built yet. Nothing sends today.

The design intent, when campaigns are enabled, is email-first, precisely because email needs no carrier approval and reactivation shouldn't wait on paperwork. A registration wizard for filing brand and campaign is planned alongside it, with SMS unlocking once approval lands. Consent tracking, opt-out propagation across channels, and volume ramping are being designed into the sending path itself rather than offered as toggles — the aim is that they aren't optional.