> 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/on-call-management-and-escalations.md). # On-call management & Escalations - [Escalation policies](https://docs.ilert.com/on-call-management-and-escalations/escalation-policies.md): Define escalation policies in ilert to guarantee that alerts are delivered through various channels until acknowledged or resolved. - [On-call schedules](https://docs.ilert.com/on-call-management-and-escalations/on-call-schedules.md): Plan on‑call schedules in ilert to orchestrate team rotation, ensure coverage for incidents, and adhere to SLA response windows. - [My on-call shifts](https://docs.ilert.com/on-call-management-and-escalations/on-call-schedules/my-on-call-shifts.md): See all your on-call shifts in one calendar, take over a colleague's shifts, hand yours to someone else, and subscribe to them from a calendar app. - [Recurring schedules](https://docs.ilert.com/on-call-management-and-escalations/on-call-schedules/recurring-schedules.md): Build a recurring on-call schedule from layers of users that take turns on a fixed cycle, optionally limited to certain hours or to your support hours. - [Create schedules using ilert AI](https://docs.ilert.com/on-call-management-and-escalations/on-call-schedules/recurring-schedules/using-ilert-ai-for-schedule-generation.md): Describe a rotation in plain language and let ilert AI fill in the recurring schedule form for you to review and save. - [Static schedules](https://docs.ilert.com/on-call-management-and-escalations/on-call-schedules/static-schedules.md): Create a static on-call schedule by placing individual shifts on a calendar, for coverage that follows no repeating pattern. - [Coverage requests](https://docs.ilert.com/on-call-management-and-escalations/on-call-coverage-requests.md): Use ilert to request coverage swaps when you need to adjust your on‑call shift, with transparent review and approval workflows. --- # 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/on-call-management-and-escalations.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.