A good SMS follow-up cadence for an inbound lead is short: one text within minutes, a second the same day if there's no reply, then a few spaced touches over about two weeks, and a hard stop on any reply, STOP or booking. Five or six texts is plenty. More than that stops being follow-up and starts being pestering.

This post is for teams building that schedule into a CRM or vertical SaaS product, so it treats the cadence as a small state machine rather than a list of message ideas. If you want wording for the individual texts, our post on the follow-up text after no response covers it. Here we focus on timing, stop conditions and what the schedule costs.

Start from consent, not from the form fill

A cadence only applies to leads who agreed to be texted. A web form with clear consent language and a phone field qualifies. A purchased list doesn't. Cold contact is by phone and mail; SMS goes to leads who opted in or have replied.

So the first question your code asks is whether you hold the lead's opt-in evidence. If you don't, don't enroll the lead. Your product keeps that evidence in your own form or CRM (we cover how in a consent record schema for developers). When you send through the API, set consent_attested to true only when your records back it up.

The cadence, touch by touch

These offsets are a starting point, not a measured benchmark. Tune them against your own reply data.

TouchWhenPurposeSkip if
1Within minutes of the formConfirm, name the sender, ask one questionLead already replied
2Same day, a few hours laterShort nudge, offer a call timeReply, booking or STOP
3Day 2New angle: a useful detail, not "just checking in"Reply, booking or STOP
4Day 5Offer a choice of two timesReply, booking or STOP
5Day 10Low-pressure last offerReply, booking or STOP
6Day 14Closing text that says you'll stopReply, booking or STOP

The first touch matters most, and we dig into why in the 60-second speed-to-lead window. Everything after it is about being useful without wearing out the welcome.

Notice that touch 3 onward are days apart. Texting the same lead three times in an afternoon rarely helps, and it raises the odds of an opt-out. If a lead hasn't answered by touch 4, a phone call by a person often does more than another text.

Model it as a state machine

Store three things per enrolled lead: the cadence step, the time the next touch is due, and a status. Keep the status list small:

  • active: next touch scheduled
  • replied: a person needs to take over; stop the cadence
  • booked: goal reached; stop
  • opted_out: stop and never re-enroll
  • exhausted: all touches sent with no reply

A worker wakes up, finds active leads whose next touch is due, re-checks the status, and only then sends. That re-check is the part people skip. A lead who replied ten seconds ago must not get touch 3.

Two details keep the state machine honest. First, update the status from inbound events as they arrive, but don't rely on that alone: check again right before each send. Second, make the worker idempotent. Generate one Idempotency-Key per touch per lead and reuse it on every retry, so a crashed job can't send a text twice. Our post on idempotency and duplicate texts explains the pattern.

Send the touch

One touch is one call to the documented send endpoint:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <one UUID per lead per touch>

{"to": "+12125550199", "body": "Hi Dana, it's Pat at Example Dental. Got your request. Is morning or afternoon better for a call?", "consent_attested": true}

Leave from out and Ready picks the number: the one this contact already texts with, otherwise your number closest to their area code. That keeps every touch on the same thread for the lead. Replies land in the inbox and in your webhook, covered in the inbound webhooks guide.

Quiet hours and the timing of each touch

Don't schedule touches at fixed clock times in your server's time zone. A lead in another zone gets the text at 6 AM, or your send is refused.

Ready enforces quiet hours by the recipient's area. A dashboard or inbox text to one person is scheduled for when the window opens, however far off, and an API text is held only if the window opens within 6 hours. Otherwise it isn't sent and the API answers 409 QUIET_HOURS_BLOCK with a next_allowed_at time. Treat that answer as "reschedule", not as a failure: one call to POST /sms/schedule with the same text and send_at set to next_allowed_at sends it when the window opens, so you don't need a retry job of your own. A reply to a contact who texted this account in the last 24 hours goes out at any hour, so a conversation the lead started isn't blocked.

The practical rule: compute each touch's due time in the lead's local morning or afternoon, and keep a reschedule path for the 409. Never retry it in a tight loop. For the broader pattern, see quiet hours across time zones.

Stop rules your code must enforce

Stopping is a product feature. Build all of these:

  1. Any inbound reply pauses the cadence and alerts a human.
  2. STOP and its clear variants end it permanently. Ready honors inbound STOP and blocks the number, but your cadence should also mark the lead opted out so it doesn't keep scheduling.
  3. A booking, a won deal or a lost deal ends it.
  4. To learn of opt-outs as they happen, subscribe to the contact_opted_out webhook (see the webhooks docs). Before a send from another tool, or after a provider migration, check GET /v1/opt-outs/:phone. GET /v1/opt-outs lists only opted-out contacts on this account unless you add ?scope=all, and a STOP held on another account of the same family still needs the per-number check, so it isn't a complete mirror.
  5. A lead who asks for a call instead moves to a call task, not a seventh text.

Opt-outs and numbers on your Ban list are refused up front and not charged, which is a safety net, not a plan. See handling SMS opt-outs.

What a full cadence costs

Here's a worked example with stated assumptions: a six-touch cadence, each text one segment (under 160 characters, no emoji), and a lead who never replies.

  • Six texts, one segment each, is six segments.
  • Each segment is $0.012 all-in: the $0.0075 Standard rate plus the $0.0045 carrier fee.
  • That all-in figure doesn't include screening, the per-segment charge for Scrub lists or Number validation if you switch them on.

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.

Most leads reply or book early, so the average cost per lead is lower than the full six segments. Replies are billed like a sent text, so a back-and-forth costs more than the cadence itself. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. Unless the account turns it off, Ready adds "Reply STOP to opt out" and the business name to the first text to each contact, so a first text near 160 characters can tip into two segments. See pricing for the full list.

The short version

Send touch one in minutes, space the rest by days, stop on any human signal, and respect the recipient's clock. Keep the cadence as a small state machine with a re-check before every send, and use one idempotency key per touch. To try it, sign up and follow the API quickstart, then read the messages reference for the full request.