> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/soc-analyst-guide/security-detections/escalations.md).

# Escalations

Escalations ensure that validated or high-impact alerts are promptly raised with customers for confirmation, action, or additional context. The process standardises communication and guarantees timely responses.

***

## When to Escalate

* **Validation Needed:** Confirm if suspicious activity is expected.\
  \&#xNAN;*Example: "Is this user expected to access this system?"*
* **Action Required:** Customer approval or remediation is necessary.\
  \&#xNAN;*Example: "Confirm to lock this account."*
* **Context Needed:** Business-specific insight is required.\
  \&#xNAN;*Example: "Is this application change authorised?"*

***

## How to Escalate

1. Open the relevant alert in the dashboard.
2. Go to **Interactions** in the alert details.
3. Select **Escalate** from the menu.
4. Draft a clear message:
   * Specify the requested action or information.
   * Include context (from `td.alert.message` or Hunt results).
5. Send — the system will:
   * Email designated customer contacts immediately.
   * Record the escalation in the alert’s history.

***

## Follow-Up Protocol

* **Critical Severity:** If no reply within **10 minutes**, trigger an emergency phone call to customer contacts.
* **High Severity:** If no reply within **30 minutes**, follow up via email.
* **All Escalations:** Customer responses are logged automatically in alert history.

***

## Tracking Escalations

1. In the alert dashboard, open **Filters**.
2. Set **Status = Escalated** to view active escalations.
3. Monitor responses and update alert statuses as needed.

***

## Best Practices

* **Be Clear:** State exactly what you need from the customer.
* **Match Urgency to Severity:** Use strict timelines for high/critical alerts.
* **Document Everything:** All escalations and responses are automatically logged for audit and compliance.


---

# 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.threatdefence.com/soc-analyst-guide/security-detections/escalations.md?ask=<question>&goal=<user_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.