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

# Requests

Users categorized as 'company' <mark style="color:green;">make requests directed to 'mss' type users</mark>, following a process defined by 'mss' itself. Once created, the <mark style="color:green;">requests are organized in a paginated list</mark>, prioritized according to established criteria. Additionally, there are filtering and sorting options to facilitate the management of these requests. On the home screen, users <mark style="color:green;">can also view a control panel that displays the current status of the treatment of each request</mark>, allowing for efficient and organized monitoring.

<figure><img src="/files/CKYqksffGeDSmPjyNhGM" alt=""><figcaption><p>Overview Requests Dashboard</p></figcaption></figure>

{% hint style="warning" %}
The prioritization in the list follows a standard: requests with 'NEW' status and the shortest remaining SLA time are shown first, followed by those that had interactions with Mss/Company, and finally, the rest are listed by ID in descending order.
{% endhint %}

A color palette indicates special situations:

* Red: SLA exceeded.
* Yellow: SLA 1 hour about to be exceeded.
* Green: Incident with a new unread interaction.

<figure><img src="/files/hvyvqd1Oo57lTeb0vQFS" alt=""><figcaption><p>Request Table Order</p></figcaption></figure>

***

#### **Important columns into dashboard include:**

* SLA: The time agreed with the client, which stops counting when the incident is addressed.
* Criticality: Organized from LOW to CRITICAL, according to the parent correlation rule.
* Status: Indicates the stage of resolution, varying from active, pending, under treatment, and closed.
* Rate: The average user feedback, based on various parameters.

***

#### Available actions into dashbord:

* Escalate Request: Increases the request's priority in the list, reducing the SLA.
* [<mark style="color:green;">Messages</mark>](/response/incidents/messages.md): Allows analysts to follow and participate in the resolution process, sending messages and files, and includes system messages about changes in the request.
* [<mark style="color:green;">Rate</mark>](/response/incidents/rate.md): Displays feedback for each analyst involved.

***

### Request Details

Presents important information, links, message history, and activities related to the resquest, allowing individual or mass changes in various parameters.

<figure><img src="/files/XFvW6T42nt1d7lPAZb6W" alt="" width="305"><figcaption><p>Request Details</p></figcaption></figure>

{% content-ref url="/pages/m0oNicfjqfB5lp8ULeIy" %}
[Messages](/response/incidents/messages.md)
{% endcontent-ref %}

{% content-ref url="/pages/OL60S6SBanae7JG2O7Wy" %}
[History](/response/incidents/history.md)
{% endcontent-ref %}

***


---

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

```
GET https://docs.inopli.com/response/requests.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.