Zoom SMS and 10DLC registration: what Zoom Phone users need to know

You moved your team to Zoom Phone for calls. Then someone tried to text a customer from their Zoom number, and it either didn't go or Zoom asked for a brand and campaign registration first. That gate is not specific to Zoom. US carriers require A2P 10DLC registration for business texting from local 10-digit numbers, so every phone system that sends SMS on local numbers has to put you through it.

This post covers what that registration involves on a phone system like Zoom, where submissions tend to stall, and which compliance pieces you should check for in any texting setup. It also covers the cases where Zoom's built-in messaging is the right tool and the cases where a dedicated texting platform is less work. We make Ready, a texting platform, so we'll be specific about where it fits and where it doesn't.

Why your Zoom Phone numbers can't text until they're registered

10DLC stands for "10-digit long code," which means an ordinary local phone number. Carriers treat texting from a business system as application-to-person (A2P) traffic. They want to know who is sending it (the brand) and what kind of messages are going out (the campaign). If a number has no registration behind it, carriers filter or block its traffic. A message can show as "sent" in your system and still never arrive on the customer's phone.

Zoom handles 10DLC for Zoom Phone numbers through its own admin portal. The exact screens, fees and review steps are Zoom's, so check Zoom's current support articles before you budget. The registration itself is the industry-standard one: you submit a brand, then a campaign, then attach numbers to the campaign. For a side-by-side of what Zoom, RingCentral, Nextiva, GoTo and Genesys each ask for, see our 10DLC by platform breakdown.

What the registration asks for, and where it stalls

Whichever platform you register through, reviewers look at the same things.

The brand

• Your legal business name and EIN, matching IRS records exactly. "Acme Plumbing LLC" and "Acme Plumbing" are different names to a reviewer.
• Business address, website and a contact.
• Entity type (private company, nonprofit, sole proprietor and so on).

A mismatch between the legal name and the EIN is the most common reason a brand fails. Copy the name straight from your IRS letter.

The campaign

• A use case, for example customer care, account notifications or marketing.
• A description of what you'll send.
• Two or more sample messages. They should read like your real messages, include your business name and show opt-out wording.
• How people opt in, plus the opt-in message, help message and opt-out message.

The website and consent flow

Reviewers visit your site. If you collect phone numbers on a form, the form needs SMS consent language near the checkbox or the submit button. Your privacy policy also needs to say that you don't share mobile numbers for marketing. A missing or vague consent statement is a top rejection reason. We cover the wording that passes in the opt-in language guide and the site requirements, with templates, in 10DLC website and privacy policy requirements.

Pick the use case that matches what you actually send

Most Zoom Phone users text in a conversational way: a rep confirms an appointment, follows up after a call or answers a question. That usually fits customer care or a mixed use case, not marketing. Registering as "marketing" because it sounds broad can cost you. Carriers judge your traffic against the use case you declared, and a mismatch between the two invites filtering and slower throughput.

Before you submit, list the three message types your team sends most. Pick the use case that describes all three. Our use-case picking guide walks through the categories.

The compliance gaps to check in any phone system's texting

Registration gets your messages delivered. It does not make your texting compliant. The TCPA lets recipients claim roughly $500 to $1,500 per unwanted text, and registration gives you no protection against that. Phone systems were built for calls first and texting second, so check whether your setup covers each of the following. Read Zoom's current documentation for each item rather than assuming:

1. STOP handling across every sender. A STOP reply should block that contact from every number and every rep on the account. If it only blocks one rep's line, a second rep can text the same person again.
2. Quiet hours by the recipient's time zone. A rep in New York texting a California contact at 8 AM Eastern is texting at 5 AM local time. The send should be held, not left to the rep to remember.
3. Litigator and DNC screening. You need a way to catch numbers that belong to known serial TCPA plaintiffs or that sit on Do Not Call lists before a message goes out. Our post on the three lists compliance teams confuse explains the difference.
4. An audit trail. You need a record of who sent what, to how many people, and when.
5. Landline detection. Texts sent to landlines fail. If you pay for them anyway, you lose the money and you also hurt your delivery numbers.

If your current tool covers all five for the way you send, you don't need to change anything.

When Zoom's built-in messaging is the right call

Stay on Zoom for texting if:

• Your texting is mostly one-to-one: reps replying to customers from the same number they call from.
• You value one number for both voice and text more than any campaign features.
• Your volume is modest and you don't send scheduled bulk messages.
• Your Zoom registration is already approved and messages are being delivered.

In that situation, a second platform adds a second login, a second bill and a second number to keep track of. That is a real cost. Don't take it on unless you need to.

When a dedicated texting platform is simpler

The balance changes when texting stops being a side feature of your phone system:

The realistic setup for many businesses is to keep Zoom Phone for calls and put texting on a separate number on a texting platform. Zoom's registration is tied to Zoom's numbers, so the texting platform needs its own registration for its own number.

On Ready, here is what that looks like:

• Registration happens in the app. You submit your brand and campaign there, and most approvals take 2 to 7 days.
• STOP replies are honored everywhere. An opt-out applies across all your campaigns.
• Quiet hours are enforced automatically, based on the recipient's area.
• Attestation is logged. For every bulk send and every API send that attests consent, we record who sent it, to how many people and when. This is a sender attestation, not a per-contact consent record. Your form or store still has to keep each contact's opt-in time, wording and page, and a keyword reply doesn't create one for you. See how to document SMS consent.
• Scrubbing is available, off by default. Litigator and DNC scrubbing and landline validation can each be switched on. Each adds $0.003 per segment. For a one-off list check, the standalone TCPA & DNC scrub is $0.005 per contact.

None of this makes you lawsuit-proof. Compliance is still the sender's responsibility. These tools reduce the risk; they don't remove it.

What texting on Ready costs, worked out

Ready charges one Standard rate: $0.0075 per segment plus a $0.0045 carrier fee per segment itemized separately. Replies you receive are billed the same way as texts you send.

Registration costs $25 at submit, which is the first month. After that the monthly charge is $25/mo for registration and $2 per number.

Worked example (assumptions stated): a clinic texts 1,000 patients two appointment reminders a month. Each reminder is 1 segment (under 160 plain characters). About 30% of patients reply once with 1 segment, which is a round assumption.

• Sent: 1,000 × 2 = 2,000 segments
• Received: 300 segments
• Rate: 2,300 segments × $0.0075 = $17, plus 2,300 × $0.0045 = $10.35 in carrier fees
• Registration with one number: $25 for registration + $2 number = $27 a month
• Total: $54.60 a month

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Watch the segment count. Put one emoji in a 175-character reminder and it becomes 3 segments instead of 2, because emoji switch the message to unicode. That alone multiplies the cost of every send by 1.5x. Ready replaces curly quotes and long dashes with plain characters before sending, so those don't change your count, but emoji do.

To be clear about price: raw carrier APIs like Twilio and GoHighLevel's LeadConnector charge less per segment. What you get with Ready is registration, the compliance pieces, the inbox and the campaigns in one place, not the lowest per-text rate. If you only need cheap pipes and have engineers to build the rest, a raw API may suit you better. The full rate card is at tryready.com/pricing.

Throughput is a separate consideration. A new standard campaign typically gets roughly 1 to 4 segments per second. At the lowest trust tier, T-Mobile caps a brand at around 2,000 messages a day. For a reminder list of a few thousand contacts, that's fine.

The practical takeaway

• If your Zoom Phone texting is one-to-one, lightly used and already delivering, stay there. Just confirm STOP handling, quiet hours and screening cover the way your team actually texts.
• If you're sending campaigns, running reminders at volume or need texts synced into a CRM, put texting on its own registered number on a platform built for it.
• Either way, the registration rules are the same: match your legal name and EIN exactly, choose the use case that fits what you send, and put clear consent language on your forms.

If you want to try Ready, sign up and add a card. Your first 20 one-to-one texts are free, so use them to test your messages before you submit your registration. Paying for a registration ends the free texts.