Docs

Admin / Organization

Sub-departments

Split one department's work into smaller queues that share its knowledge, tools, and agent channel, but keep their own tickets, members, and escalation rules

A sub-department is a specialist queue inside a department. It has its own tickets, members, escalation rules, and service levels, but it answers from the parent department's knowledge and runbooks and works in the parent's Slack agent channel.

Use sub-departments to split one team's work without a second copy of the team's setup. For example, split IT into IT / Networking and IT / Access.

When to use a sub-department

  • Tiers within a team. IT stays the front door. IT / Tier 2 or IT / Security takes the tickets that the first line escalates.
  • Specialist groups. IT / Networking and IT / Access get their own tickets and assignees, while Risotto still answers from IT's runbooks and knowledge.
  • The same name in different teams. IT / Onboarding and HR / Onboarding can both exist. Each one sits under its own parent.

If a team needs its own knowledge, tools, or agent channel, create a top-level department instead. See Add a new department.

Prerequisites

  • The Admin or Manager organization role. Only these roles can create departments. See Permissions.
  • An existing top-level department to use as the parent.

Create a sub-department

  1. Open the Create Department dialog

    Open the parent department's settings page and click New sub-department in its Sub-departments section. The dialog opens with Parent department already set.

    You can also hover the parent under Departments in the Settings sidebar and click the + that appears next to its name. Or click the + next to Departments and pick the parent in the Parent department list, which lists only top-level departments.

  2. Name and describe it

    Enter a Name and a Description. Both are required.

  3. Create it

    Click Create. Risotto opens the sub-department's General page.

  4. Check the ticket prefix

    Risotto picks the sub-department's part of the ticket prefix from its name, for example NE for Networking. The Ticket Prefix field shows the parent's prefix locked in front of it, such as IT-. To change the sub-department's part, type a new one, for example NET, and click Save. Its tickets get IDs such as IT-NET-12.

    The Agent Channel shows the parent's channel, locked, with "Inherited from" and the parent's name.

  5. Add members

    Open Members and click Add a member. Everyone in the parent department already has access, so add only the people who work this queue alone. See Members and roles.

  6. Check its service levels

    Open Escalations, Auto Resolve, and, when ticket SLAs are on for your organization, SLAs. A new sub-department starts with a copy of the parent's escalation contact, custom escalation message, review switches, AI beta opt-in, ticket sync settings, SLA targets, and auto-resolve settings. After that, a change on either department does not affect the other.

  7. Route tickets to it

    Open the parent department's Escalations page and add a routing rule. As the rule's target, pick Hand off to a sub-department, then pick the sub-department. Click Save. See How tickets reach a sub-department.

How tickets reach a sub-department

Requestors never pick a sub-department. A ticket always arrives in the parent department first and is handed down from there.

Escalation rule

On the parent's Escalations page, a routing rule can hand tickets off to a sub-department. The default below the rules can too: set it to Assign to, pick A sub-department, and pick the sub-department. Hand off to a sub-department and A sub-department show only when the department has sub-departments.

When a ticket in the parent escalates and matches the rule, Risotto moves the ticket to the sub-department and escalates it again there, under the sub-department's own rules. Those rules pick the person to tag or assign. A sub-department has no sub-departments, so its own rules can route only to people.

Manual move

An agent can move a ticket into a sub-department by hand:

  • Dashboard. Change the department on the ticket. Sub-departments are listed with their parent, for example IT / Networking.
  • Slack. Open the ticket's overflow menu in the agent channel and choose Move to another department. The Move department dialog lists the current department's sub-departments first.

Moving a ticket into a sub-department escalates it there. To have Risotto reply instead, tick Activate Risotto to respond with new department in the move dialog. A closed or solved ticket moves without escalating.

What the requestor sees

Nothing changes for the requestor. The conversation stays in the same Slack thread, because a sub-department posts to its parent's agent channel. The ticket ID gains the sub-department's part, for example IT-218 becomes IT-NET-218. The old ID still opens the ticket.

What is shared and what is separate

Knowledge and tools are set up once, on the parent. Queues, people, and service levels belong to each sub-department.

SettingComes from the parentThe sub-department's own
Runbooks, knowledge, indexes, tools, categories, service catalogYes. Department pickers offer only the parent.
Slack agent channelYes, always. The General page shows it as inherited and locked.
MembersThe parent's members, with their parent roleMembers added on the sub-department's Members page
TicketsYes
Escalation rulesYes. They can route only to people.
Escalation contact, custom escalation message, review switches, AI beta opt-in, ticket sync, SLA targets, auto-resolve settingsCopied once when the sub-department is createdYes. Edited independently after creation.
Additional ticket fieldsYes. A new sub-department starts with none.
Priority rulesNot used. Priority is set in the parent, before a ticket reaches a sub-department.

Members and roles

Access flows down, never up. A parent department's members can work every sub-department's tickets. A sub-department's own members see only that sub-department.

  • A parent Supervisor is a Supervisor in each sub-department. A parent Agent is an Agent in each sub-department.
  • You can give someone a higher role in one sub-department only, for example Agent in IT and Supervisor in IT / Networking. A role set on the sub-department never lowers the access they hold through the parent.
  • The sub-department's Members page lists its own members first. A member who also belongs to the parent carries a badge with their parent role, for example IT Agent. The parent's other members follow, marked Agent in IT or Supervisor in IT. Manage those people on the parent's Members page.
  • The person who creates a sub-department becomes its Supervisor, unless they are already a Supervisor in the parent.
  • A member of only a sub-department can open the parent department's settings pages and read them, for example to see the agent channel the sub-department inherits. They cannot change the parent's settings. The Settings sidebar lists only the departments you can edit, so for them the parent is not listed and the sub-department appears at the top level. On the sub-department's pages, the parent's name in the breadcrumb is plain text.

See Permissions for what each role can do.

Limits

  • One level only. A sub-department cannot have sub-departments.
  • The parent is fixed at creation.
  • A sub-department cannot accept requests directly, cannot be the default department, and cannot have its own Slack agent channel.
  • An existing department cannot be moved under a parent.

Delete a sub-department

  1. Open the sub-department's settings page

    Click the sub-department under its parent in the Settings sidebar, or in the Sub-departments section of the parent's settings page.

  2. Delete it

    In the Danger zone section, click Delete Department….

  3. Confirm

    In the Delete Department? dialog, click Confirm.

The sub-department's tickets move up to the parent department and keep their old IDs as aliases.

Something wrong or missing? Report an issue · View as Markdown