> 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/create-alert-node.md).
# Create alert node
The **Create alert** node creates an alert in the selected call-routing alert source. This is how a call turns into an actionable alert for your on-call team. By default the alert is escalated according to the alert source's own notification priority and [escalation policy](/on-call-management-and-escalations/escalation-policies.md); you can override these per node.
## Select the alert source
1. *(Optional)* In the **Optional title** field, enter a name to label the node on the canvas.
2. From the **Alert source** dropdown, select the call-routing alert source the alert should be created in. If you just created a source and don't see it, click the **refresh** icon to reload the list.
## Accept the alert on answer
Enable **Accept alert on answer** to automatically mark the alert as accepted when a responder answers the call — the first responder to take the call changes the alert status to "Accepted." This is useful when the same node both notifies and connects the responder.
{% hint style="info" %}
A voicemail recorded by an upstream **Voicemail** node is automatically appended to the alert this node creates, so responders can listen to the caller's message from the alert.
{% endhint %}
## Override the alert source defaults
When a **Create alert** node fires, the resulting alert is escalated using the selected alert source's default notification priority and [escalation policy](/on-call-management-and-escalations/escalation-policies.md). On each **Create alert** node you can optionally override these defaults:
1. In the node configuration, enable **Override alert source defaults**.
2. Optionally select a different **escalation policy** and/or **notification priority** (`High` or `Low`). Each field shows the alert source's current default; any field you leave empty keeps that default.
Create alert node with "Override alert source defaults" enabled
## Example
Pair it with routing and voicemail so nothing is missed:
* **Route call → No one available** → **Voicemail** → **Create alert** (with *Accept alert on answer* enabled and a high-priority escalation policy override).
## FAQ
**Does a call create an alert automatically?**\
No. Call Routing 2.0 only creates alerts where you place a Create alert node, giving you full control over when and how alerts are raised.
**Can different branches create alerts in different sources or priorities?**\
Yes. Add a Create alert node per branch and configure each independently, using the override to set a specific escalation policy or notification priority.
**Are voicemails attached to the alert?**\
Yes — a voicemail from an upstream Voicemail node is appended to the alert created by this node.
---
# 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/create-alert-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.