Best time to send cold email (by recipient timezone)

Most cold email tools schedule sends in your timezone. So if you're a founder in San Francisco at 9 AM PT, a prospect in Berlin gets your "intro email" at 6 PM their time, buried under everything that came in during the workday.

Send-time-by-recipient-timezone is one of the highest-leverage deliverability moves you can make. Here's the data and the playbook.

What the data says

Aggregated open and reply rates across 50M+ cold emails sent through real mailboxes (not blast-IP services), normalized by recipient timezone:

Three windows consistently outperform:

1. 8-10 AM local, the biggest one. People clearing inbox before the day's meetings start. Reply rate hits its peak here.
2. 2-4 PM local, post-lunch slump. Less competition for attention, readers more likely to reply on impulse.
3. 6-8 PM local, solo "catch up on email" window. Lower volume competition, especially in B2B outbound.

Worst window: 12-2 PM (people at lunch / in midday meetings), and overnight (your mail buried by morning).

Day of week matters too

Weekday performance, all timezones combined:

Tuesday-Wednesday-Thursday are dominant for B2B cold email. Monday is "catch-up day" (your email competes with weekend backlog). Friday afternoon is dead, people are mentally checked out. Weekends are skip-zones unless your audience is consumer.

The simple rule

For B2B cold email, send Tuesday-Thursday at 9 AM in the recipient's timezone. That single rule beats most other optimizations combined.

Why most tools get this wrong

Most cold email tools schedule in the sender's timezone. So a US-East sender hitting "send" at 9 AM ET delivers to:

• 6 AM PT, opened the next morning, possibly buried
• 3 PM CET (Europe), afternoon competition window
• 7 PM Asia, overnight, low engagement

If your prospect list is geo-distributed, blast-at-9-AM-ET costs you 30-50% on open rate compared to per-recipient timezone scheduling.

How timezone-aware scheduling works

Two parts:

1. Inferring recipient timezone. From their domain (@nytimes.com → US/Eastern), their stated location in your CRM, or IP-based geolocation if you have it.
2. Per-recipient send queue. Instead of one batch send, the dispatcher queues each email for its individual 9-AM-local-time window and respects per-mailbox rate limits as they release.

This is where the implementation gets complex, you need:

• A worldwide timezone-resolution database (pytz or similar)
• A per-recipient queue, not a per-batch queue
• Daily volume caps that don't fire all 150 emails at exactly 9 AM PT
• Send-window respect (don't queue mail outside the recipient's business hours, even if your sender mailbox has capacity)

Bulk Email Boxer's dispatcher does this natively, set the campaign to "9-11 AM in recipient timezone" and the queue distributes automatically. See the deliverability checklist for the bigger picture.

The exception: "fresh inbox" tactic

If your audience is execs (CEOs, VPs), an alternative play works well: send between 5:30 and 6:30 AM their time. Why?

• Their inbox is empty when they wake up
• Your email is one of the first they see
• Open rate spikes 40%+ versus mid-morning for this segment

The tradeoff: if they delete it on first scan, you lose them entirely (no second chance to be seen mid-day). Best for short, punchy subject lines and one-liner intros.

TL;DR

• Send Tuesday-Thursday at 8-10 AM in the recipient's timezone
• Avoid Monday morning (catch-up clutter) and Friday afternoon
• Avoid 12-2 PM local (lunch / meetings) and overnight
• Use a tool that schedules per recipient, not per sender batch

For higher-volume teams, also lock in your email warmup ramp before you test send-time strategies, sending to the wrong time on a cold domain just compounds the deliverability problem.