Send-time for cold email, and why relevance beats the clock

Best time to send charts are among the most shared and least useful advice in outbound. They average away the only thing that decides a reply, which is whether the email was worth reading in the first place.

The perfect hour is mostly a myth

Universal best-time studies contradict each other because the right time depends on your audience, and averaging across all audiences produces a number true for none. Tuesday at 10am is folklore, not a rule.

More to the point, timing cannot fix relevance. A generic email at the optimal minute is still generic; a relevant one at an odd hour still gets read, because the reader will get to their inbox and the good ones survive the scroll.

What timing actually helps

A few timing factors do matter, for practical reasons rather than magic hours.

• Their business hours, their time zone, so it lands while they work, not at 3am.
• Even sending, spreading volume rather than blasting, which protects deliverability.
• Avoiding the pile-up, Monday-morning and Friday-afternoon inboxes are noisier.
• Consistency, a steady sending pattern looks human to mailbox providers.

What sending schedules look like in practice

Send timing and sending volume are the same decision seen from two angles. A warmed mailbox carries only a modest daily volume of cold email, and whatever that number turns out to be for you, the messages should leave over several hours rather than in one burst at 9:00. Sequencing tools call this throttling: one email every few minutes, with small random gaps so the pattern does not look mechanical.

Spread like that, a day's sending from one inbox covers most of the recipient's working day anyway, which quietly settles the best-hour debate. The window you choose sets where the sending starts, not when each email lands. If your volume needs are higher, the answer is more mailboxes sending less each, not a tighter blast, as covered in how many emails per day is safe.

Time zones matter more than the hour

For export and multi-market outbound, sending in the recipient's local business hours matters far more than hitting a specific clock time. An email that arrives mid-morning for them beats one timed to your own day but landing overnight for them, which is a real reason to handle time zones properly.

A send-timing setup that works

If you want a concrete starting point rather than a philosophy, use this and adjust from your own results:

1. Segment the list by time zone before the campaign starts. One column in the data, checked once, saves every later scheduling headache.
2. Open the sending window at 8:30 local time for each segment and close it around 16:30. Everything lands inside the recipient's working day.
3. Throttle to a human pace. A few emails per hour per mailbox with randomised gaps. No bursts, ever.
4. Keep weekends off by default. B2B replies come from desks. Test weekend sends only after weekday performance is stable.
5. Hold the schedule steady for weeks. Mailbox providers score consistency. A sender that behaves the same every day builds trust; one that lurches between silence and volume looks like a spammer waking up.
6. Time follow-ups by gap, not by hour. Two to four days after the previous touch matters far more than the clock time, and the cadence logic lives in the follow-up sequence, not the scheduler.

Common send-timing mistakes

• Blasting the whole list at 9:00 sharp. A spike of identical messages from one domain is the clearest spam signal you can send. Fix: throttle and randomise.
• Scheduling in your own time zone. A 10:00 send from Vilnius lands at 3:00 in Chicago. Fix: segment by recipient zone and schedule per segment.
• Optimising send-time by open rate. Apple's privacy changes inflate opens and machine-scanning fires them at odd hours, so the winning hour is often an artefact. Fix: judge timing tests on replies only.
• Pausing campaigns for days, then resuming at full volume. The resume spike hurts reputation. Fix: ramp back up over several days, the same way a domain warm-up ramps.
• Testing timing before testing the message. Timing moves replies by fractions; the offer and the list move them by multiples. Fix: spend testing budget upstream first.

Test on your own audience

If send-time interests you, test it on your list rather than importing a study. Your market may behave nothing like the average. And test it against replies, not opens, which are unreliable and would point you at a meaningless optimum. Fold it into normal A/B testing, low on the priority list.

How this plays out across Europe

European multi-market campaigns make timing a logistics question rather than a tactical one. Germany and the Nordics start early and thin out by mid-afternoon, especially on Fridays. France and much of Southern Europe hold a firm lunch pause. The UK and Ireland run an hour behind Central Europe, the Baltics an hour ahead. A campaign covering DACH, the Nordics and the UK from one schedule therefore spans a four to five hour spread of local mornings.

The practical answer is boring: one sending window per market, opened at local morning, with the copy localised to match. We run campaigns in German, English, Lithuanian and Russian from Vilnius on exactly this pattern, and the scheduling layer is set once per market and then left alone. What deserves ongoing attention is the message, not the clock.

Spend your effort upstream

Timing is a minor optimisation, and chasing the perfect hour is time not spent on the list and the message, which decide far more. Get those right, send during their working day, keep volume steady, and the exact minute barely registers.