IOSOR
LearnSign InConnection applicationRestore Access
  1. IOSOR
  2. /Knowledge hub
  3. /Quiet hours

Quiet hours

Timezone send windows enforced as policy — not campaign send-at queues you schedule.

3 guides in this topic

  • Explicit Naming of Transactional Quiet Hours Overrides

    Learn why transactional overrides like OTP and P1 alerts must be explicitly named in IOSOR webhook payloads rather than bypassing quiet hours silently.

  • Quiet-Hour Windows Enforced Before Production

    Validate quiet-hour time window enforcement and queue mechanics on prepaid balances before launching live marketing or A2P SMS campaigns in IOSOR.

  • Quiet Hours as Policy, Not a Send-At Queue

    Learn why quiet hours enforcement belongs at the policy engine layer in IOSOR rather than acting as a delayed execution send-at queue for A2P SMS traffic.

Adjacent topics

  • Opt-out & consent

Not this hub: Send scheduling · Ops playbooks

Ready for a controlled prepaid path?

Tell us destinations, monthly volume, and compliance constraints. We will map onboarding clearly.

Apply for access
AboutKnowledge hubSite mapnFADP Privacy PolicyGDPR ComplianceTerms of ServiceSLA AgreementB2B Master AgreementApply for access

English is the sole legally binding language of IOSOR legal documents. Summaries in other languages are for convenience only.

© 2026 IOSOR · All rights reserved.🇨🇭 Switzerland