When you text through a general-purpose messaging API, the API sends when you call it. Deciding whether 9:40 PM in the recipient's time zone is an acceptable moment to text is your job. Twilio gives you the tools to schedule and to look up a number, but the decision logic is code you write. Check Twilio's current docs for what they offer, since features change.
Ready is built the other way: the send path knows about quiet hours and acts on them. Both approaches are workable. The question is who maintains the rules.
What you build on a raw API
To respect quiet hours on a CPaaS you need:
- The recipient's likely time zone, usually inferred from the area code.
- A rule table: federal windows plus stricter state ones.
- A scheduler that holds a message and releases it later.
- A policy for retries that don't wake someone at 2 AM.
- Tests, because a bug here is a compliance bug.
State rules also drift. Texting hours in some states are narrower than the federal baseline, and an area code isn't a residence. Even a careful build leaves edge cases.
What Ready does
Ready bases quiet hours on the recipient's area. What happens next depends on how the text was sent:
- Campaigns, drip campaigns and automations wait up to 24 hours for the window to open.
- A text typed in the dashboard or inbox to one person is scheduled for the recipient's next allowed time, however far off, and shows in the thread.
- An API text is held only if the window opens within 6 hours. Otherwise it isn't sent, and your code sends it again after the window opens.
- A reply to someone who texted in the last 24 hours can go out at any hour.
For developers, the refusal is a 409 QUIET_HOURS_BLOCK. We show how to handle it in handling the quiet hours 409 in an SMS API. The multi-time-zone case is covered in quiet hours across time zones.
Side by side
| Concern | Raw CPaaS | Ready |
|---|---|---|
| Time-zone inference | You build | Built in from the recipient's area |
| Hold and release | You build a scheduler | Held for campaigns and automations |
| Single API send outside window | Sends unless you stop it | Held or refused with a 409 |
| Solicited replies | Your rule | Allowed at any hour within the reply window |
| Responsibility | Yours | Still the sender's |
That last row deserves emphasis. Quiet-hours enforcement lowers the chance of a bad send. It doesn't make a sender compliant by itself, and it doesn't replace consent, a clear opt-out or legal advice for your use case.
Frequently asked questions
Can I override quiet hours?
Not for marketing sends. A solicited reply inside the reply window is the exception.
Does Ready use the recipient's real location?
It uses the area, not a verified address. A number that has moved is an edge case, as on any platform.
The practical takeaway
Choose where the rule lives and test it. If you'd rather own it yourself, a CPaaS is fine. If not, read the messages API docs and try a send in quiet hours on a test account.