Send-Window Planner.
Pick the countries you're messaging and your own timezone. For each market you get the local permitted marketing window, the same window in your timezone so you know when to hit send, the quiet hours to avoid, and any day restrictions. Then see the overlap window that's compliant across every market at once.
Guidance, not legal advice
Country-specific windows are used only where a regulator's or government's own published text sets one; every other market gets a clearly-labelled general best-practice window. Timezone offsets are approximate — they do not model daylight saving or in-country regional zones. Always confirm the exact permitted hours per market before you launch. This is not legal advice.
We convert each market's window into this zone so you know when to send. GMT+00:00
MENA
Africa
Asia
Europe
LATAM
North America
Oceania
Compliant overlap — when to hit send
A send in these hours (your timezone) is inside the permitted window for all 3 selected markets:
Per-market send windows
| Market | Permitted window (local) | Same window (your time) | Quiet hours to avoid | Notes |
|---|---|---|---|---|
 IndiaGMT+05:30 · approx. | 10:00–21:00 local Regulator-sourced | 04:30–15:30 | 21:00–10:00 | TRAI TCCCPR 2018: time bands outside 10:00–21:00 IST are off by default for promotional traffic; DND-scrubbed; service/transactional 24/7. |
 UAEGMT+04:00 · approx. | 07:00–21:00 local Regulator-sourced | 03:00–17:00 | 21:00–07:00 | Promotional 07:00–21:00 GST; transactional (OTP/alerts) 24/7. Promotional sender IDs need the 'AD' prefix. |
 United KingdomGMT+00:00 · approx. | 09:00–20:00 local Best-practice default | 09:00–20:00 | avoid ~20:00–09:00 |
The short answer
How the windows are worked out
For each market we start from the permitted marketing window in local time. Where a regulator or law publishes a numeric window — UAE 07:00–21:00, Saudi Arabia 09:00–22:00 with a Ramadan ban, Qatar 09:00–21:00, India 10:00–21:00 by default, the US 08:00–21:00 under the TCPA — we use it and tag the row 'Regulator-sourced'. Markets with no verified published rule fall back to a clearly-labelled 09:00–20:00 best-practice window. Each window is then shifted by the difference between the market's approximate UTC offset and your timezone's current offset, so you see exactly when to send. Transactional traffic — OTPs, alerts — is generally exempt from these windows.
Frequently asked questions
What is a send window?
A send window is the range of local hours during which marketing (promotional) SMS is permitted in a given market. Many regulators and operators impose 'quiet hours' — typically overnight — when promotional messages must not be sent. This tool shows each market's permitted window and converts it into your own timezone so you know when to trigger a global send.
Do quiet hours apply to OTP and transactional messages?
Generally no. Across most markets, transactional and service messages — one-time passcodes, delivery alerts, fraud warnings, appointment reminders — are exempt from the marketing time window. Quiet hours apply to promotional/marketing traffic. Always keep promotional and transactional flows on separate, correctly-classified sender IDs.
Where does the timing data come from?
Country-specific windows come only from official texts, listed as sources on BroadNet's regulation guides — for example the UAE's 07:00–21:00 promotional window (TDRA), Saudi Arabia's 09:00–22:00 rule with a Ramadan ban 01:00–12:00 (CST), Qatar's 21:00–09:00 direct-marketing ban (CRA) and India's default 10:00–21:00 band (TRAI). Markets without a verified numeric rule use a clearly-labelled general best-practice window.
How accurate are the timezone conversions?
The offsets are approximate. We use a single representative UTC offset per country and do not model daylight saving time or the fact that large countries (the USA, Canada, Brazil, Australia, Indonesia) span several zones. Treat the converted times as planning guidance and confirm against a live clock for your exact target region before sending.
What is the overlap window?
When you select several markets, each one's permitted window — expressed in your timezone — can start and end at different clock times. The overlap is the set of hours that fall inside the permitted window of every selected market at once. Sending during the overlap keeps a single global blast compliant everywhere. If there's no overlap, you'll need to stagger sends per market or per region.
Is this legal advice?
No. This planner is guidance built from published rules and general best practice. Regulations change, and exact windows can vary by operator, message category, consent basis and season (for example Ramadan). Always confirm the current permitted hours for each market with your provider or the regulator before launching a campaign.
Launching a global campaign?
BroadNet routes on direct operator connections with in-house sender-ID registration and quiet-hours enforcement per jurisdiction. Tell us your destinations and volumes and we'll map the compliant plan.