The user query is one of the core components used in the communication between the end-user and the service desk department. User queries are created when the end-user is unable to classify the type of their issue, whether it is an incident or a service request.
There are three ways to create a user query:
This procedure is available for all end-users. |
To create a user query, complete these steps:
User query form fields
The user query number has the INQXXXXXXX format and is populated automatically.
Field | Mandatory | Description |
---|---|---|
Caller | Y | The originator of the user query. This field is populated automatically and is hidden on the Self-Service Portal form. |
Contact type | Y | The source from which the request is received. This field is populated automatically and is hidden on the Self-Service Portal form. Available options:
|
Subject | Y | Add a brief description of the issue. |
Description | N | Add a detailed description of the issue. |
Urgency | Y | Specify the urgency of the issue. Typically, it is evaluated based on the time remaining until the issue impacts the business. For more information, see Priority Management. |
If the urgency is set to Very high, the caller is asked to confirm information by phone. The displayed phone number can be specified in the itsm.notification.contact.phone system property.
You can also attach files via the attachment window. To add files, drag them to the attachment window, or click Upload from computer and select them on your device.
After saving the form, you get a message that your query has been received:
The message states a period of time required to process the query. The system administrator can change the response time value by editing translations of the source message /record/source_message/168672734718023981. The message also displays the email address of the caller as well as the service desk phone number that can be specified in the itsm.notification.contact.phone system property.
After the form is saved, a record is created in the User Queries (itsm_inquiries) table and the new user query is processed by a support agent. You can track progress of your query on the My Tickets page of the Cabinet.
Role required: ITSM_agent. |
To create a user query, complete these steps:
User query form fields
The user query number has the INQXXXXXXX format and is populated automatically.
Field | Mandatory | Description | |
---|---|---|---|
Caller | Y | Specify the originator of the user query. | |
Contact type | Y | Define the source from which the request is received. Available options:
| |
Related ticket | N | Specify the related configuration items affected by the user query.
| |
Subject | Y | Add a brief description of the issue. | |
Description | N | Add a detailed description of the issue. | |
State | N | Specify the current work state. Available states:
| |
Urgency | Y | Specify the urgency of the issue. Typically, it is evaluated based on the time remaining until the issue impacts the business. For more information, see Priority Management. |
A newly created user query is assigned the Unprocessed state. Once it is classified by a service desk agent, the state changes to Processed. Another possible state is Dropped, which is typically assigned to erroneous or spambot user queries.
Once a user query is created, it should be processed by ITSM agents. The processing of a user query involves its classification as one of the specific record types.
Role required: ITSM_agent. |
In SimpleOne, a record of another type can be created from a user query after it is analyzed:
To do so, complete the following steps:
After a user query is analyzed, an incident can be created from it. For more information, see the Create Incidents article.
After a user query is analyzed, a problem can be created from it. To do so, complete the steps below:
As a result:
After a user query is analyzed, a change request can be created from it. To do so, complete the steps below:
As a result:
After a user query is analyzed, a service request can be created from it. To do so, complete the steps below:
Specify the required service request model in the corresponding field.
Leave the field empty if this request is classified as non-typical. Click Continue to open the create new request form.
Starting from ITSM Application version 1.7.1, the request models from the REM service catalog are used. However, you can still use request templates as in previous versions. To learn how to do this, see the instruction below. |
Click Continue.
A widget appears on the user query form that contains the request model name, REM fields and the Copy caller from the user query checkbox.
The checkbox is selected by default. Clear the checkbox to make the current user the service request Caller. |
To use templates as request models, set the itsm.service_request.use_rem_request_catalog system property to false. To find it, navigate to System Properties → All Properties. Complete the following steps to create a service request from a user query:
|
As a result: