Mass text apps on the App Store and Play Store have a simple pitch. You load your contacts, type one message, tap send, and it goes out to everyone as an individual text from your own phone. For a salon with 300 regulars or a contractor with a list of past customers, that looks like free SMS marketing.

It works until it doesn't. These apps send business messages through a channel that carriers built for people texting people. When the volume or the content looks commercial, carriers slow it down, filter it or flag the line. The app can't fix that, because the problem is the channel, not the app. This post covers where the limits are, when an app is still the right tool, and how to know it's time to move to a registered platform. We make Ready, which is one of those platforms, so we've also included the cases where you don't need one.

How consumer mass text apps actually send

Most of these apps do one of two things:

  1. Send from your phone's own number. The app queues your message and has your phone send it to each contact one at a time, through your mobile plan. To the carrier, it looks like you personally texted 300 people.
  2. Send from an unregistered virtual number. Some apps rent a long code number and push traffic through it without registering your business with the carriers.

Either way, the traffic is unregistered business messaging. US carriers split texting into two categories. P2P (person to person) is you texting friends. A2P (application to person) is a business texting customers. A2P traffic on regular 10-digit numbers is supposed to run on registered 10DLC routes, where your brand and the type of messages you send are on file with the carriers. Our A2P vs P2P explainer covers the line in more detail. The short version is that one number sending the same promo to hundreds of people is A2P, whatever app it comes from.

The three limits you hit

Throttling

Carriers watch for patterns: one number, identical text, many recipients, fast. To avoid tripping that, many apps space messages out on purpose, a few seconds apart, and some require the phone to stay awake and on Wi-Fi the whole time. A 500-person send can take a long while, and if your phone sleeps or loses signal, the queue stalls partway through.

Registered routes have throughput limits too, but they're set and predictable. A fresh standard 10DLC campaign gets roughly 1 to 4 segments per second, and T-Mobile's lowest daily brand cap is around 2,000 messages a day. Carriers don't publish an official rate card, so treat those as approximations. They're still enough to finish a 500-contact send in a few minutes rather than an afternoon.

Deliverability

Unregistered A2P traffic gets carrier-filtered, and the frustrating part is that you usually aren't told. The app shows "sent." The customer never sees it. You can't tell a filtered message from one that was ignored, so you might decide texting "doesn't work" when it was never delivered.

There's also a risk to the line itself. Consumer mobile plans generally aren't meant for commercial bulk sending. A number that gets reported as spam often enough can have its outbound texting restricted, and if that number is also your personal cell, you've lost both.

Compliance

This is the limit that costs money. Business texting falls under the TCPA, and statutory damages run roughly $500 to $1,500 per text. A consumer app typically gives you:

  • No automatic STOP handling. Someone replies STOP, and unless you remember to delete them by hand, they get your next promo.
  • No quiet hours. Nothing stops a send from going out at 10 PM in the recipient's time zone.
  • No audit trail. If someone claims they never agreed to texts, you have nothing showing who sent what, to how many, and when.
  • No consent capture. You're relying on memory for who actually opted in.

Compliance is always the sender's responsibility, on any tool. A registered platform doesn't make you immune to lawsuits. It removes the mistakes that are easiest to make on a phone app.

The group text problem

Some owners skip the apps and use a plain group text. That has its own issues:

  • Everyone sees everyone's number. Your customer list is now in 50 strangers' phones.
  • Reply-all chaos. One "thanks!" pings the whole group, and people leave or mute.
  • No way to opt one person out. You'd have to rebuild the group.
  • It's still business texting. A group thread of customers getting promos is A2P traffic, with the same consent rules.

Group MMS is fine for a project crew or a family. It's a poor customer list.

App vs registered platform, side by side

Consumer mass text appRegistered platform (e.g., Ready)
Sending numberYour personal cell or an unregistered numberBusiness number on your registered 10DLC campaign
Carrier registrationNoneBrand + campaign registration; most approvals take 2 to 7 days
ThroughputThrottled by the app to avoid filtersSet by carrier tier (roughly 1 to 4 segments/second for a fresh standard campaign)
Delivery visibility"Sent" means the phone sent itDelivery status per message
STOP handlingManualAutomatic; opt-out blocks future sends across campaigns
Quiet hoursNoneHeld for permitted local hours: campaigns, drip campaigns and automations up to 24 hours, a one-to-one or API text up to 6, otherwise refused
RepliesMixed into your personal textsShared Inbox
Audit trailNoneSender's opt-in attestation recorded each time you send a campaign (and each API send that attests consent)
CostFree or a small subscriptionPer segment, plus registration fees

What a registered platform costs

This is the real trade. Free apps are free, and a registered platform isn't. Here's the math on Ready.

Registration: no setup fee. You pay the first month, $25, when you submit. After that it's $25 for registration + $2 per number, so $27/mo with one number. The 10DLC cost breakdown explains each fee.

Messages: Standard is $0.0075/segment plus a $0.0045 carrier fee per segment. Replies you receive are billed the same way.

Worked example (assumptions stated): an 800-contact opted-in list, two promos a month, each message 150 plain characters, so 1 segment each.

  • Outbound: 800 × 2 = 1,600 segments
  • Assume around 10% of recipients reply once per send: 160 inbound segments
  • 1,760 segments × $0.0075 = $13.20, plus 1,760 × $0.0045 in carrier fees
  • Plus $27/mo registration with one number

Watch the segment count. Add one emoji to that same 150-character message and the limit drops to 70 characters per segment (67 for multipart), so it becomes 3 segments. That roughly triples the message cost. Ready swaps curly quotes and long dashes for plain ones before sending, so those don't change the count. Emojis do.

To be fair about price: if all you want is the lowest per-segment rate and you're comfortable building on an API, raw carrier APIs like Twilio are priced below our Standard rate. What you get with Ready is self-serve registration handled in the app, the compliance stack above, an inbox, contacts, templates and automations in one place. Compare on what's included, not on the rate alone.

When an app is genuinely fine

  • You're texting a small group of people you know personally, and it's conversational, not promotional.
  • It's a one-off: a volunteer crew or a youth team's parents, not customers on a marketing list.
  • Volume is tiny and every message is a real one-to-one conversation.

If that's you, don't pay for infrastructure you don't need.

Signs it's time to move

  • You're sending the same promo to more than a few dozen customers.
  • People are replying STOP and you're tracking it by hand.
  • Customers say they never got texts you know you sent.
  • Your carrier has warned you or restricted the line.
  • More than one person needs to answer customer replies.
  • You want to text from a business number, not your cell.

If you're on Google Voice or a VoIP line, those hit the same wall. See why 10DLC blocks Google Voice, Grasshopper and VoIP.ms.

How to make the switch without losing your list

  1. Clean the list first. Keep only people who actually opted in to texts from you. Remove anyone who ever asked to stop. Store the opt-in details you have, such as when and how each person signed up. That record is yours to keep. Ready records your attestation per send, not each contact's consent.
  2. Get your website ready. Carriers check for a privacy policy and an opt-in description. The opt-in examples post has sample language that gets approved.
  3. Sign up and add a card. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it. Your first 20 texts are free one-to-one sends, so use them to test before you register, because they end once a registration is paid for. Campaigns are paid from the first text.
  4. Register. Brand and campaign registration happen in the app. Most approvals take 2 to 7 days. Before registering you can send up to 500 texts a month at the normal per-text rate.
  5. Send a short intro from the new number. Tell people who you are and how to opt out, then go back to your normal schedule.

The quickstart guide walks through setup step by step.

The practical takeaway

Consumer mass text apps aren't scams. They use a personal texting channel for business traffic, and carriers increasingly filter that traffic. If your texting is small and personal, keep the app. If you're marketing to a customer list, the free app is costing you in messages that never arrive, opt-outs you have to track by hand, and legal exposure. Moving to registered sending costs about the price of a lunch a month in fees plus $0.012 per segment all-in. If you want to try it, create an account, send your 20 free test texts, and register when you're ready.

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.