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

# Calling hours

> Restrict a campaign to dial only during windows you set, evaluated in each lead's own time zone rather than yours.

Restrict a campaign to dial only during windows you set, evaluated in each lead's own time
zone rather than your own.

## Before you start

* Calling hours are set per campaign, on the [campaign creation or edit
  screen](/outbound/campaigns/create-a-campaign) — there's no separate calling-hours screen.

## Steps

<Steps>
  <Step title="Open the campaign">
    In the left navigation, select **Campaigns**, then open the campaign and go to its
    calling-hours section.
  </Step>

  <Step title="Add a window">
    Select a **Day**, a **Start (local)** time, and an **End (local)** time.
  </Step>

  <Step title="Add more windows, if you need them">
    Add additional windows for other days or split shifts. At least one window is required.
  </Step>

  <Step title="Save">
    Select **Save**.
  </Step>
</Steps>

<Snippet file="time-zone-note.mdx" />

## Verify

<Check>
  A lead outside every configured window is not dialed, and resumes being dialed once its
  local time enters a window again.
</Check>

## Common problems

* **A lead is dialed outside the hours you set.** Confirm the lead actually has a time zone
  — a lead with no time zone uses the campaign's default, which might not match where they
  actually are. See [Lead fields](/outbound/leads/lead-fields).
* **You're not sure what hours are required.** Calling-hour rules vary by jurisdiction —
  consult your legal counsel to determine the correct windows for your operation.

## Next steps

<CardGroup cols={2}>
  <Card title="DNC lists" href="/compliance/dnc-lists" />

  <Card title="Create a campaign" href="/outbound/campaigns/create-a-campaign" />
</CardGroup>