> ## Documentation Index
> Fetch the complete documentation index at: /help/llms.txt
> Use this file to discover all available pages before exploring further.

# Send in each contact's working hours

> Each step reaches the contact during their own working day, wherever they are.

A campaign has one **Sending schedule** (for example Monday to Friday, 9:00 to 18:00). With **Send in each contact's working hours** on, those same days and hours are read on each contact's own clock: a contact in Tokyo gets the step in Tokyo's morning, a contact in New York in New York's morning.

## Turn it on

**1. For every campaign**

Go to **Settings > General** and turn on **Send in each contact's working hours**. It is the default for all your campaigns.

**2. For one campaign**

Open the campaign, click **Settings**, and under **Entry and replies** pick **Contact's working hours**: **Default: On** (or **Default: Off**: it follows **Settings > General**), **On** or **Off**. The line under it reads **Each contact's own hours** or **The campaign's time zone**. It applies right away, also to a running campaign.

## Where each contact's time zone comes from

On the contact page, **Time zone** shows the zone Kerux uses and the contact's time now.

| Source | How |
| - | - |
| **Set by hand** | Pick a zone in **Time zone** on the contact page and click **Save**. It always wins. |
| **Import** | A **Time zone** column in your file (for example `Asia/Tokyo`). A value Kerux doesn't know is skipped and the row is still imported. |
| **API** | The `timezone` field of a contact (`POST` / `PATCH /v1/leads`). |
| **Location** | **Automatic**: worked out from the contact's city, country or LinkedIn location ("Tokyo, Japan", "Greater Boston", "München, Deutschland"). |

A location that only names a country with several time zones (United States, Canada, Australia, Russia) needs a city, state or province. Until then the zone stays **unknown**.

## What stays the same

* Contacts with an unknown time zone follow the campaign's own schedule and time zone.
* Daily and weekly limits, warm-up and the spacing between sends are still per account. Nothing goes over an account's limits.
* Daylight saving time is handled for every zone.

## See it

* **Launch**: the checks say how many contacts get the steps in their own hours and how many use the campaign's schedule.
* A contact waiting for their morning shows **Waiting for the contact's working hours** with the time it goes on. In **Logs > Right now** the chip reads **Their hours**, and **Send now** sends it at once (limits still apply).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.