# How to Add an Incident
#### Before You Start
* Only **Custom Services** can be selected in the *Affected Service* field (3rd-party services are reported automatically by IsDown).
#### Steps to add an Incident
1. In the sidebar, click **Incidents → New Incident**.
2. **Title** – Enter a short, clear summary (Example: “Checkout API latency”).
3. **Affected Service** – Pick the custom service that’s impacted.
4. **Severity** – Select **Minor** (partial disruption) or **Major** (widespread/critical).
5. **Updates** panel:
* Choose the initial **Resolution Stage** (defaults to **Investigating**).
* Type your first **Update Description** (what you know so far).
6. Click **Create Incident**. Notifications are sent instantly to all configured channels.
If you need any assistance, please contact us via chat or email us at **.**
***
**Related Articles**
* [**How to make an Update from an Incident**](https://help.isdown.app/how-to-make-an-update-from-an-incident)
* [**How to Delete a Custom Service**](https://help.isdown.app/how-to-delete-custom-service)
* [**How to Create Custom Services**](https://help.isdown.app/custom-monitor/how-to-create-custom-services)
---
# 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://help.isdown.app/custom-monitor/how-to-add-an-incident.md?ask=
```
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.