Search "free bulk SMS sender" and you'll find Chrome extensions that drive your phone's web messages, Android apps that push a spreadsheet through your SIM card, Excel macros that fire texts through carrier email gateways, and plenty of advice to "just use Google Voice." They look free and they often work the first time.
They fail on the second or third send. Carriers filter the messages, the number gets flagged, nobody honors STOP, and the business carries all the legal exposure with no audit trail behind it. This post covers what each kind of free tool does, why carriers catch it, what the risk costs in dollars, and what a cheap compliant setup looks like. We make Ready, so we'll show our own pricing. We'll also say where a free tool is a reasonable choice.
What "free" bulk SMS tools actually are
Most free options fall into four groups:
- Browser extensions and phone apps. These automate your personal phone or its web client, such as Google Messages for Web. Each text goes out from your personal mobile number, one after another, through your consumer plan.
- Excel or Google Sheets macros on email-to-text gateways. The script emails
number@carrier-gatewayfor each row. Carriers have deprioritized these gateways for years, and some have shut theirs down completely. - Google Voice. It's free, it gives you a second number, and it has a texting interface. It's built for personal, person-to-person use. Its terms bar automated and bulk messaging, and it limits or suspends accounts that send to many people at once.
- "Free tier" web senders. These are usually offshore gateways or trial accounts that send over unregistered routes. They're free until delivery collapses or the account disappears.
All four share one gap. None of them registers your business with US carriers as an application-to-person (A2P) sender. That gap causes most of the problems below.
Why carriers filter them
US carriers treat business texting on regular 10-digit numbers as A2P traffic, and since 10DLC rollout they expect that traffic to be registered: a brand, a campaign describing what you send, and sample messages. If you're unsure whether this applies to you, our post on whether A2P 10DLC is required goes through the edge cases.
A free tool sending from your personal phone or a Google Voice number looks like a consumer line suddenly sending 300 near-identical texts in an hour. Carrier filters are built to catch exactly that pattern. The usual result:
- Silent filtering. Your phone shows "delivered" or "sent," but the text never arrives. You get no error and no refund, because nothing was charged.
- Throttling, then blocking. After repeated hits, the number's traffic slows down or stops entirely.
- Account loss. Consumer plans and Google Voice prohibit this use. Losing the number can also mean losing your existing one-to-one conversations with real customers.
Registered traffic isn't immune to filtering. Bad content still gets caught. What registration gives you is a lane carriers recognize, with known throughput: roughly 1 to 4 segments per second for a fresh standard campaign. For more on what happens to unregistered senders, see 10DLC enforcement: fines, blocking and what unregistered sending costs.
The consent and STOP problem
Filtering is the visible failure. The consent gaps are the expensive ones.
Nobody is handling STOP
When a contact replies STOP to a text from your personal phone, nothing happens automatically. The reply sits in your inbox. Next week the macro runs again and texts them anyway. That is a clean TCPA claim, and you created it with a spreadsheet.
Variants like "cancel," "unsubscribe" and "quit" make this worse, because a human scanning replies will miss some. A compliant platform records the opt-out and blocks that number on every later send.
Nobody is checking the clock
TCPA rules restrict marketing texts to roughly 8 AM to 9 PM in the recipient's local time. A macro sends whenever you press the button. If you run it at 8:15 AM Eastern, it reaches California at 5:15 AM.
There's no record of what you did
Free tools don't log who sent what, to how many people, or when, beyond your phone's message history. If a complaint arrives, you have nothing showing which list you used or what consent you believed you had. Our guide to documenting SMS consent covers what that record should contain.
What the risk looks like in dollars
TCPA statutory damages run $500 per violating text, rising to $1,500 if the violation is found willful. These are statutory figures, not averages of real outcomes. They show the scale of exposure:
- 10 texts sent to someone who replied STOP: $5,000 to $15,000
- 200 texts sent before 8 AM local time across a list: $100,000 to $300,000 in theoretical exposure
Professional TCPA plaintiffs actively look for senders who ignore STOP and quiet hours, and free tools do both by default. Compliance is always the sender's responsibility, on any platform. Tooling reduces the number of ways you can get it wrong, but it doesn't make you immune.
The real cost of "free": a worked example
Take a small business with 1,000 customers who opted in. They send one appointment-reminder or promo text a month, kept under 160 plain characters so it fits in 1 segment.
Free tool path
- Software cost: $0
- Delivered rate: unknown. If carriers filter a third of the sends, about 330 customers never see the text, and you can't tell which ones.
- Opt-out handling: manual
- Quiet hours: none
- Exposure: $500+ for every text that reaches someone who already opted out
Registered path on Ready Standard
- Registration: $25 charged at submit (the first month), then $25/mo for registration + $2 per number. With one number, that's $27/mo. There's no setup fee, and most approvals take 2 to 7 days.
- Sending: 1,000 × 1 segment × $0.0075 = $8 in per-segment charges plus 1,000 × $0.0045 in carrier fees
- Replies are billed like sent texts. If 100 people reply with a 1-segment message, add 100 × ($0.0075 + $0.0045).
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
Segments, not messages, are what get billed. Suppose you write a 175-character promo with one emoji. The emoji forces Unicode encoding, which drops each segment to 67 characters, so the text is 3 segments. The same 1,000-contact send becomes 1,000 × 3 × ($0.0075 + $0.0045), which is three times the cost. Remove the emoji and trim to 160 characters, and you're back to 1 segment. Our breakdown of bulk SMS cost per message covers this in more depth.
Compared on monthly spend, the free tool wins. Compared on cost per text that actually arrived and didn't create a liability, it doesn't.
When free is actually fine
There are cases where you don't need a platform:
- True one-to-one texting. You text a handful of customers who contacted you first, by hand, as normal conversation. That's ordinary person-to-person messaging.
- Internal team texts. Sending a schedule change to your own six employees isn't marketing to consumers.
- Very low volume with no automation. If you'd never send the same message to more than a few people, the registration overhead may not be worth it yet.
Once you're sending the same message to a list, on a schedule, or through any tool that automates it, you're doing A2P messaging and carriers will treat it that way.
Also, if you're a developer comfortable building STOP handling, quiet hours and an audit trail yourself, raw APIs like Twilio are an option. Twilio runs about $0.0083 per segment, under our Standard rate. The cost there is your engineering time, because the compliance logic is yours to build and maintain.
What a compliant setup includes
Whichever provider you pick, these are the things a free tool is missing. Here's how Ready handles each one:
| Gap in free tools | What Ready does |
|---|---|
| Unregistered sending | Brand and campaign registration handled in-app; most approvals take 2 to 7 days |
| STOP ignored | Inbound STOP/UNSUBSCRIBE is honored automatically, and the opt-out blocks that contact across campaigns |
| No quiet hours | Held 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. A held text is charged only when it sends |
| No litigator screening | Optional TCPA-litigator and DNC scrubbing ($0.003 per segment when switched on) |
| Texting landlines | Optional landline validation ($0.003 per segment when switched on) |
| No audit trail | Your opt-in attestation is recorded per campaign you send and per API send that attests consent: who sent, to how many, when |
The attestation record is not a per-contact consent record. It doesn't store each recipient's opt-in time, wording or signup page. Your website, booking tool or store still has to keep 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.)
Ready also includes two-way conversations in one inbox, templates, an AI message writer with a spam-filter check, and a native GoHighLevel integration if you already run your business there. It works for retailers, clinics, nonprofits and service businesses, not just agencies.
Getting started without paying first
The first 20 texts are free. They're one-to-one sends; campaigns are paid from the first text. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it. Use the free texts before you register, because they end as soon as a registration is paid for. Before registering, an account can send up to 500 texts a month at its normal per-text rate. After that, it needs to register.
The practical takeaway
Free bulk SMS senders keep a $0 software line on your budget by moving the cost somewhere else: texts that silently never arrive, a personal number at risk of suspension, and TCPA exposure at $500 or more per mistake. For a list of 1,000 opted-in customers, a registered and compliant setup with one number costs $27/mo plus $0.012 per segment.
If you're currently running a macro or extension, first stop texting anyone who has ever replied STOP. Then register before your next send. You can start on Ready here and compare the numbers on the pricing page.