> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/assistance/tickets/ticketadvanced.md).

# To go further

## Tickets categories

Ticket categories are used to classify and organize tickets according to their nature or type of request. They are essential for structuring support and facilitating processing, assignment, and statistics.

<a href="/pages/IKquAB5RiZlTGNnv2Jy5" class="button secondary">Go to Categories</a>

## Tickets templates

Using ticket templates, it is possible to customize ticket creation form by masking, pre-defining or making mandatory some fields.

<a href="/pages/urokXpwsBqN6OGeviODc#ticket-templates" class="button secondary">Go to Ticket templates</a>

## Receiver

External tools can interact with assistance module using mail collectors.

Email is used to create tickets and add follow-up to existing tickets. A GLPI internal task will connect to a mailbox and fetch messages.

{% hint style="info" %}
The solution or closure of a ticket are not available via collectors.
{% endhint %}

A mail message will go through the following steps:

* Mail box;
* Collector, configured using [Configure collectors](/documentation/modules/configuration/collectors.md);
* Rules, see [Assigned a ticked opened by mail to an entity](#collectors_rules)
* Business rules, see [Business rules for tickets](/documentation/modules/administration/rules/ticketbusinessrules.md)
* Ticket is created

An answer to a mail coming from GLPI will go through the following steps:

* Mail box;
* Collector ;
* Creation of a follow-up for concerned ticket.

<a href="/pages/lxkRMwy2CAF1ZgSQ72Fa" class="button secondary">Configure Receiver</a>

## Attached costs

Deduct ticket-related costs in order to stay within the allocated budget

<a href="/pages/IIvpZrpiKeCvczBmcMYP#costs" class="button secondary">Manage costs</a>

## Links between tickets

It is possible to define links between tickets or to mark tickets as duplicates.

<a href="/pages/IIvpZrpiKeCvczBmcMYP#linked-assistance-objects" class="button secondary">Links between tickets</a>

## Processing time

Incidents resolution delays or [SLA ](#user-content-fn-1)[^1]can be configured.

<a href="/pages/BLQh9bKO25KkRp6Kqagx" class="button secondary">Configure your SLAs</a>

## Business rules

Business rules can be defined to modify and assign tickets.

<a href="/pages/shxqGkppzMy5MZzovIq9" class="button secondary">Configure Business rules for tickets</a>

## Administrative closure

Administrative closure moves the status of a ticket from *Solved* to *Closed*.

ITIL best practices recommends a validation of the solution by the ticket requester, who validates that the answer provided by the technician corresponds to the demand. However, if the requester does not fulfill this validation, it is possible to parameterize an administrative closure after a delay which can be configured at entity level (see [Assistance tab](/documentation/modules/administration/entities.md)). If this delay is set to zero, the ticket is automatically closed.

## Satisfaction

You can send out satisfaction surveys to measure your users' satisfaction levels. These surveys can then be analysed using statistics.

<a href="/pages/FVcD2wNJIlEdBOzJBB2Z" class="button secondary">Configure Satisfaction survey</a>

[^1]: Service Level Agreement


---

# 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://help.glpi-project.org/documentation/modules/assistance/tickets/ticketadvanced.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.