Desk departments
From 1.20.23 a desk can be split into desk departments, such as IT, HR and Facilities. A desk department holds teams and the content those teams work with: macros, canned responses, checklists, request types, workflows and automations. Recurring tickets follow their team.
“Desk department” is not the same as a requester’s department from the directory, which VIP lists, contact cards and report filters use. That stays as it was.
How it fits together
Section titled “How it fits together”- A team is in exactly one desk department.
- An agent is in every desk department one of their teams is in. An agent on an IT team and an HR team works with both.
- Each item is in one desk department, or in All departments. All departments items are shared desk-wide. Only admins can put an item in All departments or take it out.
- Queues don’t change. Which tickets an agent sees still follows their teams and desk role.
After upgrading
Section titled “After upgrading”Every desk gets one desk department, General, holding all its teams and all its existing content. Nobody sees anything different until an admin creates more desk departments and moves teams and content into them.
What agents see
Section titled “What agents see”Agents see and use only their own desk departments’ macros, canned responses, checklists, request types and workflows, plus anything in All departments. That applies everywhere: the reply box, the macro menu, adding a checklist, Start a workflow, New ticket, Claude in the desk and the Claude connector. Anyone who can see every team’s tickets (Admins, and Managers by default) sees every desk department’s content, so they can work any ticket they open.
A request type is offered only when both it and its workflow are in the agent’s desk departments or All departments. Get help, the customer portal, chat and email are never filtered: requesters see what they always did.
Automations
Section titled “Automations”A ticket runs the automations of its team’s desk department, plus those in All departments. A ticket with no team counts as the default desk department’s. If a rule moves the ticket to a team in another desk department, the rest of the run uses that department’s rules.
Managing desk departments
Section titled “Managing desk departments”Desk settings → Teams → Desk departments (admins):
- Create, rename or delete a desk department. One with teams in it can’t be deleted, and if content is left you’re asked where it goes. The default desk department can’t be deleted.
- Move a team. The desk first lists what changes: rules elsewhere that name the team, request types, checklists and workflows that route to it, recurring tickets, and agents who would lose the old department’s content. Confirm with Move team. The team’s own macros and canned responses go with it.
A move that would leave something pointing across desk departments is refused with a list, for example a macro an automation elsewhere still sends, or a workflow whose request type would end up in another department. Move or change those first.
Who manages content
Section titled “Who manages content”- Admins manage everything.
- Manage a desk department (a new capability, on for Managers by default) lets someone manage every kind of content in the desk departments of their own teams.
- A feature’s own capability, such as Automations, works only in the holder’s own teams’ desk departments.
- Items in All departments are read-only to everyone but admins.
Every editor has a Desk department field, and lists can be filtered by desk department when you see more than one.
In the audit log
Section titled “In the audit log”| Action | Shown as |
|---|---|
helpdesk.desk_department.created / .renamed / .deleted |
Created / Renamed / Deleted a desk department |
helpdesk.desk_department.team_moved |
Moved a team to another desk department (with what changed) |
helpdesk.desk_department.item_moved |
Moved an item to another desk department |
