A workspace is one service desk: IT, HR, Finance, Facilities, Customer Service, or whatever your organization calls them. Each workspace has its own ticket queue and ticket keys, its own agents and groups, service levels, routing rules, statuses and categories, and its own space in the knowledge base.
Open Settings → Workspaces and groups. A new organization lands here first, with five suggestions to tick. Later, New workspace adds one.
Each workspace needs:
IT or HR. Tickets in the workspace are numbered IT-1, IT-2 and so on. The prefix cannot be changed later, so choose it with care.Workspaces are archived, never deleted, so ticket keys keep meaning something.
Open a workspace to manage it.
Every workspace starts with the statuses New, Open, Waiting on requester, Resolved and Closed. Rename them, add your own under the same five kinds, and choose which is the default for new tickets. Categories are a tree you define (for IT perhaps Accounts, Network, Devices) that agents pick on a ticket and routing rules can match.
Under SLA policy set the targets per priority: how fast a ticket gets its first reply and how fast it is resolved. The policy counts business hours by default, which you define right above it (weekdays and hours, time zone, holidays); switch it to around the clock for a 24/7 team. A ticket that is waiting on the requester pauses its clock.
Tickets that are at risk or over their target show a badge in the inbox, and the SLA at risk view lists them nearest due first. The policy is off until you switch it on.
Routing rules send new tickets to the right group, and optionally straight to a person. A rule has conditions (the ticket's type, priority, category, source, subject keywords, the requester's department and more), a group to assign, and an assignment mode: none, round robin or load balanced among the group's members. Rules are tried top to bottom; the first match wins. A rule tester lets you try a sample ticket against the rules before anything real arrives.
Settings → Canned responses holds the replies your agents send often, per workspace or shared across all of them. A canned response can also be a macro that sets the status, priority, assignee or group when it is used. Agents insert one by typing / at the start of a reply.
Getting startedUpdated Oct 12, 2026
Getting startedUpdated Oct 12, 2026
Getting startedUpdated Oct 12, 2026
Getting startedUpdated Oct 12, 2026
Getting startedUpdated Oct 12, 2026