> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/incident-response/readme.md).

# Incident Response

Locate and check in on people's well-being during an emergency

**Overview**\
Verkada Incident Response helps organizations track the well-being and location of people during an emergency or incident. It allows you to account for employees, visitors, or students quickly and can be used to reunify students with their guardians in school settings.

This collection explains how to set up Incident Response in Verkada Command, including importing sites, managing personnel lists, and building Response Templates that define who must be accounted for, which statuses can be used, and how locations are tracked.

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/incident-response/getting-started/incident-response-portal.md">Incident Response Portal</a></td></tr><tr><td></td><td><a href="/incident-response/configuration/create-response-templates.md">Create Response Templates</a></td></tr><tr><td></td><td><a href="/incident-response/analytics/review-responses-from-command.md">Review Responses from Command</a></td></tr></tbody></table>


---

# 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://help.verkada.com/incident-response/readme.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.
