To schedule an SMS with an API, you either call a scheduling endpoint with a send time, or you keep the text in your own queue and call the normal send endpoint when the time comes. Both work. The hard part isn't the call, it's deciding which clock the send time is on and what happens when it lands in a recipient's quiet hours.

This post compares the two patterns, shows how Ready's scheduling endpoint works, and covers time zones and quiet hours, which cause most scheduled-text bugs.

Two ways to send later

The first pattern hands the delay to the provider. You send the text and a timestamp, and the provider holds it. The second keeps the delay in your system, with a job queue or a cron that fires the send at the right moment.

Provider schedules itYour queue schedules it
Moving partsOne API callA queue, a worker, retries
Cancel or changeNeeds a cancel route from the providerDelete or edit your own row
Recipient-local logicYou compute the timestamp up frontEvaluated at send time, with fresh data
Failure modeProvider-side hold you can't inspectA missed run or a duplicate

Provider-side scheduling is the simplest when the time is fixed and known, like a reminder 24 hours before an appointment. A queue is better when the rule depends on facts that can change before the send, like whether the contact has since opted out or booked.

How scheduling works on Ready

Ready schedules one text to one contact with POST /sms/schedule. The body carries message, send_at and either contact_id or to. The send_at value is ISO 8601 with a Z or an offset, such as 2026-12-01T15:00:00Z. Nothing is charged until the text sends. The details are in the scheduled messages docs.

To schedule one text to many people, create a campaign: POST /campaigns with scheduled_at takes a whole list, segment or set of contact ids in one request, paces it and holds it for quiet hours; see the campaigns API. The bulk send has no send time and takes at most 100 recipients per call. For the in-app side, our post on how to schedule a business text message covers the dashboard options.

Because a scheduled text is billed when it sends, the cost is the same as a normal text: $0.0075 per segment plus a $0.0045 carrier fee, and it excludes screening if you've switched that on.

Store UTC, but compute from the recipient's zone

Store every send time in UTC and send an explicit offset or Z. A timestamp with no zone is a bug waiting for a daylight saving change. The more important rule is about where the time comes from.

A reminder for "9 AM" means 9 AM where the recipient is, not where your server is. So the steps are:

  1. Decide the local rule: "9 AM on the day before the appointment."
  2. Find the recipient's time zone from their area code or from a zone you've stored.
  3. Convert that local time to UTC.
  4. Send the UTC value as send_at.

Use a time zone database, with names like America/Chicago, instead of fixed offsets. A fixed offset is wrong for half the year in any zone with daylight saving. Area codes are a reasonable guess for a mobile number but not a certain one, since people keep their numbers when they move. If you've collected an address or a zone at signup, prefer that.

One edge case: a local time that doesn't exist, such as 2:30 AM on the spring-forward night. Your library will either shift it or throw, so test that path on purpose.

Quiet hours are the real constraint

Scheduling doesn't override quiet hours. Ready enforces them based on the recipient's area, and the federal window most senders plan around is 8 AM to 9 PM local time. Some states are stricter, so the safe habit is to schedule inside a conservative daytime window and not at the edge of one. Our posts on quiet hours across time zones and calling hours by state cover the details.

What Ready does with a text that lands in quiet hours depends on its type:

  • Campaigns, drip campaigns and automations wait up to 24 hours for the window to open.
  • A text you type in the dashboard or inbox to one person is scheduled for the recipient's next allowed time and sends itself (Cancel is in the thread). 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. Send "hold_until_allowed": true and Ready holds it for up to 24 hours instead, charged only when it sends. Or, to send it when the window opens, send the same text to POST /sms/schedule with send_at set to the answer's next_allowed_at.
  • A reply to a contact who texted you in the last 24 hours can go out at any hour.

The practical consequence for a developer: don't treat a scheduled send as guaranteed. Pick times well inside the window, and handle the refusal case in the code that reads results, instead of assuming every scheduled text sends.

Patterns that hold up

A few habits keep scheduled texts from going wrong.

  • Re-check before you send. If you run your own queue, look up the contact's opt-out status at send time, not at schedule time. A STOP between the two should win. Texts you schedule on Ready are rechecked for opt-outs, quiet hours and balance when they go out, so the check is already done.
  • Use idempotency keys on your own sends. If a worker crashes and the queue redelivers, the same Idempotency-Key stops a second text. Our post on idempotency keys and duplicate texts shows the pattern.
  • Spread the load. A thousand texts scheduled for exactly 9:00:00 AM hit your own rate limits and the carrier's per-second limits at once. Add jitter of a few minutes.
  • Keep a cancel path. Appointments move. Record what you scheduled against the booking, and cancel with DELETE /sms/schedule/:id, so a reschedule doesn't leave the old reminder in place.
  • Log the intended local time next to the UTC time. When a customer says "I got this at 6 AM," you'll want both.

A worked example

Assume a clinic's app reminds patients at 9 AM local time the day before an appointment, and an appointment is on 2026-12-03 at 2:00 PM in Chicago. The reminder is due on 2026-12-02 at 9:00 AM Chicago time. In December, Chicago is six hours behind UTC, so send_at is 2026-12-02T15:00:00Z.

The reminder contains no health details, just the time and a way to reply. Ready isn't HIPAA compliant and doesn't sign BAAs, so keep diagnoses, medications and results out of any text.

The call carries that timestamp along with the patient's number or contact ID and the message. If the patient texts STOP the night before, a text scheduled on Ready is rechecked for opt-outs at send time, so the STOP wins. Cancel a scheduled text with DELETE /sms/schedule/:id.

The short version

Choose provider-side scheduling when the time is fixed, and your own queue when the decision depends on live data. Store UTC, compute from the recipient's zone, and stay well inside quiet hours. The API quickstart is the fastest way to try a first send before you add timing on top.