Does Sending Your Emails at the Wrong Time Cost You More Than You Think?

On 28 May, 585 BC, two armies met on the banks of the Halys River in what is now central Turkey. The Medes and the Lydians had been at war for five years, and this battle was shaping up to be as brutal as the ones before it. Then, in the middle of the fighting, the sky went dark.

A total solar eclipse swept across the battlefield. Both armies stopped dead. Herodotus wrote that the sudden darkness was interpreted as a divine sign—an order from the gods to lay down arms. The battle ended on the spot. A peace treaty followed, and the five-year war was over.

The Greek philosopher Thales of Miletus had reportedly predicted the eclipse, making it one of the earliest recorded astronomical predictions in history. But here's the thing that tends to get overlooked: the eclipse didn't cause the peace. Timing did. That eclipse could have fallen on any day. It just happened to land at exactly the right moment—mid-battle—and that's what made it decisive.

Email marketing works the same way.

Your content might be brilliant. Your subject line, compelling. Your offer, genuinely useful. But if your email lands when your subscriber is three meetings deep, or asleep, or standing in a school pickup queue with zero bandwidth—it gets archived without a second glance.

Send timing is the underappreciated variable that amplifies everything else. And most teams still treat it like an afterthought.

This guide is about fixing that. We'll get into how Customer.io's Recommended Send Time feature actually works, what the performance data looks like, how timing interacts with different audience segments, and how to test it properly without contaminating your other variables.

---

Why "Tuesday at 10am" Is Officially Outdated

Let's address the elephant in the room. If you've ever Googled "best time to send marketing emails," you've almost certainly seen a version of the same answer: Tuesday, Wednesday, or Thursday, somewhere between 9am and 11am or around 2pm.

It's not wrong, exactly. Customer.io's own research on email sending schedules, drawing on data from Moosend's analysis of 10 billion emails, HubSpot, Omnisend, and MailerLite, does confirm that Tuesday consistently ranks at or near the top for open rates.

But here's the problem: that advice is a population average. It's the mean of millions of sends across thousands of different audiences, industries, and geographies. It tells you where the herd is, not where your audience is.

A few things have changed the game:

1. Apple Mail Privacy Protection inflated open rate data. Since Apple introduced MPP, email open rates across the board jumped artificially as Apple pre-loads emails and triggers open pixels automatically. Raw open rate benchmarks are now harder to interpret. MailerLite's 2025 Email Marketing Benchmarks peg average open rates at 42–43%, but acknowledge MPP's distorting effect.

2. Evening sends are outperforming morning sends for engagement. Omnisend's 2025 data found that 8pm sends reached a 59% open rate—significantly higher than the 45% recorded for 2pm sends. Moosend's analysis puts peak click-through rates between 8–9pm, with Monday at 9pm hitting a 9.01% CTR. People open emails in the morning while triaging their inboxes. They read and click in the evening when they're less rushed.

3. Industry and segment matter more than day of week. A SaaS platform targeting enterprise IT buyers has an almost entirely different optimal send window than a DTC skincare brand targeting 28-year-old women. Aggregated benchmarks paper over these differences entirely.

4. Individual behaviour is the only thing that matters at scale. AI-powered send time optimisation now makes it possible to personalise timing at the subscriber level—not just at the list level. Tools like Customer.io's Recommended Send Time use AI to predict the optimal window for each individual based on their actual behaviour. According to Customer.io's own data, this approach increases open rates by 23% over static timing.

The question isn't "when do most people open emails?" The question is "when does this person open emails?"

---

How Does Customer.io's Recommended Send Time Actually Work?

Customer.io's Recommended Send Time is part of its AI feature set, released in October 2025. Here's a plain-English breakdown of the mechanics.

What it does

When you're setting up a newsletter or an email campaign in Customer.io, you can click "Recommend send time" to schedule delivery at the optimal time for your audience. The system uses AI alongside two key inputs: the content of your message and your audience's timezone data.

The output is a recommended time window plus a fallback send time—used for any subscriber whose timezone isn't known.

You can also click "Why this send time?" to get a plain-language explanation of why that time was recommended, and you can provide additional context to refine the suggestion.

What data it draws on

Customer.io's AI recommendation engine uses:

• Subscriber timezone data — either captured automatically via Customer.io's geolocation feature, or set manually via a timezone attribute on the person's profile
• Message content analysis — the AI interprets what the email is about and what kind of engagement it's likely to drive (open-and-read vs. click-and-act), then factors this into timing
• Aggregate behavioural patterns — broader engagement signal patterns associated with your audience type

It does not currently account for individual send-by-send historical open data in the same way some platforms do. But for most teams, the combination of content analysis, timezone intelligence, and AI-modelled patterns delivers meaningful lift with minimal setup friction.

How it integrates with campaign workflows

For newsletters: In the Review step, click "Recommend send time." The system schedules the send at the recommended time across all recipients, adjusted for their timezones.

For campaigns: When you open message Settings, you'll see the Recommended Send Time option. When you accept a recommendation, Customer.io automatically creates a Time Window step directly above the message in the workflow. This Time Window step holds each person in the campaign until their individualised recommended send time arrives.

If a subscriber is already inside the time window when they hit that step, the message sends immediately.

Important: Make sure your messages are set to "Send Automatically", not "Queue Draft." Otherwise, the message will queue at the recommended time but not send—which rather defeats the purpose.

Timezone handling at scale

This is where a lot of teams fall down, and it's worth spending time on.

If your audience spans multiple countries or even multiple time zones within a single country, sending everyone at "10am" is a blunt instrument. 10am EST is 3pm GMT is midnight AEST. The same send time produces wildly different outcomes depending on where the recipient is.

Customer.io handles this via two fields on a person's profile:

• cio_timezone — set automatically when you enable Customer.io's geolocation data collection
• timezone — a manually-set attribute you can push via your data pipeline in any IANA-format timezone string (e.g., Europe/London, America/New_York)

Any subscriber without a timezone attribute falls back to the default fallback time you specify. So for the Recommended Send Time feature to do its best work, you need good timezone coverage in your People data.

A quick audit before you start: go to People in your Customer.io workspace, filter for contacts where timezone and cio_timezone are both null, and assess the coverage gap. If it's significant, turning on geolocation auto-collection will start filling it in for new interactions.

---

How Send Timing Interacts With Audience Segments

Not all audiences respond to timing the same way. One of the biggest gaps in generic timing advice is that it ignores the role email plays in the recipient's day—which is almost entirely determined by who they are and how they work.

Enterprise buyers

Enterprise buyers—VP-level and above at large organisations—tend to be heavy email users by necessity. Their day is structured around meetings, so there are natural pockets of "inbox time": early morning before the first meeting, brief windows between calls, and occasionally late evening.

For this segment, the window between 7am and 9am local time often works well for emails that require a decision or a click. They're fresh, alert, and working through their inbox before the day's meetings begin. Avoid midday and early afternoon entirely—that's when their calendar is densest.

However, complex, high-value content (like a detailed case study or a product comparison) often performs better in the late evening (8–9pm) window, when they're catching up on longer reads.

Practical implication: For enterprise-targeted campaigns in Customer.io, consider segmenting by persona and testing two windows rather than applying one recommended time to your entire list.

SMB buyers

SMB owners and managers wear more hats and check email more sporadically. Their inbox behaviour is less predictable than enterprise buyers, but they tend to have more flexibility in when they engage.

Research from monday.com's send time optimisation analysis identifies that B2B audiences typically show engagement during work hours, with mid-morning and early afternoon being peak windows. But for SMB, lunch windows (12–1pm local) often over-index—they're not stuck in board meetings, so they actually have time to read something during lunch.

Practical implication: Test midday sends against your default morning window. SMB segments frequently show their best CTR data between 12pm and 2pm.

Consumer (B2C)

Consumer behaviour is the most varied of the three, but the research findings here are striking. Evening wins. Consistently.

Omnisend's 2025 data shows 8pm sends achieving a 59% open rate vs. 45% for 2pm. Moosend's click-through data peaks between 8–9pm. The explanation is behavioural: during the workday, consumers triage their inboxes and archive anything non-urgent. In the evening, they settle in, pick up their phone, and actually read things.

This means that if you're sending a B2C campaign at 10am because that's what you've always done, you're likely competing with a flood of work emails for a distracted, time-pressed inbox owner. Move the send to 8pm, and you're arriving when they're relaxed, on the sofa, and open to browsing.

Practical implication: For B2C segments, seriously test evening sends (7–9pm local time) before assuming morning is better. The data strongly favours evening for engagement.

The device dimension

One factor that cuts across all segments is device type. AI-powered send time optimisation frameworks consistently find that mobile and desktop engagement patterns diverge meaningfully:

• Mobile users often engage during commutes (7–9am), lunch breaks, and evenings
• Desktop users show stronger engagement during work hours (9am–5pm)
• Tablet users tend to engage during evenings and weekends

If you have device data in Customer.io (via browser/device tracking or app data), it's worth building segments by primary device and testing timing separately for each cohort.

---

What Do the Real Performance Lifts Look Like?

Let's get specific, because "better engagement" isn't a number you can take to a quarterly review.

23% increase in open rates over static timing is the figure Customer.io cites for AI-powered send time personalisation vs. fixed scheduling (customer.io).

A B2B software company implementing an AI send time optimisation framework saw open rates climb from an average of 23% to 34%—a 47% improvement—within 90 days. Click-through rates improved by 31%. Time spent on manual send-time testing dropped from 4–6 hours per week to under 90 minutes (sendXmail case study).

Adobe Journey Optimizer's published benchmarks note that send time optimisation increases click rates—and sometimes open rates—by approximately 2–10% depending on campaign context and constraints. This is a more conservative, platform-agnostic range, but it's meaningful at scale.

Omnisend's 2025 analysis found a 14-percentage-point difference in open rates between 8pm and 2pm sends in B2C contexts (59% vs. 45%). That's not a rounding error—that's a fundamental shift in campaign performance driven solely by timing.

The nuance here is that performance lift from timing optimisation compounds with other variables. A well-segmented, personalised email sent at the optimal time beats a generic email sent at the optimal time. Timing doesn't save bad content. But it does amplify good content significantly.

---

How to Test Send Timing Without Contaminating Other Variables

This is where most teams go wrong. They decide to test send timing, change the time, and also tweak the subject line, adjust the audience segment, or switch the call-to-action. Then the results are meaningless because they can't isolate what drove the change.

Clean timing tests follow a simple principle: change one thing at a time.

The right way to set up a timing test in Customer.io

Step 1: Lock everything else. Identical subject line. Identical preheader. Identical content. Identical audience. Identical sending domain. The only variable is time.

Step 2: Use a statistically significant sample. For most lists, you want at least 1,000–2,000 recipients per variant to reach statistical significance. If your list is smaller, you'll need more weeks of data before drawing conclusions.

Step 3: Choose your test structure. There are two clean approaches in Customer.io:

• A/B test via campaign splits: Customer.io's A/B testing functionality lets you send the same message at two different times to randomised splits of your audience. This is the most controlled approach.
• Sequential cohort testing: Send time A to your entire list in week one, time B in week two (same day of week, identical content). Less clean than a split, but workable for smaller lists.

Step 4: Measure the right metrics. Open rate is the primary signal for a timing test, but also track:

• Click-through rate — timing often affects CTR differently from open rate
• Click-to-open rate (CTOR) — strips out the MPP inflation problem and shows genuine engagement quality
• Conversion rate (if you can attribute it) — did the better-timed send actually produce more desired actions?
• Unsubscribe rate — a poorly-timed send can spike unsubscribes even if opens look fine

Step 5: Run the test long enough. A single send doesn't give you reliable data. Run each variant at least 3–4 times before drawing conclusions—this accounts for week-to-week variability and removes anomalous weeks from contaminating your results.

Step 6: Don't test during unusual periods. Avoid running timing tests over major public holidays, during bank holiday weekends, or around significant industry events where your audience's behaviour will be atypical.

What to do when results are ambiguous

Sometimes timing tests produce a 2% difference either way—within the margin of error. This is valuable information too. It tells you:

1. Your current timing isn't significantly wrong (no catastrophic misalignment)
2. The bigger performance lever is probably elsewhere—content, subject line, segmentation, or deliverability

Don't chase marginal timing gains at the expense of higher-impact improvements. Use the lifecycle marketing maturity framework to prioritise where timing sits in your overall optimisation roadmap.

---

A Practical Guide to Setting Up Send Time Testing in Customer.io

Here's a step-by-step walkthrough you can follow today.

Setting up Recommended Send Time in a Newsletter

1. Navigate to your newsletter in Customer.io and proceed to the Review step
2. Look for the "Recommend send time" option (you'll need Customer.io AI enabled under Data & Privacy settings first)
3. Click "Recommend send time" — the AI will generate a recommended time and fallback
4. Click "Why this send time?" for an explanation and to add any additional context about your audience or campaign goal
5. Confirm the recommended time and set the newsletter to "Send Automatically"

Setting up Recommended Send Time in a Campaign

1. Open the email message within your campaign workflow
2. Open Settings for that message
3. Click "Recommend Send Time"
4. Select your fallback timezone (used for subscribers without timezone data)
5. Accept the recommended time — Customer.io will automatically insert a Time Window step above your message in the workflow
6. If you want to update the recommendation later, delete the Time Window step and repeat the process to generate a fresh recommendation

Auditing your timezone data coverage

Before relying on timezone-based personalisation, run this quick audit:

1. Go to People in your Customer.io workspace
2. Filter for cio_timezone is null AND timezone is null
3. Note the count — this is your "timezone dark" population who'll receive fallback timing
4. If significant, enable Geolocation auto-collection in Data & Privacy settings to start building this data automatically for new interactions

Setting up a manual timing A/B test

If you want to test two specific send times before deploying Recommended Send Time, here's the approach:

1. Create your campaign as normal with the email content locked
2. In the Experiment/A-B test setup, split your audience 50/50
3. Set Variant A to send at Time 1 (e.g., 10am Tuesday local time)
4. Set Variant B to send at Time 2 (e.g., 8pm Tuesday local time)
5. Let it run for a minimum of 4 sends before evaluating
6. Use CTOR as your primary metric (click-to-open rate), not raw open rate, to minimise MPP distortion

For deeper guidance on A/B testing methodology in Customer.io, the practical A/B testing guide for email marketers covers experiment design, sample size calculation, and result interpretation in detail.

---

How Send Timing Fits Into Your Broader Lifecycle Strategy

Send timing doesn't exist in isolation. It's one layer in a stack that includes content quality, segmentation, personalisation, and journey design. Here's how it connects:

Timing × Segmentation: The best results come when you apply timing optimisation within well-defined segments, not across your whole list. The advanced segmentation guide for Customer.io covers how to build these audience splits.

Timing × Journey stage: Where someone is in their customer lifecycle affects optimal timing. A new subscriber in an onboarding sequence has different inbox behaviour than a churned customer receiving a win-back email. For broadcast sends and newsletters, timing optimisation matters more.

Timing × Deliverability: Sending to a highly engaged cohort during their peak window generates strong open and click signals, which reinforces your sender reputation with inbox providers. The email deliverability guide covers sender reputation in depth.

Timing × Behaviour-triggered vs. broadcast: Behaviour-triggered journeys already solve much of the timing problem by design—the email fires at the moment the subscriber takes an action. Send time optimisation matters most for scheduled newsletters, campaign broadcasts, and time-delayed follow-up sequences.

---

Frequently Asked Questions

What is send time optimisation?

Send time optimisation (STO) is the practice of using data—either aggregate engagement benchmarks or individual subscriber behaviour—to schedule emails at the time each recipient is most likely to open and engage with them, rather than sending everyone the same message at the same time.

How does Customer.io's Recommended Send Time feature work?

Customer.io's Recommended Send Time uses AI to analyse your message content and your audience's timezone data, then recommends an optimal send time for the campaign. For newsletter sends, it applies the recommendation to the whole send. For campaign workflows, it inserts a Time Window step that holds each individual in the flow until their personally recommended time arrives. You need Customer.io AI enabled in your Data & Privacy settings to access it.

Does Customer.io's send time feature personalise timing for each individual subscriber?

The Time Window step in campaign workflows does create individual timing based on each subscriber's timezone. The AI recommendation also factors in your audience profile. For true individual-level behavioural timing (based on each person's open history), you'd need to build custom logic using Customer.io's behavioural data attributes and journey branching—or use the Recommended Send Time as a strong starting point.

What performance lift can I expect from send time optimisation?

Customer.io cites a 23% improvement in open rates for AI-powered send time personalisation vs. static timing. Real-world case studies show 31–47% improvements in open and click-through rates when moving from fixed scheduling to individual-level timing. Adobe Journey Optimizer's platform benchmarks suggest a more conservative 2–10% lift in click rates. Results vary based on how poor your current timing is and how diverse your audience's timezone/behaviour profile is.

Is Tuesday at 10am actually the best time to send emails?

Tuesday consistently ranks highly in aggregate studies, including Customer.io's own 2025 research. But it's a population average, not a prescription. Omnisend's 2025 research found 8pm sends achieved a 59% open rate vs. 45% for 2pm sends. Evening sends typically outperform morning sends for engagement (clicks) even when morning sends edge ahead on opens. The best time to send is always the time your specific audience is most receptive—which only testing or AI optimisation can reveal.

How important is timezone data for Customer.io send time optimisation?

It's critical. Without timezone data on your subscribers, Customer.io can't personalise delivery timing—everyone falls back to your default fallback time. Run an audit in your People section to check coverage. Enable geolocation auto-collection if coverage is low, or push timezone attributes from your CRM or data warehouse via Customer.io's API. The data integration guide for Customer.io covers how to sync this data from external sources.

Should I use different send times for enterprise vs. SMB vs. consumer audiences?

Yes, if your list spans multiple segments. Enterprise buyers tend to be most receptive early morning (7–9am) or late evening (8–9pm). SMB audiences often over-index during lunch windows (12–1pm). Consumer audiences show their strongest engagement in the evening (7–9pm). Applying a single recommended time to a mixed audience averages these out and reduces the effectiveness of the optimisation.

How do I test send timing without contaminating other variables?

Lock everything except the send time: identical subject line, content, audience, and sending domain. Use Customer.io's A/B test functionality to split your audience randomly across two time variants. Run the test for at least 3–4 sends before drawing conclusions. Use CTOR (click-to-open rate) as your primary metric to reduce distortion from Apple Mail Privacy Protection. Avoid testing during holidays or atypical weeks.

How long does it take to see results from send time optimisation?

Most teams see directional data within 2–4 weeks of consistent testing or AI-optimised sending. Reliable, statistically significant data typically requires 6–8 weeks. AI optimisation systems that learn from individual behaviour continue improving for months as they accumulate more data per subscriber.

Can send time optimisation work with a small email list?

It can, but the smaller the list, the less statistically reliable the results. For lists under 1,000 subscribers, individual behavioural patterns are harder to detect and test results take longer to reach significance. For very small lists, start with the aggregate-based recommendations (Customer.io's Recommended Send Time) rather than trying to build individual timing models. Even simple timezone-aware sending is a meaningful improvement over a fixed send time.

Does send timing affect deliverability?

Indirectly, yes. Sending to a highly engaged audience at their peak engagement window generates strong positive signals (opens, clicks) for inbox providers like Gmail and Outlook. These signals reinforce your sender reputation and improve deliverability over time. Chronically poor timing suppresses engagement, which can subtly erode your sender reputation. It's one of many factors that contribute to the email deliverability picture, but not the primary lever.

What's the difference between send time optimisation and behaviour-triggered emails?

Behaviour-triggered emails fire in response to a subscriber action—a signup, a purchase, a page visit—at the moment the action occurs. They already have near-perfect timing by design because the trigger is the moment of peak intent. Send time optimisation applies to scheduled emails (newsletters, campaign broadcasts, time-delayed sequences) where you have a choice about when to deliver. For most lifecycle marketing programmes, both matter: behaviour-triggered journeys handle real-time intent, while STO handles scheduled communications.

Do I need to enable anything special in Customer.io to use Recommended Send Time?

Yes. You need to enable Customer.io AI in your Data & Privacy settings. If you don't see the Recommended Send Time option in your newsletter Review step or campaign message Settings, that's almost always the reason. Once enabled, the feature is available for email messages in both newsletters and campaign workflows. Note that the feature also needs timezone data on your subscribers to personalise timing effectively.

Will send time optimisation fix a bad email?

No. Customer.io's own team put it well: "send time optimization matters at the margins, but it will never save a bad email. The best subject line sent at the perfect time still loses to genuinely useful content sent at an inconvenient hour." Timing is a multiplier. It amplifies good content and good segmentation. It doesn't substitute for them.

---

The Bottom Line

The Medes and Lydians didn't stop fighting because they had bad swords or a poorly executed battle plan. The eclipse hit at exactly the right moment—and that moment changed everything.

Your emails don't need a solar eclipse. They need to arrive when your subscriber is actually present, unhurried, and ready to engage. That's what Customer.io's Recommended Send Time feature is built to do—and with proper timezone data, clean audience segmentation, and disciplined testing, it's one of the highest-leverage, lowest-effort improvements you can make to your email programme.

The gains aren't hypothetical. A 23% improvement in open rates over static timing. A 47% improvement in one documented case. A 14-percentage-point swing in open rate between a 2pm and 8pm send in consumer contexts. These are real numbers from real sends.

If your team is still sending everyone at the same time because "that's what we always do," you're leaving a measurable amount of engagement—and revenue—on the table.

Start with the audit: check your timezone data coverage in Customer.io. Enable the AI feature if you haven't already. Run one properly controlled timing test. The data will tell you the rest.

And if you want a Customer.io Certified Partner to help you build this out properly—from data architecture to campaign testing to full lifecycle optimisation—NerveCentral is here to help.

---

Sources and References

1. Customer.io — Recommended Send Time Documentation
2. Customer.io — Best Day and Time to Send Marketing Emails (2025)
3. Customer.io — AI Features: Enhance Your Marketing Workflow
4. MailerLite — Email Marketing Benchmarks 2025
5. sendXmail — AI Email Send Time Optimisation: How Predictive Timing Increases Opens by 47%
6. monday.com — Send Time Optimization: Deliver Emails When Engagement Peaks
7. Braze — Send Time Optimization: What It Is and Why It Matters (2025)
8. Wikipedia — Eclipse of Thales (585 BC)
9. WIRED — May 28, 585 BC: Predicted Solar Eclipse Stops Battle
10. History Club — The Battle of the Eclipse