# Incident

To set up incidents, navigate to the incident section and click on the configure button located at the top right corner of the screen.

<div align="left"><figure><img src="/files/aQIfgDp296SR8QI6F3Rh" alt=""><figcaption></figcaption></figure></div>

The usual configuration works if you follow the process of creating a ticket/issue for each production incident in your Issue tracker.

\
Click on the configure button and select the basis for this identification"By type", "By label" or "By Custom filed". Mention the identifier & you can further narrow it down to the priorities to be very specific.

<div align="left"><figure><img src="/files/m0ieHD8wW2d9d6p2QesT" alt=""><figcaption></figcaption></figure></div>

Once done, click on the save button. The data will be updated shortly.

If you have a different process and would like to set it up, just email us at <hello@typoapp.io> with the details, and we'll set it up for you right away.

For further queries or to understand this in detail you can pick a convenient slot for a quick meeting [using this link](https://calendly.com/kovid_b/30min). [​​](https://calendly.com/kovid_b/30min)


---

# Agent Instructions: 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:

```
GET https://typo.gitbook.io/typo-help-docs/configurations/incident.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.