> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/support-hours.md).
# Support hours
Set notification priority based on support hours
Define support hours for alert sources and call routing numbers to manage the priority of alert notifications and to route calls to different targets.
### Create support hours
1. Navigate to **Alert sources** --> **Support hours**
2. Click on **Create new support hours**
3. Select the team to which the support hours belong to (if any), give it a name, and enter your support hours.
4. Click **Save**. You can now use these support hours in [alert sources](/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/alert-sources.md#notification-priority-and-support-hours) and call routing numbers to set notification priority of alerts and route incoming call routing calls to different targets based on support hours.
{% embed url="" %}
{% hint style="info" %}
**Global support hours are not yet available for call routing numbers**
Support hours for call routing numbers are not yet global and are specified for each number. Global support hours for call routing numbers will be available very soon; please follow product updates in [ilert release notes](https://docs.ilert.com/ilert-release-notes).
{% endhint %}
---
# 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.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/support-hours.md?ask=&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.
