> For the complete documentation index, see [llms.txt](https://support.incidentlake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidentlake.com/incidents/create.md).

# Create an incident

How to declare an incident from the console or from Slack.

You can start an incident from the web app or from Slack. Use whichever place the conversation is already happening.

## From the web app

{% stepper %}
{% step %}

## Open Incidents

In the sidebar, choose **Incidents**, then **Create Incident**.
{% endstep %}

{% step %}

## Name what is happening

Give the incident a name people will recognize later — the affected service and the symptom, not a ticket number.
{% endstep %}

{% step %}

## Add what you already know

You can set status, severity, category, and first timestamps now, or leave them and fill them in as the response unfolds.
{% endstep %}

{% step %}

## Create

The incident opens immediately. Share the page with the people who need to help.
{% endstep %}
{% endstepper %}

## From Slack

If Slack is connected for your organization:

* Mention **Incident Lake** in a **thread** and say **go**, optionally followed by a name
* Or use the **Go Incident** action on a message (the ••• menu). If you use it on a channel message, Incident Lake starts a thread for you

The new incident is linked to that thread so later messages can be attached to the record. See [Use Incident Lake from Slack](/incidents/slack.md).

## From Chat

In **Chat**, you can start a conversation about a situation and then create or link an incident so the assistant has that context. This is useful when you are still deciding whether to declare.

## After you create

On the new incident, do these first if you can:

* Assign an **Incident Commander**
* Set severity
* Add the affected configuration items from the CMDB
* Create or apply the first tasks
* Make sure the Slack or Teams thread is linked if the discussion is happening there


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.incidentlake.com/incidents/create.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.