Automated texting service: what to automate, what to write by hand

Automate the texts that respond to something the contact just did or is about to do: appointment reminders, missed-call text back, quote follow-ups and short drip campaigns for people who opted in. Write by hand anything that answers a question, handles a complaint or negotiates, and stop sending generic promos to your whole list, because an automated texting service makes those cheap to send and expensive in opt-outs.

The rest of this post is the practical version. It covers which automations earn replies, which ones damage your list and your carrier reputation, what the money looks like at our $0.0075/segment rate, and how Ready handles quiet hours and opt-outs so your automations don't create compliance problems on their own.

The rule: automate the trigger, hand-write the conversation

Every text that works as automation has a clear trigger and a predictable next step:

• Someone booked, so they get a reminder.
• Someone called and you missed it, so they get a text back.
• Someone asked for a quote and went quiet, so they get a follow-up.
• Someone signed up, so they get a short onboarding drip campaign.

The trigger tells the contact why they're getting the text. They recognize the context, so they reply. Opted-in, context-rich texts get far more replies than generic promos sent to everyone.

Things go wrong once a reply comes in. "Can I move to Thursday?" "Is the $400 quote including parts?" "You charged me twice." None of these fit a template. A human should take the thread from here.

Ready no longer lets accounts create AI reply agents, but one set up earlier may still answer texts on its own until you pause its automation in Automations, and the Take over button in the Inbox thread stops it in that conversation. Replies land in the Inbox, and in GoHighLevel for connected accounts, and a person answers them. The AI message writer helps you draft and spam-check outbound copy. Each set of drafts it writes costs the same as 5 texts at your rate. It doesn't talk to your customers for you.

Automated texts that earn replies

Appointment reminders

This is the most reliable automation there is. The contact asked for the appointment, the text is useful, and a reply ("confirm" or "reschedule") is the expected action. A common pattern is two reminders, one around 24 to 48 hours out and one a couple of hours before. Our appointment reminder SMS guide has templates and timing by industry.

Missed-call text back

Someone called, nobody picked up, and a text goes out within a minute: "Sorry we missed you, what can we help with?" That person reached out to you seconds ago, so the text is a reply, not a cold open. Still, make sure your registered use case covers it.

The cost math for local service businesses is in the missed-call text-back setup post. If you use GoHighLevel, the missed-call workflow sends through Ready once the integration is connected.

If you then call back by hand, the Ready Dialer is click-to-call from the dial pad at $0.025/min. Missed inbound calls also show in the call log, so the follow-up call is easy to find.

Quote and lead follow-ups

A lead asked for pricing and didn't reply. One or two automated nudges spaced a few days apart are reasonable. Six in a week is not.

Short drip campaigns for opted-in contacts

Onboarding, post-purchase care instructions and "your trial ends Friday" all work as drip campaigns when they're short and tied to something the contact signed up for. The principle that matters most: a drip campaign should end for a contact the moment they reply. If your setup can't guarantee that, keep drips to two or three steps so a reply never collides with step four.

Automated texts that hurt

Generic promos to everyone

A "20% off this weekend!" campaign sent to every contact you've ever had is the classic way automation backfires. It has no trigger tied to the person, so the most common reply is STOP. Promo content is also what carriers filter hardest.

One honest note: registration doesn't fix content filtering. A promo can be blocked on a fully approved campaign. Matching your registered use case to what you actually send matters too. This use-case picking guide explains why registering "marketing" when you mostly send reminders, or the other way round, causes trouble.

Stale-consent check-ins

A lead who opted in 18 months ago and never heard from you is not a warm contact. Automating a "still interested?" text to that list invites complaints.

Cold lists

Contacting people who never opted in happens by phone and mail. Texts go to people who consented or replied.

What an automated texting service actually costs, worked out

These are example numbers with stated assumptions, not benchmarks.

Example: a clinic sending reminders. Assume 600 appointments a month, two reminders each, and every reminder under 160 GSM-7 characters with no emoji. That's 1 segment per text.

• Outbound: 1,200 segments × $0.0075 = $9, plus 1,200 × $0.0045 in carrier fees
• Replies: assume 1 in 4 reminders gets a reply. That's 300 inbound segments. Replies are billed like a sent text, so 300 × $0.0075 = $2, plus 300 × $0.0045
• Those totals exclude the compliance surcharge. TCPA/DNC scrubbing and landline validation each add $0.003 per segment when you switch them on for an account. Both are off by default.

Now add one emoji. A 140-character reminder with a single emoji drops to the 70-character unicode limit (67 per segment for multipart). That makes it 3 segments instead of 1, so the same 1,200 reminders become 3,600 segments, or $27 instead of $9 before carrier fees.

Ready swaps curly quotes, long dashes and ellipses for plain ones before sending, so those never inflate the count. Emoji still do.

Example: one promo to an opted-in list. Assume 5,000 contacts and a 175-character message with an emoji, which is 3 segments. That's 15,000 segments × $0.0075 = $113, plus 15,000 × $0.0045. It also takes time to go out. At an assumed 2 segments per second on a fresh standard campaign, 15,000 segments take a little over two hours. This is one more reason targeted, triggered texts beat whole-list sends.

Our Standard rate is one flat $0.0075/segment with no volume tiers. Enterprise pricing is custom, so talk to us. Raw CPaaS APIs and GoHighLevel's LC Phone cost less per segment. With Ready, what you pay for is that registration, compliance and the inbox come included. If you want a pure carrier pipe and plan to build all of that yourself, a raw API is a reasonable choice. Pricing details are at tryready.com/pricing.

The guardrails Ready runs on every automation

The real risk of automation is that a bad rule fires a thousand times before anyone notices. Quiet hours, opt-out handling and consent attestation run on every send, automated or not. Scrubbing runs when you switch it on:

• Quiet hours. Sends outside permitted local hours for the recipient's area are held and sent later. You're charged only when the text actually goes out. A drip campaign step scheduled for 6 AM in the recipient's time zone waits. 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.
• Opt-out handling. Inbound STOP and UNSUBSCRIBE are honored automatically. The opt-out applies across every campaign and drip campaign, so the contact can't be texted again by some other automation. Sends to opted-out numbers are refused up front and not charged. For routing STOP, HELP and YES differently, see the keyword routing tree post.
• Litigator and DNC scrubbing, if you switch it on. Known TCPA-litigator and DNC numbers can be screened out before a send. It is off by default and adds $0.003 per segment when on. The standalone scrub is $0.005 per contact. TCPA exposure runs $500 to $1,500 per text, which is why the scrub is cheap insurance.
• Consent attestation. Every bulk send and every API send that sets consent_attested records the sender's opt-in attestation: who sent it, to how many people, and when. That gives you an audit trail of the send. It is not a per-contact consent record, so the opt-in time, wording and page URL for each contact should live in your own store.

None of this makes you lawsuit-proof. Compliance remains the sender's responsibility. These tools lower the odds that an automation creates a problem at scale.

Setting up automations on Ready

There are three ways in, depending on who you are.

In the Ready app. Build templates, set up automations and drip campaigns, and work replies in the unified inbox. Campaigns and drip campaigns send from your regular registered numbers. If you add a blue line ($99 a month per line plus 6 cents a segment) for iMessage conversations, it carries one-to-one threads, not campaigns.

In GoHighLevel. Install Ready via OAuth as an LC Phone alternative. Your existing GHL workflows, including missed-call text back and reminder workflows, send through Ready. Messages sync both ways per GHL location, so each sub-account stays isolated.

Via the API, for platforms texting on behalf of their customers. Fire a text from your own trigger (booking created, payment failed, trial ending):

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: 6f1c2b7e-3d4a-4e8b-9c1f-2a7d5e0b8c34

{"to": "+12125550199", "body": "Reminder: your appointment is tomorrow at 10 AM. Reply C to confirm or R to reschedule.", "consent_attested": true}

The Idempotency-Key matters for automation. If your job retries after a timeout, the contact still gets one reminder, not two. Docs: docs.tryready.com/api/messages and the quickstart.

Registration comes first for real volume. Brand and campaign registration (A2P 10DLC) is handled in-app. The charge at submit is the first month, $25. After that the monthly cost is $25 for registration + $2 per number. Most approvals take 2 to 7 days.

Your first 20 texts are free one-to-one sends. Use them to test your reminder copy before you register, because the free texts end once a 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.

The practical takeaway

Automate the texts the contact would expect: reminders, missed-call text back, one or two follow-ups and short drip campaigns. Hand-write every reply. Keep generic promos rare and targeted, and keep emoji out of high-volume templates unless you've done the segment math.

Let quiet hours, opt-out handling and scrubbing run underneath so a misfiring rule can't reach the wrong person at the wrong hour.

If you want to try it, sign up, send your reminder template to your own phone with the free texts, then register before you turn automations on.

FAQ

What is an automated texting service?

It's software that sends texts when a trigger fires or a schedule hits: a booking, a missed call, a form fill or a drip campaign step. You don't type each one. Good services also handle carrier registration, opt-outs and quiet hours, because automation multiplies mistakes as fast as it multiplies sends.

Which automated texts get the most replies?

Texts tied to something the contact just did or is about to do, like appointment reminders, missed-call text back and quote follow-ups. They have obvious context and an obvious next step. Generic promos to an entire list usually get the fewest replies and the most opt-outs.

Does Ready auto-reply to customers with AI?

Not on a new account. Ready no longer lets accounts create AI reply agents, though one set up earlier may still answer texts until you pause its automation in Automations. Ready's AI helps you write messages and check them against spam filters, and the in-app assistant answers questions about your account. On a new account, inbound replies go to the inbox for a person to answer.

What happens if an automation fires at 11 PM?

Ready holds sends that fall outside permitted local hours for the recipient's area and sends them later. You're charged only when the text actually goes out. 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.

Do I need 10DLC registration to run automations?

For any real volume, yes. An account can send up to 500 texts a month before registering, at its normal rate. After that it must register. Unregistered traffic gets carrier-filtered. Registration is $25 at submit, and most approvals take 2 to 7 days.