Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
A user query is one of the core components used in the communication between the end-user and the service desk department. User queries come to the fore when the end-user is not able to classify the type of their issue, whether it is an incident or a service request.
Create a user query
You can create a user query in two ways:
- via the Self-Service Portal
- via the agent interface
Via the Self-Service Portal
To create a user query, complete these steps:
- Navigate to your Self-Service Portal and click Ask a question.
- Fill in the fields.
- Click Save.
User query form fields
Field | Mandatory | Description |
---|---|---|
Number | Y | User query number. This field has the INCXXXXXXX format and is populated automatically. |
Contact Type | Y | Define the source from which the request is received. Available options:
|
Caller | Y | Specify the originator of the user query. |
Urgency | Y | Specify the urgency of the issue. Typically, it is evaluated based on the time remaining until the issue impacts the business. Available options:
|
Subject | Y | Type a brief description of the issue. |
Description | N | Type a detailed description of the issue. |
After the form is saved, a record is created in the Inquiries (itsm_inquiries) table. At this time, the newly created user query is waiting to be processed by a service desk agent.
viaVia the agent interface
To create a user query, complete these steps:
- Navigate to User Queries → All User Queries.
- Click New to add a record for a new user queryand fill in the fields.
- Click Save or Save and Exit to apply the changes.
User query form fields
Field | Mandatory | Description | ||
---|---|---|---|---|
Number | Y | User query number. This field has the INCXXXXXXX format and is populated automatically. | ||
Contact Type | Y | Define the source from which the request is received. Available options:
| ||
Caller | Y | Specify the originator of the user query. | ||
Company | N | Specify the company to which the user query is related. | ||
Related Tickets | N | Specify the related configuration items affected by the user query.
| ||
Subject | Y | Type a brief description of the issue. | ||
Description | N | Type a detailed description of the issue. | ||
State | N | This field displays the 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. Available options:
|
User query states
Anchor | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
The A newly created inquiry user query is in assigned the Unprocessed state. If Once it is classified by a service - desk agent, its the state changes to Processed. Another possible state is Dropped. Erroneous or spambot inquiries should be dropped, which is typically assigned to erroneous or spambot user queries. |
Once an inquiry a user query is created, it should be processed by ITSM agents. The inquiry process includes processing of a user query involves its classification as one of the specific issue types.
The following issue types are available:
- Incident
- Problem
- Change Request
- Service Request.
To classify a inquiryuser query, an agent should complete the these steps below:
- Navigate to Inquir ies User Queries → Unprocessed.
- Open the necessary inquiryrequired user query.
- Click on the UI action named by the needed issue type.
Image Removed
into Incident
- Select the type by clicking the respective button in the top-right corner of the form.
Image Added
Convert a user query into an incident
A user query can be converted into an incident after it is analyzedInquiries can be converted to incidents after analysis. For more information about this, please refer to the Inquiry to Incident conversionsee the User Query to Incident transformation article.
into ProblemConvert a user query into a problem
A user query can be converted into a problem after it is analyzed. To do so, follow these steps:
- Navigate to Inquir ies User Queries → Unprocessed.
- Open the necessary inquiryrequired user query.
- Click Problem at in the top-right corner of the form.
- Fill in the mandatory fields in the problem form:
- Service
- Impact
- Assignment groupGroup
- Assigned user.User
- Click Save or Save and Exit to apply the changes.
As a result:
- Original inquiry The original user query state is changed to Processed.
- A new Problem record is created in the Registered state.
into Change Request
Convert a user query into a change request
A user query can be converted into An inquiry can be converted to a change request after analysisit is analyzed. To do this, an agent should complete the steps below:
- Navigate to Inquir ies User Queries → Unprocessed.
- Open the necessary inquiryrequired user query.
- Click Change Request at the in the top-right corner of the form.
- Select a previously created change template from the dictionary. This field is mandatory.
- Click Create to finish the conversion or Skip to cancel.
- Fill in the mandatory fields in the request form:
- Service
- Impact
- Assignment group Group
- Assigned user.User
- Click Save or Save and Exit to apply the changes.
As a result:
- Original inquiry state The original user query state is changed to Processed.
- A new Change Request record is created in the Registered state.
Convert a user query into a service request
- Navigate to Inquir ies User Queries → Unprocessed.
- Open the necessary inquiryrequired user query.
- Click Service Request at in the top-right corner of the form.
- Select the a previously created request modeltemplate from the dictionary.
- Leave the field empty if this request is classified as non-typical.
- Click Create.
- Fill in the mandatory fields in the request form:
- Service
- Impact
- Assignment groupGroup
- Assigned User
- Click Save or Save and Exit to apply the changesClick Create to finish the conversion.
As a result:
- Original inquiry state The original user query state is changed to Processed.
- A new Service Request record is created in the Registered state.
Table of Contents | ||||
---|---|---|---|---|
|
...