---
title: Desktop of the Service Desk
slug: pink/desktop-of-the-service-desk
description: Learn how to effectively use the Ticket Management interface on your Service Desk Desktop. This comprehensive document provides step-by-step instructions on accessing the interface, utilizing its main features such as the powerful search bar, ticket listi
docTags: 
createdAt: 2021-10-27T20:37:35.000Z
---

The **Desktop of the Service Desk** is a <font color="#3b9f0f">**place where tickets**</font> that have been opened for activities linked to your group <font color="#3b9f0f">**are available**</font>, and <font color="#3b9f0f">**where you can view multiple information about a ticket**</font>.

## Before getting started

To have access to the features of the **Ticket Management** interface, it is essential:

- [x] To have workgroup permissions; and&#x20;
- [x] Also access to service catalogs;
- [x] In addition, to having at least one ticket in the attendance queue.&#x20;

## Procedure

Access the menu `Processes > Ticket Management > Ticket`.

## Interface

The home screen of **Ticket Management** is the analysts of attendance interface with requests and/or incidents that are in process or awaiting attendance. This interface consists of Search Features, Ticket Listing, and Main Menu.

### Search

It is possible to use the search bar to make it easier to search for a specific ticket - by entering the number - or a set of tickets with similar characteristics - using several attributes - such as:

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/XJwPxndv7AHjM_TK5ub4b_image.png)

<font color="#3b9f0f">**1\:** </font>****<font color="#3b9f0f">**Number of the ticket**</font>;

<font color="#3b9f0f">**2\:** </font>****<font color="#3b9f0f">**Requester** </font>of ticket (Who requested);

<font color="#3b9f0f">**3\:** </font>****<font color="#3b9f0f">**Type** </font>**–&#x20;**&#x6F;f service (Request, Incident, or Procedure);

<font color="#3b9f0f">**4\:** </font>****<font color="#3b9f0f">**Status** </font>of ticket (status/expressions registered in the flow);

<font color="#3b9f0f">**5\:** </font>****<font color="#3b9f0f">**Contract** </font>to which the ticket is linked;

<font color="#3b9f0f">**6\:** </font>****<font color="#3b9f0f">**Executor group**</font> (Current set of people who can attend the service);

****<font color="#3b9f0f">**7\: Current task**</font> (User task in the flow);

****<font color="#3b9f0f">**8\: Assignment** </font>of ticket (Current person who's attending the service);

****<font color="#3b9f0f">**9\: SLA status**</font>**:&#x20;**&#x4E;ormal, Expired, Waiting for approval and others;

****<font color="#3b9f0f">**10\: Order by**</font>**:&#x20;**&#x54;icket No, Date/time of creation, Activity, Service, Assignment,&#x20;Priority, Status, Date/time of limit, and Date of the last update;

****<font color="#3b9f0f">**11\: View**</font>**:&#x20;**&#x41;ll tickets or just the ones I can track or execute;

****<font color="#3b9f0f">**12\: Unit** </font>**–&#x20;**&#x6F;f Requester;

****<font color="#3b9f0f">**13\: Exhibition**</font>**:&#x20;**&#x41;ll, Chat – just opened by this channel - and critics – only critical incidents;

****<font color="#3b9f0f">**14\: Option to show related tickets**</font> **–&#x20;**&#x69;n the attendance list;

To apply a search based on the filters you set, use the "**Search**" button. After making the search, the icon will change to identify the search status, such as:

::Image[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/7XxrcJJuWEafT8vYyacjb_image.png" size="10" width="37" height="31" caption=" Icon without Active Search" position="center" showCaption="true"}

::Image[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/nTPvMCfGz9FPuZWM09axY_image.png" size="10" width="37" height="33" caption="Icon with Active Search" position="center" showCaption="true"}

It is possible to clean all filters selected and return to default format by clicking on "**Clear**".

### Tickets List

In the list we can see the tickets available in an attendance queue - based on group permissions - where we find the following columns:

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/pD0FrS1CDAWK7TKycGkxV_image.png)

<font color="#3b9f0f">**1\:** </font>****<font color="#3b9f0f">**Selecting Ticket(s)** </font>**–&#x20;**&#x74;o delegate or suspend/reactivate them;

<font color="#3b9f0f">**2\:** </font>****<font color="#3b9f0f">**Ticket** </font>number;

<font color="#3b9f0f">**3\:** </font>****<font color="#3b9f0f">**Priority** </font>**–&#x20;**&#x6F;f attendance (SLA);

<font color="#3b9f0f">**4\:** </font>****<font color="#3b9f0f">**Service**</font>;

<font color="#3b9f0f">**5\:** </font>****<font color="#3b9f0f">**Request** </font>(Request/Incident);

<font color="#3b9f0f">**6\:** </font>****<font color="#3b9f0f">**Requester**</font>;

<font color="#3b9f0f">**7\:** </font>****<font color="#3b9f0f">**Contract**</font>;

****<font color="#3b9f0f">**8\:** </font><font color="#3b9f0f">**Created by**</font> (Who created the ticket);

****<font color="#3b9f0f">**9\:** </font><font color="#3b9f0f">**Creation date**</font> of the ticket;

<font color="#3b9f0f">**10\:** </font>****<font color="#3b9f0f">**Task** </font>**–&#x20;**&#x6F;f flow;

****<font color="#3b9f0f">**11\:** </font><font color="#3b9f0f">**Current group**</font> **–&#x20;**&#x6F;f attendance;

<font color="#3b9f0f">**12\:** </font>****<font color="#3b9f0f">**Unit**</font>;

<font color="#3b9f0f">**13\:** </font>****<font color="#3b9f0f">**Assignment** </font>**–&#x20;**&#x74;he responsible for the attendance;

<font color="#3b9f0f">**14\:** </font>****<font color="#3b9f0f">**Task status**</font> **–&#x20;**&#x69;n the flow;

<font color="#3b9f0f">**15\:** </font>****<font color="#3b9f0f">**SLA** </font>**–&#x20;**&#x6D;aximum time of attendance;

<font color="#3b9f0f">**16\:** </font>****<font color="#3b9f0f">**Deadline** </font>**–&#x20;**&#x66;or attendance;

<font color="#3b9f0f">**17\:** </font>****<font color="#3b9f0f">**SLA Status**</font>;

Located in the upper right side, we can see a series of icons representing, respectively:

::Image[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/uOMqXgFFOg25r_9Ux1N0L_image.png" size="66" width="362" height="39" position="center" showCaption="false"}

### Pagination:

****<font color="#3b9f0f">**1\: Back** </font>to the first page;

****<font color="#3b9f0f">**2\: Back** </font>one page;

****<font color="#3b9f0f">**3\: Number**</font> ticket identifier number of the start page;

****<font color="#3b9f0f">**4\: Number** </font>ticket identifier number of end page;

****<font color="#3b9f0f">**5\: Number** </font>total of tickets;

****<font color="#3b9f0f">**6\: Advance** </font>one page;

****<font color="#3b9f0f">**7\: Advance**</font> to the last page;

### Delegation:

****<font color="#3b9f0f">**8\: Delegate**</font> **–&#x20;**&#x74;icket(s) to a group;

:::hint{type="warning"}
⚠️ <u>**Attention**</u>**!&#x20;**

The "**Automatic Update**" button will come by default not enabled in the <font color="#3b9f0f">**CITSmart** </font>**Parameters**, to enable it, it is necessary to change **parameter 418** to "**YES**". This way, the button will be available on the ticket screen to automatically refresh the page every 25 seconds.
:::

### Page Updating:

****<font color="#3b9f0f">**9\: Automatic Update** </font>(25 and 25 seconds);

****<font color="#3b9f0f">**10\: Update List**</font> **–&#x20;**&#x74;o refresh manually the page;

### Reports

****<font color="#3b9f0f">**11\: Reports**;</font>

<font color="#3b9f0f">**12\: (Other) Options**</font>;

- **a: Suspension/Reactivation** **–&#x20;**&#x6F;f ticket;
- **b: Change columns** (to custom the list);

### Ticket options:

Clicking on a ticket in your attendance queue will present you the actions available:

::Image[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/JIiIM4EiBH7fmXg8bQ48u_image.png" size="60" width="362" height="350" position="center" showCaption="false"}

### Main options:

****<font color="#3b9f0f">**1\: Open**;</font>

<font color="#3b9f0f">**2\: View**;</font>

<font color="#3b9f0f">**3\: Description**</font> **–&#x20;**&#x76;iew the description without opening it;

****<font color="#3b9f0f">**4\: Reports**;</font>

<font color="#3b9f0f">**5\: View Flow** </font>**–&#x20;**&#x6F;f service;

****<font color="#3b9f0f">**6\: More options** </font>(present the items below);

### Secondary options:

****<font color="#3b9f0f">**7\: Delegate**;</font>

<font color="#3b9f0f">**8\: Suspend**;</font>

<font color="#3b9f0f">**9\: Change SLA**;</font>

<font color="#3b9f0f">**10\: Reclassify**;</font>

<font color="#3b9f0f">**11\: Create Sub-ticket**;</font>

<font color="#3b9f0f">**12\: Create related ticket**;</font>

<font color="#3b9f0f">**13\: Schedule activity**;</font>

<font color="#3b9f0f">**14\: Print**;</font>

:::hint{type="warning"}
⚠️ <u>**Attention**</u>**!**

These options are based on the permissions given to your profile, so you may not be able to use all of the options above.
:::

### Main Menu

### Global Vision:

- **List** **–&#x20;**&#x50;resents a list with the tickets in your queue;
- **Team management** **–&#x20;**&#x54;icket management in a Kanban view;
- **SLA status** **–&#x20;**&#x41; synthetic view categorized by SLA status;
- **Flow status** **–&#x20;**&#x43;urrent status (expressions registered for a flow) of tickets assigned to a group;

### Map View:

- **Map** **–&#x20;**&#x41;llows to view tickets registered for attendance in a unit;

### View by Search:

- **Filters** **–&#x20;**&#x57;hen selecting a filter (expressions registered for a flow) will present the tickets according to the selected item;

### Other options

- **Schedule:&#x20;**&#x41;llows to view events related to Ticket, Change, Problem and Release;
- **Summary:&#x20;**&#x41; quantitative report of tickets;
- **Advanced Search:&#x20;**&#x49;t allows you to perform more detailed ticket searches as well as the information generated in your attendance;
- **Audit:&#x20;**&#x49;t presents all changes that occur to a ticket whether automatic or manual;

