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

# Office hours and holidays

> Set default and custom office hours with timezones, shifts and holidays, and see which features follow them: handoff, team assignment, SLAs and calls.

Office hours tell OpenCX when your human agents are working, so it knows when a handoff will reach someone and when the clock on an SLA should stop. Set one default schedule for the workspace, then add custom schedules for teams, SLA policies or sequences that keep different hours.

> [!NOTE]
>
> **Settings → Office Hours** in your [OpenCX dashboard](https://platform.open.cx/settings/office-hours). Viewing requires the **Office hours** permission; creating, editing and deleting schedules requires write access to it.

## Default and custom office hours

| | Default office hours | Custom office hours |
| - | - | - |
| How many | One per workspace | As many as you need, each with a unique name |
| Used by | The whole workspace, and every team set to **Use organization default** | Teams, SLA policies, sequences and workflows that select it by name |
| Timezone | Also your workspace timezone | Its own |

A schedule with no shifts is open around the clock, except during its holidays and closures. Until you save default office hours for the first time, OpenCX treats your workspace as always open.

## Set your default office hours

**1. Pick a timezone**

Under **Default office hours**, choose the **Timezone** your team works in. This is also the workspace timezone that AI instruction schedules use, and the timezone in which the AI agent sees the current date and time.

**2. Add shifts**

Click **Add shift**. A new shift starts as **Monday To Friday**, 09:00 to 17:00. Pick a single day, **Everyday**, or a range such as **Sunday To Thursday**, then set the start and end times. Add a shift for each block of hours.

**3. Add holidays (optional)**

Under **Holidays and exceptions**, click **Add** for each holiday or one-off change. See [Add holidays and exceptions](#add-holidays-and-exceptions).

**4. Save**

Click **Save changes**. **Reset** discards your edits. The save bar only appears while you have unsaved changes.

## Add holidays and exceptions

Each exception has a name, a type, a start and an end date and time, and an optional **Repeat every year** switch.

| Type | Effect |
| - | - |
| **Holiday (closed)** | Closed for the whole period, even during a shift. Workflows that check working hours also see **Is Holiday**. |
| **Closed** | Closed for the whole period, even during a shift. |
| **Extra opening hours** | Open for the whole period, even outside your shifts. |

When exceptions overlap, a holiday wins over a closure, and a closure wins over extra opening hours.

* Times use the schedule's own timezone.
* The end time is exclusive. For a full day, end at midnight of the following day.
* A yearly exception must span less than one year.
* A schedule holds up to 200 exceptions.
* A local time that does not exist in the timezone, such as an hour skipped by a daylight saving change, is rejected when you save.

## Create custom office hours

![Creating custom office hours named US shipping with the America/New\_York timezone and one shift](https://mintcdn.com/openchat/hiyaCL2S28Hya6Q7/images/ticketing/office-hours-custom.gif?s=186c2e432fd71c0e05133187060f731f)

Create a schedule called US shipping in New York time with a Monday to Friday shift, and it appears under Custom office hours.

**1. Open the form**

Under **Custom office hours**, click **New office hours**.

**2. Name it and pick a timezone**

Enter a **Name**, such as the team that follows it. Names must be unique, ignoring capitalization and surrounding spaces. The **Timezone** starts as your browser's timezone.

**3. Add exceptions and shifts**

Add holidays and shifts the same way as for the default schedule, then click **Create**.

Use the pencil on a row to edit a schedule and the trash icon to delete it. The list shows each schedule's timezone and hours. A filter by name or timezone appears once you have more than eight schedules.

> [!WARNING]
>
> Deleting a schedule cannot be undone. Teams and sequences that used it fall back to the default office hours. SLA policies that used it are left without office hours, so their timers run continuously.

## What follows your office hours

Not every feature reads the same schedule. Check which one applies before you change hours.

| Feature | Schedule it uses | What happens outside hours |
| - | - | - |
| [Handoff](https://docs.open.cx/handoff/settings.md) | Default | With **Allow handoff outside office hours** off, the AI does not transfer to your team and follows **Instructions outside office hours** instead. By default, email sessions can still be handed off. |
| [Team assignment](https://docs.open.cx/teams.md#support-office-hours) | The team's **Support Office Hours**, or the default | Sessions routed to the team wait unassigned and are assigned once the team's hours start. |
| Prohibited topic handoff set to **Within office hours only** | The session team's schedule, or the default | The prohibited topic is recorded but the AI keeps the session. |
| [SLA timers](https://docs.open.cx/ticketing/sla-policies.md) | The policy's **Custom Office Hours** only | Timers pause. With **None** selected, timers run continuously, including nights and weekends. The default office hours are never used. |
| [Phone answer-time SLA](https://docs.open.cx/phone/answer-time-sla.md) | The policy's office hours | Waiting time outside hours does not count. |
| Workflows | **Get Default Working Hours** or **Get Custom Working Hours** | Your workflow branches on the result, for example in [call flows](https://docs.open.cx/phone/call-flows.md). The **Ticket Handoff** trigger also reports **Within Office Hours** from the default schedule, including for transferred calls. |
| Sequences | The sequence's schedule, or the default | With **Only send during business hours** on, messages that come due outside hours wait for the next opening. |

> [!NOTE]
>
> An agent who is already assigned to a session and belongs to the team keeps it outside office hours. Office hours only hold back new automatic assignments.

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| "An office hours configuration with this name already exists" | Another schedule has the same name, ignoring capitalization. | Pick a different name. |
| Saving fails with "End must be after start" or "A yearly exception must span less than one year" | The end is not after the start, or a repeating exception covers a full year or more. | Shorten the period, or turn off **Repeat every year**. |
| Sessions wait in a team during working hours | The team uses a custom schedule with different hours, or the default schedule's timezone is wrong. | Check the team's **Support Office Hours** in [Teams](https://docs.open.cx/teams.md) and the timezone here. |
| None of the above | | Contact OpenCX support with the schedule name and the time you expected it to be open. |

***

## Related Documentation

> [card] [Handoff settings](https://docs.open.cx/handoff/settings.md)
>
> What the AI says inside and outside hours

> [card] [Teams](https://docs.open.cx/teams.md)
>
> Give a team its own schedule

> [card] [SLA policies](https://docs.open.cx/ticketing/sla-policies.md)
>
> Pause timers outside business hours

> [card] [Phone answer-time SLA](https://docs.open.cx/phone/answer-time-sla.md)
>
> Count caller wait time in hours only


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