> 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/incident-comms-and-status-pages/getting-started.md). # Getting started ilert's incident comms product is a suite of capabilities to effectively communicate incidents to stakeholders and external users. ## What is incident communication? Incident communication is the process of informing users that a service is experiencing issues in a way that will likely impact the user experience. ## Why use ilert's incident comms features? * Spend less time on manual incident communication and focus on resolving incidents. * Build trust with your customers by keeping your users in the loop during an incident * Reduce incoming support requests during incidents ## The basics * [**Incidents**](/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/incidents.md) are the main way to communicate with your users when you are experiencing user impacting issues with the services you provide to them. * [**Services**](/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/services.md) model business capabilities to which subscribers can subscribe to receive updates about incidents. Any user in ilert can subscribe to incidents, services and status pages. * [**Status pages**](/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/status-pages.md) are one way to help you inform users about outages and maintenances of one or more service. * [**Metrics**](/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/metrics.md): Use metrics in status pages to showcase how well your services are performing. You can submit your own metrics data or import metrics from your existing tools (e.g. Datadog). --- # 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/incident-comms-and-status-pages/getting-started.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.