If your platform lets customers text through sub-accounts, you're the one carriers and regulators will call when a customer misbehaves. Know your customer (KYC) for SMS is the short list of things you collect and check before the first message goes out.
Done well, it also does double duty. The same facts a platform needs to trust a customer are the facts 10DLC registration asks for. Collect them once, check them once, and you have a registration-ready customer.
Why does a platform need KYC for texting?
A sub-account sends under your name as far as your messaging provider is concerned. One customer with a bad list or a deceptive message can hurt registrations, deliverability and your relationship with the provider. Our post on the agency and client compliance liability split explains why the customer carries the legal duty for consent, but you still carry the operational risk of who you onboard.
KYC reduces three risks:
- Fraud and abuse, such as a shell business set up to send scams.
- Registration rejections, caused by mismatched or missing business details.
- Bad-consent senders, who text people who never agreed.
None of this makes a customer's texting lawful on its own. Compliance stays the sender's responsibility. KYC lowers the odds that you onboard the wrong sender and gives you a record if you need to act.
What should you collect?
Ask for the same things the registration needs, plus a few that help you judge risk. This table pairs each item with why it matters.
| Item | What to collect | Why it matters |
|---|---|---|
| Legal business name | As registered with the state or IRS | Must match the brand registration exactly |
| EIN | The employer identification number | Ready registers businesses with an EIN only |
| Business address | Physical address, not only a mailbox | Carriers vet it against the brand record |
| Website | A live, working site | Reviewers visit it; a dead link causes rejections |
| Contact | Named person, work email, phone | You need someone to reach during an incident |
| Use case | Plain description of what they'll text | Maps to the campaign use case |
| Sample messages | Two or three real examples | Reviewers compare them to the use case |
| Consent flow | Where and how people opt in | The core of the campaign submission |
| Expected volume | Rough texts per month | Sets sender expectations and throughput needs |
One note on the EIN. Ready registers businesses with an EIN only, so a sole proprietor without one can't register there. Ask for it at signup, not after the customer has built a campaign around a number they can't use. Our post on sole proprietor and low-volume registration covers what that means in practice.
What can you verify yourself?
Collecting a field isn't the same as checking it. Spend a few minutes verifying the facts you can.
- Compare the legal name and EIN against a public record or a document the customer uploads.
- Open the website. Confirm it names the same business and shows how to reach them.
- Check the website has a privacy policy and terms. Our guide to 10DLC website, privacy policy and terms requirements lists what reviewers look for.
- Read the sample messages. Do they match the stated use case?
- Look at the opt-in flow itself. Visit the form or ask for a screenshot of it.
Some signals deserve a second look before approval:
- A business address that's a residential or virtual office with no tie to the name.
- A website created last week with template text.
- A use case that changes between your form and the sample messages.
- A request to text a purchased list.
- A customer who asks how to avoid registration.
Cold lists are out. Cold contact belongs on the phone and in the mail. SMS goes to people who consented or who replied, so a customer whose plan starts with a bought list is a customer to turn away or redirect.
How does this map to 10DLC registration?
10DLC registration has two layers: the brand (who the business is) and the campaign (what it'll text and how people opt in). Your KYC fields line up almost one to one.
| KYC field | Registration field |
|---|---|
| Legal name, EIN, address | Brand |
| Website, contact | Brand |
| Use case, volume | Campaign use case |
| Sample messages | Campaign samples |
| Consent flow | Campaign opt-in description |
In Ready, each customer is a sub-account with its own numbers and its own registration. The brand and its first campaign are one Registration line at $25/mo per customer, each extra campaign is $20/mo, and each number is $2/mo. Most approvals take 2 to 7 days. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
You can drive this by API. POST /v1/sub-accounts creates the sub-account, and POST /v1/registration/brand, POST /v1/registration/campaign and POST /v1/registration/confirm submit the registration. The docs for sub-accounts and registration have the request details. For the full flow, read 10DLC for SaaS platforms.
How do you check the consent flow?
This is the step platforms skip, and it's the one that matters most. A registration can pass and a customer can still text people who never opted in.
Ask the customer to show you:
- The exact form, checkbox or keyword prompt where someone agrees.
- The disclosure language next to it: who's texting, what about, how often, how to stop.
- Where they store the proof of agreement.
Ready stores no per-contact consent for most sends, so the sender keeps it in their own form or CRM. The one exception is a sign-up on a Ready-hosted opt-in page, which is stored per contact with the time, IP and exact wording. Tell your customers to keep their own records. Our consent record schema for developers shows what a good record holds.
What should you re-check after approval?
KYC isn't one gate at signup. Customers change their business, their messages and their lists. Plan light checks later:
- Review opt-out and complaint rates per sub-account on a schedule.
- Re-read a sample of messages when volume jumps.
- Ask for an updated consent flow if the use case changes.
- Act on a spike in opt-outs before the provider does.
Keep notes on what you checked and when. If you ever need to suspend a sub-account, a short record of what the customer told you is far more useful than a memory.
Frequently asked questions
Is KYC legally required to resell SMS?
There's no single KYC rule for every platform, and this isn't legal advice. Carrier and messaging provider rules do require accurate business details at registration, and a platform that onboards carelessly takes on risk. Treat KYC as operating practice, and ask your lawyer about your own obligations.
What if a customer has no EIN?
On Ready, they can't register as a sole proprietor, because Ready registers businesses with an EIN only. The customer can get an EIN, or they can use a channel that doesn't need 10DLC registration, such as the blue line for iMessage.
Who is responsible if a customer sends without consent?
The sender is responsible for consent. A platform still carries the operational fallout, so check the consent flow at onboarding and keep the right to suspend a sub-account in your terms.
The practical takeaway
Collect the registration fields up front, verify the ones you can in a few minutes, and review the consent flow with your own eyes. You'll turn away a few bad fits, reject fewer registrations and have a record when something goes wrong.
If you're designing the onboarding flow now, the vertical SaaS onboarding checklist is a good next read.