> 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/call-routing/call-flows/support-hours-node.md).
# Support hours node
The **Support hours** node branches a call flow based on your defined [support hours](/alerting/configure-alerting/support-hours.md), so callers reach the right destination depending on whether they call inside or outside of working hours — for example a live responder during the day and a voicemail at night.
## Select your support hours
1. *(Optional)* In the **Optional title** field, enter a name to label the node on the canvas *(e.g., "Business hours").*
2. From the **Choose support hours** dropdown, select an existing support-hours definition. The node will evaluate each call against this definition's schedule and time zone.
3. If you just created a new definition and don't see it yet, click the **refresh** icon next to the dropdown to reload the list.
{% hint style="info" %}
Support-hours definitions are created and managed under **Alerting → Support hours**. See [Support hours](/alerting/configure-alerting/support-hours.md) for details on defining schedules, holidays and time zones.
{% endhint %}
Support hours node configuration
## Branches
The Support hours node adds two branches to the flow. Click the **+** icon under each branch to define what happens next.
| Branch | Taken when |
| ----------------------- | --------------------------------------------------- |
| `During support hours` | The call arrives inside the selected support hours. |
| `Outside support hours` | The call arrives outside them. |
The node adds a "During support hours" and an "Outside support hours" branch
## Example
A typical business-hours flow:
* **During support hours** → [Route call](/call-routing/call-flows/route-call-node.md) to the on-call schedule, then [Create alert](/call-routing/call-flows/create-alert-node.md).
* **Outside support hours** → **Voicemail**, then [Create alert](/call-routing/call-flows/create-alert-node.md) so the recording reaches the team.
## FAQ
**Which time zone is used to decide the branch?**\
The time zone configured on the selected support-hours definition. Update it under **Alerting → Support hours**.
**Can I use the same support hours in more than one call flow?**\
Yes. A support-hours definition can be referenced by multiple Support hours nodes across different call flows.
**Can I nest support hours (e.g. business hours vs. extended hours)?**\
Yes. Add another Support hours node on one of the branches to create a second, more specific time-based split.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/call-routing/call-flows/support-hours-node.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.