# How to send LinkedIn messages in a lead's local time zone
> Find each lead's city from their profile, sort them into time zone batches and set a send window so your LinkedIn messages land during their workday.
- HTML: https://getkinlead.com/ai-outreach-time-zone-settings
- Markdown: https://getkinlead.com/ai-outreach-time-zone-settings.md

**Short answer:** Read the city on the lead's profile, convert it to their current local time and send inside a window that falls in their working day. A message that arrives at 3 AM their time reads as automation, even when you wrote every word of it yourself.

## Why a message at 3 AM reads differently

The lead doesn't see your message on its own. They see it next to whatever arrived while they were asleep: newsletters, a recruiter, an internal note from their manager. If your note is fourth in that stack, it's competing with things that got there first.

Timing also says something about the sender. A message that lands at 3 AM their time tells them you're either sending in bulk or sitting eight hours away. Both facts change how much of the message gets read before they decide to close it.

The other side is simpler. At 10 AM a lead is at a desk with LinkedIn already open in a tab, and replying costs them one line. At 10 PM the same reply costs them the last bit of energy they have for the day.

**Sent on your clock**

- You write at 4 PM and it sends at 4 PM, which is 11 PM for the lead
- The alert sits overnight under anything newer
- The lead reads a timestamp and decides it's a bot before reading the words

**Sent on their clock**

- You write at 4 PM and it waits until 9 AM their time
- The message is the newest thing in their notifications
- The lead opens it with most of a workday still ahead of them

## How to find a lead's local time

The location line under the name is the field people update when they move, and most profiles give you a city or metro rather than just a country. Greater Boston, Berlin, Singapore: any of those is enough to work with.

Don't substitute company headquarters. A 200-person agency with a London address might run delivery from Manila, and the profile is the only place that shows up.

If the location is blank or just says United States, you still have options. Read the about section, then check the last few posts before you assign a bucket. Guessing from a company name is how you end up sending into a closed office.

1. **Read the location line first.** It sits under the name and above the headline. Copy the city as written, including the region when there is one, because Berlin and Munich share a clock but Boston and Denver don't.
2. **Check the about section when the line is vague.** United States or United Kingdom tells you nothing useful about the hour. Look for a city, a metro area, or a line about where they actually work.
3. **Scan recent posts for a trip.** If someone posted from a conference in Lisbon last week, they're probably not at their desk in Chicago. Treat that as a temporary exception, not a permanent edit to their record.
4. **Convert to their clock, not yours.** Open a world clock, put both cities side by side and check the offset for today. Offsets move with daylight saving, so look it up rather than trusting memory.
5. **Write the region onto the lead.** Tag the lead with a region so the batch becomes a filter later. A region you're holding in your head is a region you'll forget by Thursday.

## Group leads into batches and send them in the right order

Most teams don't have a time zone problem. They have a list with no region column. Once every lead carries a region and a local start time, scheduling turns into a filter.

Three buckets cover most lists: the Americas, Europe and the Middle East, and Asia Pacific. More than that and you'll spend the day checking clocks instead of talking to people.

If your list already lives in a spreadsheet, [import a CSV of LinkedIn profile URLs](/ai-sdr-csv-import-workflow) with the region column filled in rather than tagging leads one at a time.

1. **Sort the day by region, not by lead.** The sun moves east to west. Start with Asia Pacific, then Europe and the Middle East, then the Americas, and your day becomes one continuous wave instead of four interrupted ones.
2. **Start with the batch that's awake now.** If your morning begins at 8 AM in New York, the Asia Pacific window is already closing. Either start earlier or accept that Asia Pacific gets the early slot and the Americas get your afternoon.
3. **Keep one window per bucket.** Send the whole batch inside a single window rather than sprinkling it through your day. A lead in Berlin gets one consistent morning, not a message at 9 AM and a follow-up at 4 PM.
4. **Move one lead, don't redraw the map.** If someone in the wrong bucket gets a badly timed message, move that person. Rebuilding the region scheme every Monday is how scheduling slowly becomes the entire job.

```
full_name,profile_url,city,region,window_start_local
Dana Whitfield,linkedin.com/in/dana-whitfield,Austin,americas,09:00
Marcus Ibe,linkedin.com/in/marcus-ibe,London,emea,09:00
Priya Raman,linkedin.com/in/priya-raman,Singapore,apac,09:00
Elena Sokolova,linkedin.com/in/elena-sokolova,Berlin,emea,09:00
```

## Choosing a send window that fits the role

Business hours is the default for a reason. It's when a buyer is at a desk with LinkedIn open in another tab. If you only pick one window, pick that one.

Extended hours help when your buyer has nobody filtering the inbox. The trade is real: an 8 PM message can land while someone is putting a kid to bed, so it has to be short enough to answer in one line.

Any time is the honest answer for a list spread across six continents that you can't split any further. Better than not sending, worse than doing the work of splitting it.

| | Window | Local hours | Who it suits |
| --- | --- | --- | --- |
| Business hours | 9 AM to 5 PM | Corporate roles, larger companies, anyone whose calendar is mostly internal meetings |
| Extended hours | 8 AM to 8 PM | Founders, agency owners and freelancers who answer their own messages |
| Any time | No restriction | One list spread across several regions that you can't split further |

## Timing the connection request and the follow-up

The invite and the first message are two separate sends with two separate clocks. A request that arrives at 9 AM their time sits near the top of the invite list while the lead is clearing notifications. One that arrives at midnight is buried by the time they open the app.

The message after an acceptance should also land in working hours, but the gap matters less than the hour. If they accepted at 2 PM, a message at 9 AM their time the next morning reads like a person who noticed. Ten minutes later reads like a sequence.

- **you:** Dana, saw you moved into the agency ops role at Northwind in March. Most agencies that size end up with client work spread across three tools by the second quarter, so I'm curious how you're holding it together.
- **them:** Four tools and a spreadsheet, honestly. What are you building?
- **draft:** A single board that shows client work, hours and the pieces that are slipping, in one place. Worth 15 minutes next week to see whether it fits how your team already works?

## What breaks the schedule mid-campaign

Daylight saving moves offsets twice a year, and it happens on different dates in different countries. The US changes in mid-March and the UK at the end of March, so for a couple of weeks London and New York sit four hours apart instead of five.

Travel is the other one. People post from conferences, mention being in a city for a week, change their location line for two days and change it back. Check recent posts before assuming, and don't rebuild the whole list around one trip.

Public holidays split the same way. A bank holiday in Germany isn't one in the US, so a perfectly timed European batch can land on a day when nobody is checking LinkedIn at all.

> Check the offset in the week you send, not the week you built the list. It moves twice a year and the two sides don't move together.

## Doing this with Kinlead

Kinlead keeps the send window on the campaign: business hours, extended hours or any time, applied in the lead's time zone. You pick the window once and it stops being a calendar problem.

Pace is separate from the window. Each connected LinkedIn account sends at most one action every 5 minutes, inside whatever daily invite and message limits you set yourself. Nobody can give you the number LinkedIn allows, because LinkedIn doesn't publish one, so your limits and the window are the two dials you control.

- Outreach runs from your own LinkedIn account, connected through Unipile, and Kinlead never stores your password.
- Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.
- Replies from every campaign land in one inbox, sorted with interested ones first, and you get an email when someone answers.

## Related

- [Campaigns and send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)
- [LinkedIn account safety](https://getkinlead.com/features/linkedin-account-safety.md)
- [Cleaning a lead list by CSV](https://getkinlead.com/cleaning-linkedin-lead-lists-via-csv.md)

## Common questions

**What happens if my message arrives at 3 AM their time?**

It still arrives. It lands under whatever came in after it, and the timestamp tells the lead you're either automated or on another continent.

**How exact does the location need to be?**

A country is rarely enough. A city or metro area is. If the profile only says United States, check the about section and recent posts before you assign a bucket.

**Should I send manually to get the timing right?**

Manual sending gives you precise timing on twenty messages and eats your morning. Scheduling exists so you keep the same timing while you do something else.

**How do I handle a lead who travels constantly?**

Use the profile location as the default and move one lead when a post shows they're somewhere else. Don't rewrite the buckets for one trip.

**Can I send outside business hours on purpose?**

You can, and for some buyers it works. Use that window for the whole bucket rather than alternating, or the pattern starts to look automated.

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