Automated text message systems: software, replies and reminders compared

An automated text system does four jobs: it sends a text when something happens, it answers inbound texts without a person, it sends texts at a set time, and in some products it writes or sends a reply with AI. Most software is good at one or two of these and weak at the others. If you buy before you know which jobs you need, you end up with a tool that handles reminders well and then mishandles STOP replies.

This guide covers each job, what it costs per message, the consent rules that apply to all of them, and the questions to ask before you commit. We make Ready, so we'll point out where it fits, where it doesn't, and where a cheaper or simpler tool will do the job just as well.

The four jobs, defined

Each job has a different failure mode, so treat them separately before you compare vendors:

1. Triggered texts. An event in your system (form fill, booking, payment failure, missed call) fires a text. The risk is that the trigger fires twice, or fires for someone who never consented.
2. Auto-replies. An inbound text gets an instant answer: a keyword response, an after-hours notice, or a STOP confirmation. The risk is an auto-reply that ignores an opt-out.
3. Scheduled reminders. Texts go out at a time relative to an event, such as 24 hours before an appointment. The risk is sending at 6 AM in the recipient's time zone.
4. AI responses. A model drafts or sends a reply. The risk is a confident, wrong answer going to a customer with nobody checking it.

For a longer list of what to automate and what to leave to a person, see what to automate, triggers, and compliance limits.

Triggers: where most automation starts

A trigger needs three things: an event source, a consent check, and protection against duplicates.

Event source. In a CRM like GoHighLevel, the trigger is a workflow step. In your own product, it's an API call from your backend. Ready installs natively into GHL over OAuth. Messages sync both ways and map to each GHL location's sub-account, so a workflow-triggered text and the customer's reply land in the same thread. If you're a software platform texting on behalf of your own customers, you call the API directly:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: 3f1c9a2e-8b7d-4e1a-9c55-2d0f6b7a1e44

{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true}

Duplicate protection. That Idempotency-Key header matters more than it looks. Webhooks retry, and queues redeliver. Without an idempotency key, a retried request sends the text a second time and you pay for both. With one, the retry never sends twice. If a vendor can't tell you how it prevents double sends, assume it doesn't. Full request details are in the messages API docs.

Consent check. consent_attested is your promise that the recipient agreed to receive texts. More on what that does and doesn't record below.

SMS marketing automation workflows covers which triggered workflows to build first.

Auto-replies and opt-out handling

Auto-replies are the simplest automation and the easiest to get wrong. Common types:

• Keyword replies. Someone texts JOIN or HOURS and gets a canned answer.
• After-hours replies. "We're closed, we'll text back by 10 AM."
• Missed-call text-back. A call goes unanswered and a text goes out within seconds. The setup is covered in the missed-call auto-text-back guide.
• Opt-out confirmations. STOP gets a one-time confirmation, and nothing after that.

That last one is required. On Ready, inbound STOP and UNSUBSCRIBE are honored automatically. The opt-out applies across every campaign, so a contact who stopped your promo list can't be reached by your reminder workflow either. Sends to opted-out numbers are refused before they go out and aren't charged. Ask any vendor whether opt-outs are global or per-campaign. Per-campaign opt-outs are how businesses end up texting people who already said stop.

Two cost facts that vendors rarely mention up front:

• Replies are billed. On Ready, an inbound reply is billed like a sent text: the per-segment rate plus the carrier fee.
• Keyword replies don't create consent records. A keyword reply doesn't create a consent record for you.

For wording you can copy, see auto-reply text message examples.

Scheduled reminders, with the math

Reminders are usually the highest-value automation for appointment businesses, and the easiest to price out.

Example assumptions: 2,000 appointment reminders a month. Each is under 160 characters, plain text, no emoji, so each is one segment. Roughly 30% of recipients reply ("confirmed", "can I move it?"). That's an assumed figure, not a benchmark.

On Ready Standard ($0.0075/segment plus a $0.0045 carrier fee):

• Outbound: 2,000 × 1 segment × $0.0075, plus 2,000 × $0.0045 in carrier fees
• Replies: 600 × 1 segment × $0.0075, plus 600 × $0.0045 in carrier fees
• Registration: $25/mo for registration + $2 per number

What changes the bill. Segments are billed, not messages. Add one emoji to a 140-character reminder and the encoding switches to unicode, which allows 70 characters per segment, or 67 per segment when the message splits. That makes it 3 segments instead of 1, and the outbound line becomes 2,000 × 3 × ($0.0075 + $0.0045). Curly quotes and long dashes don't cause this on Ready, because they're swapped for plain characters before sending. Emoji do.

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.

Time zones. Ready enforces quiet hours based on the recipient's area. A reminder scheduled during the recipient's quiet hours is held, sent when permitted, and charged only when it actually sends. This matters if your list spans time zones and you scheduled "9 AM" in your own. For scheduling options on phones and in business tools, see how to schedule a text message. 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.

AI responses: what to automate and what to review

A lot of software now advertises AI that answers inbound texts on its own. Decide whether you want that before a demo decides it for you.

Ready's AI is narrower. The AI message writer drafts and checks messages, including a spam-filter check before you send. Each set of drafts it writes costs the same as 5 texts at your rate. The in-app assistant answers questions and takes actions on your account. Ready no longer lets accounts create AI reply agents. One set up earlier may still reply to inbound texts until you pause its automation in Automations. On a new account, replies are written or sent by a person, or by a rule you configured, such as a keyword reply.

That's a real limitation if you want fully autonomous conversations. If that's a requirement, choose a tool built for it, test it hard on pricing and refund questions, and plan for a human handoff. SMS chatbots: what they can handle covers where handoffs belong. For most reminder, confirmation and lead-response work, rules plus a human inbox are predictable, and a predictable system is easier to keep compliant.

Consent rules that apply to every automated text

Automation sends more texts with less human review, so compliance mistakes repeat at scale. The basics:

• Register first. Unregistered A2P traffic gets filtered by carriers. Ready handles brand and campaign 10DLC registration in-app. You pay $25 at submit (the first month) with no setup fee, and most approvals take 2 to 7 days. Your registered use case has to match what you automate. If you register for appointment reminders and then send promos, expect trouble. If a campaign gets rejected, this guide to decoding and resubmitting a rejected campaign walks through the fix.
• Get consent before the first automated text. Text people who opted in or who contacted you first. Cold outreach belongs on the phone or in the mail, not in an SMS workflow.
• Keep your own consent records. Ready records the sender's attestation on each bulk send and each API send that sets consent_attested: who sent, to how many, and when. That's an audit trail of your promises. It is not a per-contact consent record, and it doesn't store each recipient's opt-in time, wording or page URL. Your form, CRM or store needs to keep those. (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.)
• Scrub high-risk numbers. TCPA exposure runs $500 to $1,500 per text. The standalone TCPA & DNC Litigator Scrub costs $0.005 per contact and checks numbers against known litigator and DNC-complainer lists. It reduces risk, but it doesn't make you lawsuit-proof. Compliance is ultimately the sender's responsibility.

Platform types compared

To be direct about the price comparison: Twilio's per-segment rate and GHL's per-message rate are both lower than our Standard rate. If you have engineers who want to build compliance logic themselves, a raw API is a reasonable choice. With Ready, you're paying to get live in minutes with self-serve registration, with the compliance stack already working.

Questions to ask before you buy

• How does the system prevent a retried trigger from sending twice?
• Are opt-outs global across campaigns, and are sends to opted-out numbers charged?
• Are quiet hours based on the recipient's time zone or the sender's?
• Are replies billed, and at what rate?
• Does AI send replies on its own, or draft them for review?
• Does 10DLC registration happen in the tool, and who fixes a rejection?
• Where are per-contact consent records stored?

The practical takeaway

Write down which of the four jobs you need: triggers, auto-replies, reminders or AI responses. Price out your real message lengths in segments, including replies. Then confirm that opt-outs, quiet hours and registration are handled before the first automated send goes out.

If Ready fits that list, you can sign up and use your first 20 free one-to-one texts, sent by hand from the inbox, to check your reminder or auto-reply wording before registering. Automated sends are paid from the first text. The quickstart shows the API path. If a raw API or your CRM's built-in texting fits better, that's a reasonable choice too.