Send-time test: same campaign, 3 windows

Send-time test: same campaign, 3 windows

A team split 900 identical sends across three dispatch windows to test the "Tuesday 10am" folklore.

— Tue 7-9am local: 38% open, 5% reply
— Tue 1-3pm local: 35% open, 4% reply
— Thu 7-9am local: 40% open, 6% reply

Thursday morning quietly edged out the sacred Tuesday slot. The bigger finding: local-time sending (via Smartlead's timezone detection) beat blasting everyone at one UTC hour by ~3 open points across all windows.

Pros of timezone-aware sending
— Lands at top of inbox, not buried overnight
— Spreads mailbox load naturally
Cons
— Needs reliable timezone data per contact
— Marginal vs deliverability fundamentals

Verdict: 4/5. Worth setting once; don't obsess over the exact hour.

Who it's for: lists spanning multiple timezones. Skip micro-optimizing send time if your placement is still below 80% — fix that first.