> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/workspace/business-calendars.md).

# Business Calendars

Business calendars define the working schedules that drive SLA clocks and availability-based routing. Create one per team, location, or shift, and attach each where it applies

Business Calendars define the working schedules that control two things in Siit: when SLA clocks run, and who requests get routed to.

Instead of a single workspace-wide schedule, you can create multiple calendars — one per team, location, or shift — and attach each one where it applies.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FMdFRiqe6RhXXlE6K9lru%2FCleanShot%202026-03-23%20at%2017.21.59%402x.png?alt=media&amp;token=3e7d2838-e7dd-4fbc-8595-e54edef49592" alt=""><figcaption></figcaption></figure>

### SLA timing

Each SLA Rule references a Business Calendar. SLA timers only count down during that calendar's working hours — evenings, weekends, and public holidays don't count toward breach. Different rules can use different calendars: your EU team's SLAs run on CET hours, your US team's on ET hours, your P1 incidents on a 24/7 calendar.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2F3TmJNmQEGuKjoYg47qkr%2FCleanShot%202026-03-23%20at%2017.24.55%402x.png?alt=media&amp;token=a4143c8e-8c74-46ad-997d-de38eb4faa19" alt=""><figcaption></figcaption></figure>

### Availability-based routing

Admins are assigned a Business Calendar within an inbox, defining their working hours in that context. Siit routes requests only to admins currently within their calendar's active hours — not to someone who clocked out two hours ago.

Because calendars are set at the inbox level, the same admin can operate on different schedules in different inboxes. An admin covering EU hours in the IT inbox can follow a different calendar in an on-call inbox.

For how calendars interact with inbox assignment methods, exclusions, and routing rules, see [Assignment](https://docs.siit.io/request-management/assignment.md).

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2Fan76dBiGV7zcEXIRgxof%2FCleanShot%202026-03-23%20at%2017.25.57%402x.png?alt=media&amp;token=4c7fc54f-27bb-447e-a3c3-efbbbe5c23a0" alt=""><figcaption></figcaption></figure>

***

*Related:* [*SLAs*](https://docs.siit.io/service-catalog/slas.md) *·* [*Assignment*](https://docs.siit.io/request-management/assignment.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/workspace/business-calendars.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
