Key Takeaways
- Quiet hours are send windows you enforce so promotional (and sometimes reminder) SMS do not land at night in the recipient’s timezone.
- On an Android SMS gateway, quiet hours live in your app/queue — the radio will happily send at 2am if you ask.
- OTP and critical security alerts usually bypass quiet hours; marketing does not.
- BYO carrier: airtime still burns on accidental overnight blasts. Platform pricing is devices + volume.
- Not legal advice — TCPA-minded US practice and other local rules may require windows. Free canary: 300 SMS lifetime.
Glossary intent: what is quiet hours in android sms gateway context. Scheduling feature: scheduled SMS. Transactional context: transactional SMS. Timezone campaigns: schedule by timezone.
You need a working Android phone with a SIM and SMS credit from your mobile operator. Operator message costs are yours—we do not sell carrier SMS balance. Service pricing is based on device count and total SMS sent through the gateway. Pricing. No Unlimited SMS titles.
quiet hours
hold promo · allow OTP
What quiet hours means
A clock policy: outside 21:00–08:00 local (example only), non-urgent messages wait. Recipients live in timezones; your server UTC clock is not their living room.
The handset does not know quiet hours. Your queue does — or you will fund 2am complaints and airtime.
Android gateway context
Jobs send when the device is online. A delayed campaign still needs power, pairing, and operator credit at release time. Setup: device setup.
Which traffic to hold
| Message class | Quiet hours? | Notes |
|---|---|---|
| OTP / 2FA | Usually bypass | User-initiated; measure latency |
| Shipping / receipt | Often allow | Still avoid spammy wording |
| Marketing / promo | Enforce | Consent + STOP; timezone aware |
| Appointment reminders | Often enforce | Local rules may require windows |
| Incident pages | Bypass with care | On-call lists, not customers at random |
Consent / TCPA-minded notes
US marketers often discuss TCPA calling/texting windows and consent proof; other jurisdictions differ. This glossary is operational context, not legal advice. Keep counsel involved for promotional programs. STOP handling: auto-reply and STOP.
Where to enforce
Prefer application-level gates before enqueue. If you use panel scheduling, still tag message class so OTP never sits behind a marketing quiet-hours flag. Confirm live schedule APIs in Developer docs.
Next steps
Define timezone source of truth per contact, unit-test the window, canary a promo at edge hours, watch DLR.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- scheduled SMS campaignsSend later windows
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
