# Opening a ticket
A requester formulating a need can use several tools:
* Filling an online [form](/documentation/modules/administration/forms.md), the requester being known to GLPI or not;
* Asking a delegate in the group to open the ticket (see [Administer groups](/documentation/modules/administration/groups.md)).
* In **simplified interface**, this is put into evidence by an option allowing to indicate if the ticket concerns the requesting user or another user.
* **In standard interface**, simply enter the user's name in the **`Actor`** > **`Requester`** field.
* Contacting an operator directly or by phone, the operator will open the ticket;
* Sending the demand by mail, it can be converted into a ticket directly by the receiver.
## Opening a ticket in GLPI
A ticket can be opened:
* Through the anonymous ticket opening interface, this interface being accessible by all non-authenticated users if GLPI general configuration allows it
* Through the graphical interface:
* simplified interface: lightweight form for an authenticated end-user;
* standard interface: full-fledged form;
* Using a [form](/documentation/modules/administration/forms.md#public-access) accessible to anyone with the link to it.
### Anonymous ticket opening interface for non-authenticated users
This interface can be accessed at URL [http://front/helpdesk.html](http://front/helpdesk.md); it allows users having no GLPI account to send an incident signaling form to the help desk. Once filled and submitted, a mail will confirm the ticket opening.
The form can be customized by modifying directly file `helpdesk.html`.
By default, ticket is created in root entity.
### Opening a ticket in graphical interface
Since GLPI11, [forms ](/documentation/modules/administration/forms.md)are native. The [service catalog](/documentation/modules/assistance/service-catalog.md) allows you to make forms available to users in order to simplify ticket creation.
If templates are used (see [Using templates](/documentation/modules/overview/templates.md#ticket-templates)), some fields can be made mandatory, predefined or masked when opening the ticket (content, title and/or category). If a mandatory field is missing, the ticket will not be opened.
The different fields are described in [Manage tickets](/documentation/modules/assistance/tickets/ticketmanagement.md).
It is possible to attach to the ticket one or more documents in one operation.
When activating option **Use rich text for assistance** in general configuration, the *Description* field of the ticket will be able to be formatted as HTML. Moreover, an added zone will be available for images drag and drop, for example screenshots. A tag will then be added automatically to the description in order to formalize the content of the demand.
#### Forms
Example of service catalog
Forms simplify the ticket creation process for users. Using a service catalog, they guide users to the right form so that they can answer a series of predefined questions, enabling them to create their request independently.
It is possible to filter the visibility of a form for users, profiles, and groups in order to restrict access to your forms. It is also possible to make them visible to users who are not authenticated in GLPI.
Configure Forms
#### Simplified interface
This interface allows an authenticated user to open quickly a ticket, for the user or by [delegation ](/documentation/tabs/common_fields/group.md)for another person.
Ticket opening form can be accompanied by a message inviting user to check personal information (location, phone number) in order to be easily contacted by technicians.
Specific fields:
* **Inform me about he actions take**: Appears if email followup are configured, see [notification management](#configure_notifications). If set to `Yes`, the requester will be kept informed by mail of the different processing of the ticket. The field *Mail* contains the email address to which notifications will be sent. If several email addresses are defined, GLPI will select the default email defined in user's preferences. It is possible to select another email address or to enter an address if user's profile does not mention an email;
* **Associated elements**: Allows to associate an item of the inventory with the ticket. The content of the list depends upon parameters defined in user's profile (see [Administer user profile](/documentation/modules/administration/profiles/profiles.md)).
* **Watchers**: Allows to add a watcher and to define notification parameters.
{% hint style="success" %}
Users can add new email addresses to the profile, see [Manager preferences](/documentation/readme-1-1/preferences.md).
{% endhint %}
{% hint style="warning" %}
If images or documents are added to the ticket, it is important to add them **after** having filled **all** mandatory fields marked with a red star, this because the reloading of the ticket opening form triggered by a missing mandatory field suppress attached images or documents.
{% endhint %}
A message confirms the creation of the ticket which is then accessible by clicking on the ticket number highlighted in green.
#### Standard interface
To create a ticket, go to menu **`Assistance` > `Ticket`** then click add button with the **`+ Add`** icon.
When adding a new image from tab *Documents* of the ticket, the generated tag can also be used to insert image in ticket's description.
A message confirms the creation of the ticket which is then accessible by clicking on the ticket number.
A [validation](/documentation/modules/assistance/tabs/approvals.md) demand can also be done at ticket opening by indicating the desired validating user.
{% hint style="info" %}
When filling assigned requester, technician or group, information is displayed about the number of tickets this person or this group has opened or is in charge of. Similarly, when selecting an item, a simplified view of current tickets for this item is displayed.
{% endhint %}
## Open a ticket by mail
Opening a ticket by mail is done by sending a mail to an email address defined in the collector.
On reception of the mail, a ticket will be opened automatically:
* Message object will become ticket title;
* Body will become ticket description;
* Cc: will become observers if emails are known to GLPI;
* Attachments will become attached documents of the ticket.
Configure my receiver
## Open a ticket automatically
This mechanism is activated through recurrent tickets.
Configure recurrent ticket
---
# 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://help.glpi-project.org/documentation/modules/assistance/tickets/ticketopening.md?ask=
```
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.