# How to coordinate LinkedIn outreach across timezones
> Group leads by timezone and set a send window per region so LinkedIn messages land during local business hours instead of sitting unread until morning.
- HTML: https://getkinlead.com/managing-outreach-for-multiple-timezones
- Markdown: https://getkinlead.com/managing-outreach-for-multiple-timezones.md

**Short answer:** Split your lead list by the timezone each person actually works in, then set a send window per region so messages go out between roughly 9 AM and 4 PM local time. LinkedIn doesn't publish exact daily limits on invites or messages, so keep volume modest and spread it across the day instead of firing everything at once.

## Why timing affects your reply rate

A message that lands at 3 AM in your lead's city sits in the inbox overnight. By the time they open LinkedIn, it's under a stack of internal alerts, recruiter notes and connection requests from people who sent theirs at a reasonable hour. Where you sit in that stack decides whether the message gets read at all.

Mid-morning is the usual sweet spot. People have cleared the first rush of the day, answered the urgent messages and settled into work they can interrupt. A note at 10 AM local time reaches someone at their desk and in a work frame of mind.

Timing also changes how the message reads. A note that arrives at 2 AM looks like it came from a script running on a server somewhere. A note that arrives at 10 AM on a Tuesday looks like a person who knows roughly where you are and what your week looks like. The text can be identical and get a different reaction.

LinkedIn doesn't publish exact daily or weekly limits on invites, messages or profile views. What it does look at is how your activity compares to normal human use. Sending one burst across every timezone at once looks less human than spreading the same volume across the working day.

**Poor timing**

- Sending a connection request to a London lead at 2 AM GMT
- Messaging a Singapore lead on a Sunday afternoon
- Following up with a New York lead on Friday at 6 PM ET

**Timing that lands**

- Sending to London leads between 9 AM and 11 AM GMT
- Messaging Singapore leads on Tuesday morning SGT
- Following up with New York leads on Wednesday at 10 AM ET

## Segmenting your leads by region

You can't hold global timing in your head if your list is one flat pile. Split the list by the timezone each lead works in before you write a single message.

Group by timezone rather than by country. The US spans six hours from New York to Hawaii, so a single United States group set to Eastern time will hit California at 6 AM. Europe spans three. Split the large countries into the timezone bands you actually plan to message.

Name each group after the window it serves, not the geography. A group called Europe 8 to 4 tells you what to do with it at a glance. A group called EMEA tells you nothing about when to send.

1. **Pull your target list into one view.** Export the list to a spreadsheet so every location sits in the same column and you can sort it.
2. **Add a timezone column.** Read the location line on each profile and write the timezone band next to it, such as GMT, CET, EST or SGT.
3. **Split into groups by window.** Create a group for each band you plan to message: North America East, Western Europe, Southeast Asia.
4. **Give each group its own campaign.** Separate campaigns let you set a different send window per region without touching the others.

## Defining your send windows

A send window is the block of hours when messages are allowed to leave. Set one per region and leave the rest of the day closed.

For most B2B outreach, 9 AM to 4 PM local covers the working hours without the edges. The first hour of the day is when people triage what came in overnight, and the last hour is when they're closing tabs. Neither is a good moment to ask for a meeting.

If you're targeting founders and executives, shift the window earlier. Many of them start before their team and keep a quiet hour around 8 AM that they use for exactly this kind of message.

| | Region | Local window | Days to skip |
| --- | --- | --- | --- |
| North America East (ET) | 9 AM to 4 PM | Weekends, federal holidays |
| North America West (PT) | 9 AM to 4 PM | Weekends, federal holidays |
| Western Europe (GMT/CET) | 8 AM to 4 PM | Weekends, local bank holidays |
| Southeast Asia (SGT) | 9 AM to 5 PM | Weekends, Lunar New Year week |

## Running the manual send process

Doing this by hand means you are the scheduler. That works if you're strict about it. It falls apart when you send to whoever is convenient at the moment you happen to be at your desk.

The failure mode is drift. You start the day on Europe, get pulled into a call, and by the time you come back the European window has closed and you send to the US list instead. The next morning you can't remember who got what.

Keep a log. One row per region per day with the date, the batch size and the window you used. It takes a minute and it stops you from double-messaging the same person.

1. **Set an alarm for each window opening.** One alarm per region, named after the region, so you know which list is live right now.
2. **Send one region at a time.** Log in, work the region whose window is open, then close the tab. Resist the urge to clear the whole list.
3. **Log the batch.** Write down the date, the region, roughly how many you sent and the window you used.
4. **Check the log before the next batch.** Confirm nobody from today's region already got a message yesterday from a different list.

- **you:** Hi Sarah, saw your post on supply chain planning at Northwind. Worth comparing notes on how you're handling forecast changes?
- **them:** Morning. Just sat down with coffee, so good timing. What are you working on at the moment?
- **you:** Same problem from the other side, forecasting for a 40-person agency. Free Thursday afternoon?

## When the profile doesn't say which timezone

Plenty of profiles list a country and nothing else. United States on four thousand leads is useless for scheduling.

Work down a short list of signals. The location line in the profile header. The city attached to their current role. The office locations listed on the company page. The hour they tend to post. Two of those agreeing is usually enough to place someone.

When the signals conflict, put the lead in the later window. Sending slightly late in their day is safer than sending before they've started.

> If two location signals disagree, schedule for the later window. A message that arrives after someone starts work gets read. One that arrives before they wake up gets buried.

## Keeping follow-ups inside the same window

Follow-ups are where timezone discipline usually breaks. The first message goes out inside the window, then the follow-up fires whenever the sequence says so, which is often the middle of the night for the lead.

Anchor every follow-up to the same window as the first touch. If the first message went out at 10 AM Berlin time, the follow-up goes out at 10 AM Berlin time three days later.

Leave at least two working days between touches. A Friday message followed by a Monday message reads as two messages in one working day from the lead's side of the desk.

Check the calendar, not just the clock. Bank holidays and the week between Christmas and New Year are dead zones across most of Europe. A message sent then sits unread and pushes your next follow-up into an even worse week.

```
Region: Western Europe (CET)
Window: 09:00 to 16:00 CET, Monday to Thursday
Skip: weekends, local bank holidays, 20 Dec to 2 Jan
First touch: connection request with a note under 200 characters
Follow-up 1: +3 working days, same window
Follow-up 2: +4 working days, same window
Stop on: any reply
```

## Doing this with Kinlead

Kinlead keeps leads in [lead groups](/features/lead-groups-and-scoring), and any campaign can point at any group. Set a [send window](/features/campaigns-and-send-windows) per campaign (business hours, extended hours, or any time) and it applies in the lead's own timezone, so you don't convert hours by hand.

Sending runs at a human pace: at most one action every 5 minutes per LinkedIn account, inside the daily invite and message limits you set. Outreach goes from your own account through Unipile, a third-party LinkedIn provider, and Kinlead never stores your LinkedIn password.

If LinkedIn pushes back on an account, Kinlead pauses invites on that account and emails you. Stale pending invitations are withdrawn automatically so the pending pool stays healthy.

> Kinlead doesn't warm up a LinkedIn account for you. It keeps your sending inside the limits and windows you set, and that's the whole job.

## Related

- [Campaigns and send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [LinkedIn account safety](https://getkinlead.com/features/linkedin-account-safety.md)

## Common questions

**Should I use a tool to schedule LinkedIn messages across timezones?**

If your list spans more than two timezones, yes. Manual scheduling means being online at odd hours to hit each window, and one missed day throws the whole rotation off.

**What happens if I send at the wrong time?**

The message gets buried under everything that arrived overnight, and it reads like it came from a script. Both cost you replies.

**How do I find a lead's timezone if it isn't on their profile?**

Start with the location line in the profile header. If it only says United States, check the city on their current role or the office locations on their company page.

**Do weekends count for global outreach?**

In most markets, Saturday and Sunday are dead for B2B. Some regions also run a shorter week, so check the local calendar before you schedule a follow-up.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
