> 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/system-settings/configuring-the-mss/request-categories.md).

# Request Categories

Request Profiles screen is a dedicated interface for <mark style="color:green;">creating and editing request profiles.</mark> These profiles can be filtered, activated, deactivated, deleted, and linked to companies, offering 100% <mark style="color:green;">customization to meet client-specific needs.</mark> It enables the mapping of the most frequent requests and the definition of the information flow required from the user. This approach streamlines <mark style="color:green;">problem resolution</mark>, making it <mark style="color:green;">faster</mark> and <mark style="color:green;">more efficient</mark>. Additionally, the system allows for configuring the responses to <mark style="color:green;">assign a level of criticality to each request</mark>.

<figure><img src="/files/llMDJnE0O0Dnoje1hmag" alt=""><figcaption><p>List of Request Profiles</p></figcaption></figure>

***

### Creating a Request Profile

When creating a profile, <mark style="color:green;">it's essential to provide a name and description.</mark>&#x20;

The flowchart outlines the <mark style="color:green;">user's journey when initiating a request</mark>, aiding in retrieving relevant information. Certain stages allow defining the criticality of the ensuing request.

Adding a new stage to the flow is as simple as clicking the '+' sign. In every stage the user's response is mandatory.

#### Types of Stages

{% tabs %}
{% tab title="Title" %}
This is the first stage of the flow, where a standard question is posed. The user's text response forms the <mark style="color:green;">title of the request</mark>.

<figure><img src="/files/OzBN097QkMEEkD0dCDs8" alt=""><figcaption><p>Title Stage</p></figcaption></figure>
{% endtab %}

{% tab title="Question" %}
This second standard stage, where <mark style="color:green;">you can set the main question</mark> to be answered for different 'Response' stage types.

<figure><img src="/files/6jCwfILKHAbGocKrR6rl" alt=""><figcaption><p>Adding Question Stage</p></figcaption></figure>
{% endtab %}

{% tab title="Response" %}
At this stage, <mark style="color:green;">the criticality of the request is determined.</mark> It presents the user with fixed response options to the 'Question' stage, typically in a select format.

<figure><img src="/files/tUPmkEvmXdTiZOqKJBiS" alt=""><figcaption><p>Adding Response Stage</p></figcaption></figure>
{% endtab %}

{% tab title="Text" %}
A stage for <mark style="color:green;">open-ended questions.</mark>

<figure><img src="/files/DsUILm5kkUPcVlT5FUTF" alt=""><figcaption><p>Adding open-ended questions</p></figcaption></figure>
{% endtab %}
{% endtabs %}

To complete this flow, connect all stages to form a continuous sequence leading to the 'Create Request' stage.

Once the flow is finalized, it can be linked to companies that will use it as their request flow.

{% hint style="warning" %}
Remember: Each company can only be linked to one request profile.
{% endhint %}

***