A2P 10DLC: why your business texts do not arrive without an EIN
It is not a setting and not a checkbox. It is registering your company with the US carriers, and either it is done or the messages are filtered.
By Eugene Romanov·Published
The short answer
A2P 10DLC is the registration that lets a business send text messages from an ordinary ten-digit number in the US. Two things get registered: the company itself, with its legal name and EIN, and the specific campaign, with sample messages. Without it carriers filter or refuse the traffic, and you find out late, because sending looks successful while the customer receives nothing.
SHT-02What drives the number
What is actually registered
Two layers. The company: legal name exactly as the state records it, EIN, address and website. Then the campaign: what you send, why, how someone opted in and how they opt out, with sample texts. The second layer is the one people underestimate. Campaigns are reviewed, and a campaign described as "customer notifications" with no detail and no samples gets rejected. Both layers register to your entity, not to a vendor's.
Why an EIN is not optional
Because what is being registered is a company, and it is checked against public records. The entity has to be live: one that is closed or administratively dissolved fails the check even if its name has been on the letterhead for years. A separate path exists for sole proprietors, with tighter limits, and it does not suit every campaign. This is the part no code can route around.
The real cost is the calendar, not the money
No dollar figure and no waiting period appear on this page on purpose: both depend on the provider and both change, and inventing them would be easy. What is certain is that this is an external process with its own queue, and it should start earlier than feels necessary. One system in production still has its unified message feed unlaunched for exactly this reason: the code is finished and the registration needs a live entity with an EIN. That is recorded with a date in that project's requirements document, on 19 August 2026, rather than remembered.
What to run while the registration is pending
Everything that does not need it: email, notifications into a messenger, a phone call. Lead intake, statuses, documents and email follow-up do not depend on SMS and can launch immediately. The right order is to build the system, start the registration alongside it, and switch the SMS channel on when it is permitted. Done that way the launch does not wait on somebody else's review queue.
Who holds the accounts
You do. The messaging provider, the phone number and the payment account are in your name: the invoices come to you, the access is yours, and nothing is resold at a markup. That is more administration and it is the honest arrangement, because infrastructure rented from a contractor is one more way to be tied to them. The registration follows the same rule: it is your entity being registered, so it stays with you.
What happens if you skip it
Some messages do not arrive, and you are the last to know, because the send reports success. From there the number can pick up filtering that outlasts the mistake, and rebuilding a sender's standing takes longer than registering would have. This is the cheapest thing on the whole build to do early and one of the most expensive to do late.
SHT-03The options, side by side
What each route actually costs you.
| Option | Price | Timeline | The trade-off |
|---|---|---|---|
| Register properly | Provider fees, on your own account | External queue, start early | Messages are delivered and the sender is yours. Requires a live entity with an EIN and a campaign described honestly enough to be reviewed. |
| Sole proprietor route | Provider fees, on your own account | External queue | Available without a company EIN, with tighter limits. Suits some campaigns and not others; confirm with your provider before designing around it. |
| Email and messenger only | Included in a build | Immediately | Launches the same week and needs no registration at all. Does not reach the customer who only reads texts. |
| Send unregistered | Looks like $0 | Immediately | Sending reports success and delivery quietly fails. The number can pick up lasting filtering, which costs more than the registration would have. |
SHT-04General notes
The questions people actually ask.
- N01What is A2P 10DLC in plain terms?
- It is registering business texting with the US carriers: who the sender is, what company stands behind them, and what they send. Without it, messages are filtered or not delivered.
- N02Do I actually need it?
- Yes, if your system sends texts to customers on behalf of the business, reminders and status updates included. No, if you are texting customers personally from your own phone.
- N03Can I register without an EIN?
- Not as a company. A separate sole proprietor path exists with tighter limits and it does not suit every campaign. Check with the provider your messages will go through before building around it.
- N04How much does it cost and how long does it take?
- No figures here, because they depend on the provider and change. Ask the provider carrying your messages, and plan the time as an external wait rather than as a developer task.
- N05My company name is on the letterhead but the entity lapsed. Is that a problem?
- Yes, and it is a common one. The check reads public records, so a dissolved or administratively closed entity fails it. Reinstating takes its own time, which is another reason to start early.
- N06Who does the registration, me or the studio?
- It registers to your entity, because that is what gets checked. What to prepare and how the campaign should be described we work through together, and the account stays yours.