Segment a Cold Email Campaign by Timezone

How do you segment a cold email campaign by timezone?

Build one campaign per timezone, each with its own local sending window, then split your list by where each lead is and enrol them into the matching campaign. Claude can spin up the copies and sort the leads in a couple of prompts, so every email arrives in the reader's morning.

Start your 7 day free trial Connect the MCP server

No credit card required.

Before you start

You need a HotHawk account and the HotHawk MCP server connected to Claude. It takes a couple of minutes and no code. Full setup is on the MCP server page.

Step by step

1

You ask Claude
Build a US East campaign called Enterprise IT, sending 8 to 11am their time, weekdays.

Claude calls mcp__hothawk__campaigns_create

name "Enterprise IT US East" timezone America/New_York sendingStartTime 08:00 sendingEndTime 11:00 sendingDays Mon to Fri

Claude builds the campaign pinned to Eastern time. It will only ever send in that three hour morning window, so the email is waiting when they open their inbox.
2

You ask Claude
Now clone it for London and Sydney, same copy, same local hours.

Claude calls mcp__hothawk__campaigns_create

timezone Europe/London, Australia/Sydney sendingStartTime 08:00 sendingEndTime 11:00

Two more campaigns, identical copy, each locked to its own local morning. Same email, three time zones, each arriving when the reader is at their desk.
3

You ask Claude
Split my list by the lead's timezone and drop each one into the right campaign.

Claude calls mcp__hothawk__campaigns_leads_create

campaignId per timezone leadIds grouped by region

Claude sorts the leads by their timezone and enrols each group into its matching campaign. A New York lead never gets a 3am send.

The same email, sent at the wrong hour, is a worse email

You can spend a week on the copy and still get it read at the worst possible moment. A prospect in San Francisco who gets your email at 4am their time will not see it fresh. By the time they are at their desk it is under thirty other things, and cold email rarely survives being second.

The fix is not a better subject line. It is arriving in their morning, when the inbox is quiet and yours is near the top. That is a timing problem, and timing is something you can control precisely.

One campaign per timezone, same copy

A HotHawk campaign has a single sending window, so the clean way to cover the world is a campaign per region. Build one pinned to America/New_York sending 8 to 11am, clone it for London, clone it for Sydney, keep the copy identical. Now the same email goes out in three local mornings instead of one global blast that suits nobody.

Claude does the fiddly part. Ask it to build the copies and it sets the timezone, the start and end times and the sending days on each. Then ask it to split your list by where each lead sits and drop them into the right campaign. A London lead goes into the London campaign, a Sydney lead into the Sydney one, and no one gets a send in the middle of their night.

What this does and does not promise

Sending in business hours is a reply-rate play, not a deliverability trick. It will not rescue a weak offer, and we would never tell you an inbox is guaranteed either way. What it does is put your email in front of a person while they are actually working, which is when a good offer gets a reply.

None of this touches the machinery. All three campaigns share the same rotation, the same warmup on real Google and Microsoft inboxes, the same pixel-free sending, whether the lead sits in New York or Sydney. You are not changing how the email sends. You are changing when it arrives, and for cold outbound that alone can move the number.

The HotHawk tools behind this

Every action here is a real endpoint. Claude reaches it over the MCP server, and you can hit the same endpoints directly from the REST API if you would rather build it into your own stack.

mcp__hothawk__campaigns_create Create one campaign per timezone with its own sending window
mcp__hothawk__campaigns_leads_create Enrol each lead into the campaign for their region

MCP server setup Read the API docs

Frequently asked

Why does timezone matter for cold email?

Because timing decides whether your email sits at the top of the inbox or halfway down it by the time they look. An email that arrives in someone's morning gets read on the first pass. One that arrives at 2am is buried under overnight mail before they wake up. Same email, different reception.

Can one campaign handle multiple time zones on its own?

Cleanest is one campaign per timezone. A campaign has a single sending window, so to send everyone their local morning you spin up a copy per region and split the leads by where they are. Claude can build the copies and sort the list in a couple of prompts.

What if I do not know a lead's timezone?

You can usually infer it from country, state or city, and Claude can do that grouping for you from the data on the lead. Where it genuinely cannot tell, put those leads in a sensible default campaign rather than guessing wildly and sending at odd hours.

Does splitting by timezone change deliverability?

The protections are identical across every campaign, because they are properties of your account, not the send window. Rotation, warmup and the pixel-free sending run the same at 8am in New York as at 8am in Sydney. Sending in local business hours does not touch any of that. It just means your email arrives when a person is there to read it.

Do I need to write code?

No. Building the per-region campaigns and sorting leads by timezone is all plain language over the MCP server. The REST API is there if you would rather have your own system assign leads to regional campaigns automatically.

Keep going

Launch a campaign from Claude Build, fill and send a campaign from a chat Schedule sends around holidays Pause on the days nobody is reading AI cold email software The whole picture: what AI runs on inside HotHawk AI cold email Where AI meets your outbound, start here

How to segment a cold email campaign by timezone