Mass texting on Google Voice, RingCentral, Dialpad and Square: limits

You already pay for a phone system. It has a texting tab. Your customer list sits in a spreadsheet. Pasting 800 numbers into that tab and pressing send looks like the obvious move. Usually it fails in one of three ways: the platform blocks the send, carriers filter the messages without telling you, or the number you've used for years gets flagged as spam.

This post covers why that happens on Google Voice, RingCentral, Dialpad and Square, what each one is built to do, and when a dedicated texting platform is the safer route. We make Ready, which is one of those dedicated platforms, so we also say plainly when your current phone system is fine.

Phone systems are built for conversations, not campaigns

Carriers sort business texting into two buckets. Person-to-person (P2P) is a human typing to another human, one message at a time. Application-to-person (A2P) is software sending the same message to many people. Our A2P vs P2P breakdown goes into the detail, but the short version is this: mass texting is A2P no matter which app you press send in.

VoIP phone systems were designed around P2P. A rep texts a customer back, a front desk confirms an appointment, a manager replies to a missed call. The texting features, rate limits and spam detection all assume that pattern. When you push a list through them, three things go wrong:

• Rate and recipient caps. The platform throttles you or refuses the send.
• Registration gaps. US carriers expect A2P traffic from local numbers to run on a registered 10DLC brand and campaign. Unregistered or mismatched traffic gets filtered.
• Reputation spillover. If the campaign goes badly, the main business number your customers call takes the damage.

Platform by platform

Limits on these products change, and most vendors don't publish exact numbers. Treat this section as a description of how each product is designed. Check the vendor's current docs before you plan a send.

Google Voice

Google Voice is the weakest fit for mass texting. Its policies prohibit automated and bulk messaging. It has no campaign tool, no list upload and no opt-out handling. Accounts that send many similar messages to many numbers can have texting suspended, and in the worst case Google can reclaim the number. That's a bad outcome if the number is printed on your truck. Our full write-up on bulk texting with Google Voice covers the workarounds people try and why they break.

Fine for: a solo operator texting customers one at a time.

RingCentral

RingCentral requires 10DLC registration for business texting from local numbers, and it offers higher-volume SMS options beyond what a normal user line is meant to carry. That puts it ahead of Google Voice. The common catch is that the registration is often filed for conversational or customer-care use. A promotional campaign then goes out on a campaign registered for something else, and carriers notice the mismatch. Our guide to 10DLC on RingCentral, Zoom, Nextiva and others explains what each of those platforms requires.

Fine for: registered, modest-volume texting that matches the use case you registered.

Dialpad

Dialpad also requires 10DLC registration for US business texting, and it limits how much a user can send. The product is organized around user lines and conversations, not lists, segments and drip campaigns. You can send to a group. You won't get campaign-level opt-out tracking across sends, quiet-hours holds or list scrubbing as built-in steps.

Fine for: sales and support teams texting their own conversations.

Square

Square is a different kind of product. Square Marketing lets sellers send text campaigns to customers in their Square directory, and Square runs the sending infrastructure. That's reasonable if your whole customer relationship lives in Square. You're limited to Square's contacts, Square's templates and Square's rules. You can't bring an outside list, you can't reach it through an API, and you can't hold two-way conversations at volume the way a texting inbox allows.

Fine for: a Square-only retailer sending occasional promos to its Square customers.

At a glance

What "blocked" actually looks like

Most senders picture a red error message. In practice the failure is usually quieter.

1. Silent carrier filtering. The app shows "sent" and the handset never receives it. Unregistered A2P traffic is the most common cause. The 10DLC enforcement guide covers what carriers do and what it costs.
2. Throughput throttling. Even registered traffic has ceilings. A fresh standard 10DLC campaign typically gets roughly 1 to 4 segments per second. T-Mobile caps a brand's daily volume by trust score, starting around 2,000 messages a day at the lowest tier.
3. Account-level action. The VoIP provider pauses texting on your line because the pattern looks like spam. That pause also affects your normal customer conversations.

Here's a rough sense of the throughput ceiling. At an assumed 2 segments per second, a 2,000-recipient one-segment message takes about 1,000 seconds, a little under 17 minutes, to leave. On a fresh, low-trust brand, those 2,000 messages also use up the whole T-Mobile daily allowance.

Registration is what separates delivered from filtered

The fix is not a cleverer workaround inside your phone system. The fix is sending A2P traffic on a registered brand and a campaign whose use case matches what you actually send.

On Ready, brand and campaign registration happen in the app. There's no setup fee. The charge at submit is the first month, $25. After that, the monthly cost is $25/mo for registration and $2 per number. Most approvals take 2 to 7 days.

While you wait:

• Your first 20 texts are free one-to-one sends. Use them before you register, because they end the moment a registration is paid for.
• An account can send up to 500 texts a month before registering, at the normal per-text rate.
• To send, you add a card and get a number, which is $2 a month with the first month charged when you get it.

The registration API is documented at registration API docs if you're a platform registering on behalf of your own customers.

What a dedicated platform adds

The reason to move is the compliance plumbing around each send, not the send button:

• Automatic STOP handling. An opt-out applies across every campaign, so a contact who texted STOP can't be messaged again by accident.
• Quiet hours. Sends are held outside permitted hours in the recipient's local time and go out later. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.
• TCPA litigator and DNC scrubbing. Known litigator and DNC-complainer numbers are screened out before the send. TCPA exposure runs $500 to $1,500 per text, so this is cheap risk reduction, not immunity.
• Attestation records. Each campaign you send and each API send that attests consent records who sent it, to how many recipients, and when. Your own opt-in records still need to live in your store or form tool.
• Segment-aware billing. You can see in advance what an emoji will cost you.

None of this makes compliance automatic. Consent is still yours to collect. Cold lists should be reached by phone or mail, not text.

Worked example: a 1,500-customer reminder

Assumptions: 1,500 opted-in customers, one registered campaign with one number, and a 140-character message.

Without an emoji, the 140-character message is 1 segment:

• Sending: 1,500 × $0.0075 = $11, plus 1,500 × $0.0045 in carrier fees.

With one emoji, the message drops to the unicode limit of 70 characters per segment, so the same 140 characters become 3 segments:

• Sending: 4,500 × $0.0075 = $34, plus 4,500 × $0.0045 in carrier fees.

Replies are billed like sent texts. If 300 customers reply with a one-segment answer:

• Replies: 300 × $0.0075 = $2, plus 300 × $0.0045.

First month registration: $25.

Those all-in figures don't include optional screening. Scrubbing and landline validation each add $0.003 per segment when switched on, and both are off by default.

For honesty about price: raw carrier APIs like Twilio (around $0.0083 per segment) and GoHighLevel's LeadConnector (around $0.0083 per message) cost less per message than our $0.0075 Standard rate. What you're paying for with Ready is registration in the app, the compliance stack above, and an inbox where replies land next to your other conversations.

When to stay, when to move

Stay on your phone system if:

• You text conversationally, one customer at a time, a few dozen a day.
• You're on RingCentral or Dialpad with registration that matches what you send.
• You're a Square-only seller happy with occasional Square promos.

Move list sends to a dedicated platform if:

• You send the same message to hundreds or thousands of people.
• Your messages show "sent" but customers say they never arrived.
• You need opt-outs, quiet hours and scrubbing that apply across every campaign.
• Your main business number is too valuable to put at risk.

Many teams split the traffic. Day-to-day calls and one-off texts stay on the VoIP system, and campaigns run from a registered number on a texting platform.

The practical takeaway

Your phone system is good at conversations, and mass texting is a different kind of traffic. Google Voice prohibits it outright. RingCentral and Dialpad can handle it within limits if your registration matches what you send. Square handles it only inside Square. If you're sending to lists, get a registered campaign whose use case matches your messages, keep opt-outs and quiet hours enforced across every send, and do the segment math before you add an emoji.

If you want to try that setup, you can create an account, send your 20 free one-to-one texts, and register when you're ready. Most approvals take 2 to 7 days.