Collect the legal business name, the EIN, the business address, a website and a contact person before you ask a customer to turn on texting. Ready registers businesses that have an EIN, so that field decides whether a customer can register at all. Asking for it up front saves a failed submission later.
Most registration trouble starts with details that don't match what the carrier checks. If your onboarding form captures them cleanly the first time, the rest of the process is routine. Here's what to ask, how to design the fields and what to do when the answer is "I don't have one."
Why the EIN comes first
An EIN is the federal tax ID the IRS issues to a business. Carriers use the registration details to confirm that a real business is behind the brand, and the EIN plus the legal name is the strongest match they have. Ready registers businesses with an EIN only. A sole proprietor without one can't register through Ready, so don't offer that path in your product.
If you want the background on why registration exists, read our 10DLC explainer. For the sole proprietor question in depth, see 10DLC for sole proprietors and low-volume senders.
What to collect
| Field | Why it matters | Form tip |
|---|---|---|
| Legal business name | Must match the name on the EIN record | Label it "legal name", and show a hint that it differs from a brand or trade name |
| EIN | Identifies the business to carriers | Accept 9 digits, format as 12-3456789 as they type |
| Business address | Checked against public records | Collect street, city, state and ZIP as separate fields |
| Website | Reviewers open it to see what the business does | Require a live URL with https:// |
| Contact name, email and phone | For questions during review | Prefill from the signup user, let them edit |
| What they text about | Drives the campaign description | A short pick list plus a free text box |
Keep the list this short. Every extra field loses some people. The submission and status endpoints are covered in the registration API docs, so check there for the exact fields to send.
Validate before you submit
Catch typos in your form rather than in a rejection.
- Format. An EIN is nine digits. Strip spaces and dashes, check the count and re-insert the dash for display.
- Name match. Show the legal name back and ask "Is this exactly how it appears on your IRS notice?" A customer who types a brand name in the legal name field is an easy way to cause a mismatch.
- Website. Check that the URL loads. A parked or broken site stalls review. Our guide to website, privacy policy and terms requirements for 10DLC lists what the page should show.
- Address. Use the business address, not a home address pasted from a personal profile, unless they're the same.
Don't block on things you can't check. You can't confirm an EIN is real from your side. Format-check it and let registration do the rest.
Handle sensitive data carefully
An EIN is a tax identifier. Treat it that way. Mask it after entry, show only the last four digits when you display it, don't write it to logs and limit which staff roles can read it. Say on the form why you're asking: "We need this to register your business with carriers so your texts get delivered."
What to do for customers without an EIN
Some customers will be sole proprietors, hobbyists or newly formed companies. You have a few honest options.
- Point them to the IRS. A US business can apply for an EIN directly from the IRS, and it's free. Link to the IRS page rather than to a paid filing service, and let them return when they have it.
- Let them save progress. Store what they've entered so they don't redo the form.
- Offer something they can use now. An account can send a limited number of texts a month until its registration is approved. After that cap, it has to register. A blue line sends iMessage and needs no 10DLC registration, though it only reaches iPhone users and has its own daily limits.
- Say no clearly. If none of those fit, tell them registration isn't available without an EIN. A clear answer beats a form that fails after five minutes.
Don't suggest a made-up number or someone else's EIN. That's a misrepresentation, and it puts both the customer and your platform at risk.
Where the form sits in your flow
Put registration after the customer has seen value, not on the first screen. A good order is signup, a first look at the product, then a "turn on texting" step that asks for the business details. Our guide to onboarding for vertical SaaS covers how to stage it.
Plan for what happens after submission, too. Registration goes into review, and your product should show that state rather than a blank screen. Most approvals take 2 to 7 days.
The takeaway
Ask for the EIN early, validate its format, match the legal name to the IRS record and treat the number as sensitive. For customers without one, point them to the IRS and be plain about what they can't do until they have it. When you're ready to build the flow, begin with the registration guide.