Campaign sending windows and timezones: audit the clock that matters

Define the decision

A window such as 09:00–17:00 is incomplete without a timezone. In a geographically mixed list, one campaign window cannot mean local business hours for every recipient. Either accept a documented compromise or create audience groups with schedules suited to their locations. Do not infer a person's timezone solely from an email domain.

Work through the procedure

1. Record the campaign timezone exactly as configured. Prefer a named region in your planning notes over a fixed UTC offset because seasonal clock changes can alter offsets.
2. Choose two representative contacts with verified business locations. Translate the opening and closing times into their local clocks using a current timezone tool.
3. Check a due timestamp against the campaign window rather than comparing it only with the browser display.
4. Review workspace and campaign cap reset zones separately. A local midnight in one setting need not reset every constraint that affects the campaign.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Two-clock worksheet
Campaign: Europe/London, 09:00–16:00
Contact A: business location confirmed in London
Contact B: business location confirmed in New York
For the intended date: convert both window endpoints
Decision: separate Contact B if the resulting local window is unsuitable

Read the result

The worksheet deliberately leaves offsets to the intended date. A copied winter conversion can be wrong in summer or during weeks when two regions change clocks on different dates. The operational decision is whether the converted window fits the audience, not whether a particular hour universally performs best.

Check before moving on

1. Compare both endpoints; a suitable opening time can still create an unsuitable closing time for another region.
2. Recheck imported location data before using it to segment contacts.
3. After a timezone edit, inspect a pending enrollment rather than assuming every previously computed due time has shifted as intended.

Limits and next action

This guide does not promise automatic per-recipient timezone scheduling. Zintara evaluates campaign windows and separately applies delivery budgets. Use the actual settings visible in your workspace, and resolve uncertain location data before making highly specific local-time claims in a message.

Source: Zintara sequence product context