> For the complete documentation index, see [llms.txt](https://distance.gitbook.io/distance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://distance.gitbook.io/distance/getting-started/notifications.md). # Notifications ### **Introduction** **Notifications** in Distance determine how your team receives alerts across different parts of the platform. They cover ticket activity, urgent updates, escalation rules, campaign and automation events, and integrations with external tools such as Slack and Microsoft Teams. These alerts help teams stay responsive, reduce missed updates, and maintain consistent communication across workflows. *** ### **Why notifications matter** **Stay informed.** Receive updates on important events as they happen. **Focus on what matters.** Control the type and frequency of alerts to reduce noise. **Improve response time**. Surface urgent and high-priority activity quickly. **Stay connected**. Receive updates directly in the tools your team already uses. *** ### **How notifications work** Notifications in Distance are triggered by specific events across the platform. [**Ticket notifications**](/distance/getting-started/notifications/ticket-notifications.md) are generated when ticket actions such as creation, assignment, or status changes occur. [**Urgent notifications**](/distance/getting-started/notifications/urgent-notifications.md) highlight high-priority tickets and alert selected team members via SMS. [**Escalation notifications**](/distance/getting-started/notifications/escalation-notifications.md) are triggered when predefined conditions are met, ensuring important issues are routed for attention. [**Campaign and automation notifications**](/distance/getting-started/notifications/campaign-and-automation-notifications.md) surface key workflow events such as recipient replies, completions, or failures. [**Integration notifications**](/distance/getting-started/notifications/integration-notifications.md) deliver updates directly into external tools like Slack and Microsoft Teams. Together, these notification types ensure your team stays informed across all critical workflows without needing to actively monitor the system. --- # 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://distance.gitbook.io/distance/getting-started/notifications.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.