> 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/ja/readme.md).
# インシデント対応
緊急時に人々の安否を確認し、所在を把握します
**概要**\
Verkada Incident Responseは、緊急事態やインシデント時に人々の安否と所在を追跡するのに役立ちます。従業員、訪問者、または学生の所在確認を迅速に行うことができ、学校環境では学生を保護者と再会させるためにも使用できます。
このコレクションでは、サイトのインポート、担当者リストの管理、誰の所在確認が必要か、どのステータスを使用できるか、場所の追跡方法を定義するResponseテンプレートの作成など、Verkada CommandでIncident Responseを設定する方法を説明します。
---
# 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/ja/readme.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.