A group text is the wrong tool for a business message going to more than a handful of people. Everyone sees everyone else's number, every reply goes to the whole group, and nobody can opt out cleanly. Send the same message as separate one-to-one texts from a registered business number instead. Each person gets their own thread, and replies come back only to you.
This post covers why a personal group chat breaks once a business uses it, how group MMS differs from mass texting, what the one-to-one setup costs per segment, and when a plain group chat is still fine. We make Ready, so the setup section uses our product as the worked example. The mechanics are the same on any registered texting platform.
Why a group text breaks for business
The group chat on your phone was built for five friends planning dinner. It was not built for 300 customers, and it shows in a few predictable ways.
Reply all is the default, not an option
In a group MMS thread, a reply goes to every member. One customer asks "is this still on Saturday?" and 299 phones buzz. Then someone answers them, and 299 phones buzz again. Within an hour people mute the thread or leave it, so the next message you send never gets read.
Everyone's number is exposed
Every participant can see every other participant's phone number. For a business that is a privacy problem. Your customer list is now visible to your customers, and to anyone they screenshot it for.
There is no clean opt-out
If one person in a group thread replies STOP, nothing structured happens. They stay in the group, keep getting replies from everyone else, and still receive your next message. With a real opt-out, that person is suppressed from every future send.
Size limits and mixed phones
Group threads have participant caps that vary by phone and carrier. Mixed iPhone and Android groups fall back to MMS, which handles media and long threads less reliably. Past a few dozen people, a group thread starts failing in ways you can't see from your end.
Personal numbers aren't registered for business traffic
US carriers expect business texting to run over registered A2P 10DLC routes. Business messages from a personal phone number, at volume, are the traffic carrier filters are built to catch. Messages get silently dropped and you never find out.
Group MMS vs mass texting: what's actually different
People use "group text" loosely to mean either of two very different things. Here they are side by side.
| Group MMS (a group chat) | Mass texting (one to one at scale) | |
|---|---|---|
| What recipients see | One shared thread with everyone in it | A private thread with your business only |
| Who sees replies | Every member | Only you, in your inbox |
| Numbers exposed | Every member's number is visible | None |
| Opt-out | No structured STOP handling | STOP suppresses the contact from future sends |
| Personalization | Same text for everyone | Merge fields such as first name per contact |
| Size | Small caps that vary by device and carrier | Hundreds or thousands, paced by carrier throughput |
| Carrier registration | Personal number, unregistered | Registered A2P 10DLC brand and campaign |
| Best for | A small team that all agreed to a shared chat | Customers, members, leads, any list of consented contacts |
Most business texting platforms, Ready included, send campaigns as one-to-one messages and do not send them as group MMS. For a business, that is usually what "group texting" should mean. If you're comparing vendors on this, our guide to what to check before you pick a mass texting service goes further.
How to message many people one to one
Here is the setup, in order. The steps are generic, and the details in brackets are how Ready handles each one.
- Get consent first. Text only people who opted in or have already been texting you. Store where and how each person agreed. A form, a checkout checkbox or a keyword sign-up all work if you keep the record. See how to document SMS consent so it holds up.
- Get a business number and register it. You need a brand and campaign registration for A2P 10DLC. (On Ready this happens in-app. The charge at submit is the first month, $25. The monthly cost after that is $25/mo for registration plus $2 per number. Most approvals take 2 to 7 days.)
- Import your contacts. Bring them in with names so you can personalize. "Hi Dana" reads like a message. "Hi all" reads like a broadcast.
- Write the message to fit one segment. Keep it under 160 plain characters. One emoji drops the limit to 70 characters per segment. The math section below shows why that matters.
- Send it as a campaign, not a thread. Each contact gets their own copy from your number.
- Handle replies one at a time. Replies land in an Inbox as separate threads, so you answer Dana without the other 299 people seeing it.
Ready lets you send up to 500 texts a month before registering, at the normal per-text rate. After that you have to register. If you buy a number before registering, you send on Ready's shared registration at the same per-text rate while your own registration is in review. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it.
What it costs: the segment math
Carriers bill segments, not messages. On Ready Standard you pay $0.0075/segment plus a $0.0045 carrier fee per segment. That all-in figure excludes the compliance surcharge. Scrubbing and landline validation each add $0.003 per segment when you switch them on for an account, and both are off by default. Replies you receive are billed the same way as a sent text.
Example 1, plain text. You text a 400-person member list a 150-character schedule change with no emoji. That is 1 segment each, so 400 segments:
- Rate: 400 × $0.0075 = $3.00
- Carrier fees: 400 × $0.0045
Example 2, same list, one emoji added. The message grows to 175 characters with a 🎉. Unicode multipart segments hold 67 characters each, so 175 characters is 3 segments, or 1,200 segments for the list:
- Rate: 1,200 × $0.0075 = $9.00
- Carrier fees: 1,200 × $0.0045
The emoji tripled the bill. Ready swaps curly quotes, long dashes and ellipses for plain ones before sending, so those characters won't push a text into unicode. Emoji will.
Assumption to note on speed: a fresh standard campaign usually moves around 1 to 4 segments per second. At an assumed 2 segments per second, the 400-segment send finishes in about 200 seconds. That is a few minutes, not instant, and it's fine for a schedule change.
The first 20 texts on Ready are free. They count only for one-to-one sends, since a campaign is paid from its first text, and they end the moment a registration is paid for. Use them to test your wording before you register. For the bigger picture on list sizes and pacing, see how bulk SMS works when sending to thousands.
Compliance pieces a group chat doesn't have
These are the parts that make one-to-one sending safer. They reduce risk but don't eliminate it, and compliance stays the sender's responsibility.
- STOP handling. On Ready, an inbound STOP or UNSUBSCRIBE is honored automatically. The opt-out carries across campaigns so that contact can't be texted again.
- Quiet hours. Campaign and drip sends are held outside permitted local hours, based on the recipient's area. A campaign you queue at 10 PM goes out the next morning instead of waking someone up. A single inbox or API text is held only if sending opens within about 6 hours; otherwise it is refused with the reopen time and you send it again.
- Litigator and DNC scrubbing. You can screen out known TCPA-litigator and DNC numbers before a send. The standalone scrub is $0.005 per contact. TCPA exposure is commonly cited at $500 to $1,500 per text, so it is cheap insurance on any list you didn't build yourself.
- Attestation trail. Ready records your opt-in attestation for each bulk send and each API send that sets
consent_attested: who sent it, to how many people, and when. This is not a per-contact consent record. Ready doesn't store each recipient's opt-in time, wording or page. Your own system keeps that. (A contact who signs up on a Ready-hosted opt-in page is the exception: Ready stores that sign-up, with the time, IP address and exact wording, and support@tryready.com can send you a copy.)
A group chat on your phone has none of this, which is why it carries real legal exposure once a business uses it.
When a group chat is actually fine
To be fair to the group chat: sometimes it's the right call. Ready's inbox can start one from your business number.
- An internal crew of five or six coordinating a job, where everyone agreed to the chat and wants to see each other's replies.
- A small committee or project team that needs actual group discussion, not announcements.
- Anything where reply all is the point, such as a quick poll among people who already know each other.
If the people are customers, members or leads, and the message is an announcement, reminder or offer, use one-to-one sends.
On blue lines: Ready's blue line sends texts as iMessage, with your business name and photo, for $99 a month per line plus 6 cents a segment. Group chats on a blue line land in the same inbox thread as SMS. Campaigns and drip campaigns still send from regular numbers, though, so a blue line is not a mass-announcement tool. Our post on blue bubble texting for business covers when it's worth it.
Sending one to one from your own product
If you run a platform and your customers want a "text my whole list" button, the bulk endpoint covers it. Each number gets its own message, not a shared thread:
POST https://api.tryready.com/v1/messages/bulk
X-API-Key: <key>
Idempotency-Key: 6f1c2e9a-3b7d-4c1e-9a2f-0d5b8e7c4a11
{"to": ["+12125550199", "+15559876543"], "body": "Saturday's session moves to 10 AM. Reply here with questions.", "consent_attested": true}The Idempotency-Key header means a retried request never sends twice. Opt-outs, numbers on your Ban list and known landlines are refused up front and not charged. Each of your customers can get a sub-account with its own numbers and 10DLC registration. Full details are at docs.tryready.com/api/bulk-messages.
The practical takeaway
For business, "group text" should mean one message sent privately to many people, not a shared thread. Register a business number, text only consented contacts, keep messages to one segment, and let STOP, quiet hours and replies run per contact. A group chat is still fine for a handful of teammates who want reply all.
If you want to try the one-to-one approach, you can sign up and test your wording with the first 20 free texts before registering. Rates are on the pricing page.
FAQ
Can I send a group text from a business number? Yes, for a small group. In Ready's inbox, start a new text to 2 or more people and it goes out as one group text from your registered number, so everyone sees the replies. Campaigns never go out as group texts: each person gets a private thread, which is what you want for customer announcements.
How many people can I text at once? There's no small participant cap like a group chat has. The limits are carrier throughput (around 1 to 4 segments per second for a fresh standard campaign) and T-Mobile's daily brand cap, which starts at about 2,000 messages a day at the lowest trust score.
Will recipients see each other's numbers? No. In a one-to-one send, each person sees only your business number.
What happens when someone replies? The reply lands in your inbox as that person's own thread, and only you see it. Replies are billed like a sent text: $0.0075/segment plus the $0.0045 carrier fee.
Do I need 10DLC registration to text a group of customers? Yes, for anything beyond light volume. Ready allows up to 500 texts a month before you register. After that, registration is required, and most approvals take 2 to 7 days.