Almost every sales team starts with a personal phone. A rep texts a few leads, calls a few back, and it works. Then the list grows to 300, someone finds an iOS Shortcut or an Android auto dialer app, and texts start disappearing, the number gets a "Spam Likely" label, and nobody can say who replied STOP last Tuesday.
A personal phone line is built for one person talking to people they know. It was not designed for commercial volume, and carriers treat it accordingly. This post covers what breaks first, what the legal exposure looks like, and what a business setup costs, with the math shown.
What breaks when you mass text from a personal phone
Carriers filter it
US carriers separate person-to-person traffic from application-to-person (A2P) traffic. Business texting to many recipients is A2P, and in the US that traffic is supposed to run over registered 10DLC numbers. A consumer line sending the same promo to 400 people looks like unregistered A2P to carrier filters, so messages get delayed, silently dropped or blocked. Most consumer plan terms also prohibit commercial bulk messaging, so the line itself is at risk. We cover the enforcement side in 10DLC enforcement: carrier fines, blocking and what unregistered sending costs.
Group texts are the wrong tool
Putting 30 customers in one group thread exposes everyone's number to everyone else, and one "reply all" turns into a mess. Group threads also have participant limits, and they mix iMessage and SMS unpredictably. Individual sends from Shortcuts avoid the exposure, but they run on one device, with no record of who opted out and no reporting on what was delivered.
Nobody is tracking STOP
When someone replies STOP to your iPhone, nothing happens automatically. You have to remember, across every rep's phone, never to text them again. Miss one and you have an opt-out violation with your name on it. TCPA exposure runs around $500 to $1,500 per text, which is why this is the part that turns a scrappy setup into a liability.
No quiet hours, no audit trail
A phone will happily send at 10 PM to a contact three time zones away. It also keeps no record of who sent what, to how many people, and when.
For a longer comparison of consumer apps and platforms, see texting apps vs business platforms.
What breaks when you auto dial from a phone
Your number gets labeled spam
Carrier call analytics watch for patterns: high outbound volume, short calls and low answer rates. A personal number dialing 150 people a day hits all three. Once it's labeled, answer rates drop for every call that number makes, including the ones to your existing customers.
The legal line is about consent and the equipment
Auto dialing cell phones without the right consent is exactly what the TCPA targets, and a phone app doesn't change that analysis. State calling-hour windows are often stricter than federal ones. Before anyone installs a dialer app, read are auto dialers legal? TCPA rules, consent and calling limits.
Calls and notes live on one device
When the rep leaves, the call history, voicemails and context leave with their phone.
Personal phone vs business platform at a glance
| Personal iPhone / Android | Business platform (e.g. Ready) | |
|---|---|---|
| Carrier treatment | Consumer line, filtered as unregistered A2P | Registered 10DLC numbers |
| STOP handling | Manual, per phone | Automatic, applies across every campaign |
| Quiet hours | None | 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 |
| Litigator / DNC screening | None | Optional scrub before send |
| Shared inbox | No | Team inbox, two-way |
| Call recording | Varies by app | Consented recording and transcripts |
| Records | On one device | Per-send attestation log (who, how many, when) |
The move: registered numbers, a shared inbox and a dialer
Here is what the switch looks like on Ready. We make Ready, so treat this as one option. If you already run GoHighLevel's LC Phone or a raw CPaaS like Twilio, those cost less per message, and they're fine if you're happy with them. Ready's case rests on what's bundled: self-serve registration, the compliance stack and the inbox are all included.
Registration
You register a brand and a campaign in the app. There's no setup fee. The charge at submit is the first month, $25, and after that the monthly cost is $25 for registration + $2 per number. Most approvals take 2 to 7 days. While you wait, an account can send up to 500 texts a month at its normal rate. If you bought a number before registering, it sends on Ready's shared registration while yours is in review. The first 20 texts are free one-to-one sends. Use them before you pay for registration, because the free texts end once registration is paid for. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it.
Worked example: a monthly customer text
Here are the assumptions: 1,500 customers who opted in, a 150-character message with no emoji, and a reply rate of about 20%. That figure is an assumption for the math, not a measured rate.
- 150 GSM-7 characters is 1 segment. Add an emoji and the limit drops to 70 characters, so the same text becomes 3 segments.
- Outbound: 1,500 × 1 segment × $0.0075 = $11, plus 1,500 × $0.0045 carrier fee.
- Replies are billed like sent texts: 300 × $0.0075 = $2, plus 300 × $0.0045.
- That's about $14 a month in per-segment charges, plus carrier fees, plus the $27 registration monthly for one number.
This all-in figure excludes the compliance surcharge. Scrubbing and landline validation are each $0.003 extra per segment when switched on, and both are off by default. Opt-outs and numbers on your Ban list are refused before send and not charged. Texts during a recipient's quiet hours are held and charged only when they go out; a one-to-one or API text is held only if the window opens within 6 hours, and is otherwise refused and not charged.
Want blue bubbles? That's a blue line, not your iPhone
Part of the appeal of texting from an iPhone is that messages show up blue. A Ready blue line sends as iMessage with the business's name and photo, and it needs no 10DLC registration. It costs $99 a month per line plus 6 cents a segment, sent or received, and reactions are free. Each line can start up to 50 new conversations a day, send up to 2 texts before a reply and send photos only after one. Texts to Android go from the regular number. If the account already had a number they bill at the regular text price; if the blue line came with its green number, the account's texts bill at 6 cents a segment once it registers or sends through GoHighLevel. Campaigns send from regular numbers, so think of a blue line as a one-to-one sales tool, not a campaign tool. Details: docs.tryready.com/guides/imessage.
Dialing: click-to-call, not auto dial
The Ready Dialer is click-to-call from a dial pad in the dashboard or in GoHighLevel. It includes consented recording and transcripts, inbound calls that ring the open pad, and a Missed call card in the Inbox thread for each call you miss. It does not auto dial, power dial or drop voicemail. If your team needs those features, buy a dedicated dialer and check its consent rules first.
Pricing is $0.025 a minute, with each started minute billed as a full minute and only answered time billed. Here's a worked example: a rep makes 120 calls in a day, 30 are answered (voicemail counts as answered), and each answered call runs about 3 minutes 20 seconds, so 4 billed minutes. That's 30 × 4 × $0.025 = $3.00. The 90 calls that rang out or hit a busy line cost nothing.
A pattern that works well with consented leads: text within the first minute, then call from the pad while the lead is still looking at their phone.
Local presence
With local presence on, Ready sends from your number closest to the contact's area code. Every number stays on your registered campaign.
If you're building this into your own product
If you run a CRM or vertical SaaS and your users are the ones texting from their phones, you can give each customer a sub-account with its own numbers and registration through the API:
POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: 3f1c2a8e-7b4d-4e0a-9c1f-2d6b8e5a4c10
{"to": "+12125550199", "body": "Your appointment is confirmed for Thursday at 10 AM. Reply STOP to opt out.", "consent_attested": true}Bulk sends take up to 100 recipients per call. See docs.tryready.com/api/messages and the quickstart.
The practical takeaway
A personal phone is fine for talking to a handful of people you know. Once you're sending the same message to hundreds of contacts or dialing a list every day, the phone becomes a liability. Texts get filtered, the number gets labeled spam, and STOP replies go untracked. Text only people who opted in or replied, register your numbers and keep calls and records off individual devices. Compliance stays your responsibility on any platform, but the right tools make the routine parts automatic.
If you're planning the first campaign, how to send a mass text to customers the right way walks through it. Pricing is at tryready.com/pricing, and you can create an account and send your first 20 one-to-one texts before you register.