# Overview

<figure><img src="/files/gIXSiq8BXVcOqjYsFSB3" alt=""><figcaption></figcaption></figure>

* **Create a war-room Slack channel** to gather resources and handle incidents.
* War Room Channel **stays up to date** with all the following information :
  * Incident Status
  * Incident ETA
  * Current Assignee
  * Business Impact
  * Action Item Created
  * Additional Information (Customization)
* **Assistance** in war-room channel
  * Automatically Created Zoom Channel
  * Automatically Jira main ticket for tracking issue
  * Links to all dashboards
  * Additional Information (Customization)
* **Ticketing Update:**
  * **2-way sync of comments on Jira** and Slack Channel. The following information would be synced
    * Severity SLA
    * Ticketing Board
    * Assignee
    * Action Items :
      1. Ticketing Board
      2. Assignee
    * Taggings: Labels and Components
  * **Creation of action items.**
    * Severity SLA
    * Ticketing Board
    * Assignee
    * Action Items :
      1. Ticketing Board
      2. Assignee
    * Taggings: Labels and Components
* **Paging Oncalls** for other teams
* **Automatically RCA / Postmortem** Documentation
  * Choose RCA Template with auto-filled with the following information
    * Business Impact
    * MTTR
    * Root cause
  * **Automatic Timeline Generation**
    * Status changes
    * Severity changes
    * User role assignments
    * Pinning Slack Conversations
      * Messages - these are timestamped and added to the RCA showing which user sent the message
      * Images - these are added to the RCA as attachments - note that if an image is attached with a message, only the picture is attached to the incident
  * Automatically Add Action Items Generated
* **Send out internal status updates** to other users/ stakeholders
  * Send updates via Slack
  * Send updates via Email
* **Scheduled Actions**

  By default, the app will look for incidents that are not resolved that are older than 7 days. You may adjust this behaviour via the scheduler module if you wish.
* **Summarization**
* **Dedupe**
* **Reporting**

**With Pagerly, you have the liberty to add customization for your use case**


---

# 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://docs.pagerly.io/incidence-response/overview.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.