> 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/chatops/overview.md). # Overview ChatOps at ilert integrates seamlessly with two of the most widely-used collaboration platforms: Slack and Microsoft Teams. This allows you to harness the power of chat to streamline incident management and communication. Below is a brief overview of the core features and their functionalities. For detailed guides on how to use these features with each specific platform, click on the respective links. ### **Report incidents in the chat tool** Simplify incident reporting by allowing team members to report issues directly from their chat interface, without the need for an ilert account. Immediate reporting means faster response times. * [Microsoft Teams Guide](/~/changes/vPSzQFfkdJCVWGT5AL1m/chatops/microsoft-teams/create-alerts-in-microsoft-teams.md) * [Slack Guide](/~/changes/vPSzQFfkdJCVWGT5AL1m/chatops/slack/create-alerts-in-slack.md) ### **Create dedicated incident collaboration channels** For major incidents, create dedicated channels to bring all stakeholders together. This centralized communication space ensures everyone is aligned and facilitates quicker resolution. * [Microsoft Teams Guide](/~/changes/vPSzQFfkdJCVWGT5AL1m/chatops/microsoft-teams/create-a-channel-for-an-existing-alert-in-microsoft-teams.md) * [Slack Guide](/~/changes/vPSzQFfkdJCVWGT5AL1m/chatops/slack/create-a-dedicated-slack-channel-for-an-existing-alert.md) ### **Receive and respond to alerts from your chat tools** Stay informed in real-time. Receive critical alert notifications directly in your chat channels, ensuring you never miss an important update. Amplify your response agility. From acknowledging alerts to re-routing them, handle all alert actions without leaving your chat interface. * [Microsoft Teams Guide](/~/changes/vPSzQFfkdJCVWGT5AL1m/chatops/microsoft-teams/chat.md) * [Slack Guide](/~/changes/vPSzQFfkdJCVWGT5AL1m/chatops/slack/post-alerts-to-a-slack-channel.md) ### **Who is on-call lookup** Need to find out who's on-call? Quickly view the on-call schedule directly from your chat tool, ensuring you can reach the right person at the right time. * [Microsoft Teams Guide](https://docs.ilert.com/chatops/microsoft-teams/look-up-who-is-on-call-in-microsoft-teams) * [Slack Guide](/~/changes/vPSzQFfkdJCVWGT5AL1m/chatops/slack/lookup-who-is-on-call.md) For detailed instructions on setting up and using these features with your preferred platform, please navigate to the respective guides. --- # 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/chatops/overview.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.