# Departments and routing (video)

A two-minute video of how requests reach the right team: add a department and a sub-department, set its categories and priority, connect a request source, and watch a request from Slack land in its queue.

Watch a Security department set up next to IT in two minutes, then watch a request from Slack find it. Each step below links to its written guide.

[Video: Departments and routing](https://media.tryrisotto.com/videos/departments-routing-desktop.mp4)

Every request goes to one department. A request from a source that is locked to a department goes straight there. Every other request is matched against each department's description. See [Enterprise routing](https://www.tryrisotto.com/docs/concepts/enterprise-routing).

Before you start, make sure you are an Org Admin or a Manager: only these roles can create departments. Only Org Admins and Managers see **Request Sources**.

## The seven steps

1. **Add the department**

   In **Settings**, click the **+** next to **Departments**, and name it
   Security. Risotto routes on the description, so be specific. Name what
   employees ask about, such as phishing emails, suspicious logins, lost
   laptops, and new app reviews. Click **Create**, pick the team's **Agent
   Channel**, and click **Save**. See [Add a new
   department](https://www.tryrisotto.com/docs/guides/add-a-department) and [Write effective department
   descriptions](https://www.tryrisotto.com/docs/guides/department-description-guide).

2. **Add a sub-department**

   A sub-department is a specialist queue with its own tickets and members,
   that shares its parent's knowledge and agent channel. On Security's
   settings page, click **New sub-department**, name it Incident Response,
   describe it, and click **Create**. See
   [Sub-departments](https://www.tryrisotto.com/docs/dashboard/settings/sub-departments#create-a-sub-department).

3. **Set categories**

   Open **Settings > Categories** and pick Security. Risotto already suggested
   some categories from the department's name and description. Click **Create
   category** to add one, like Phishing, and describe which requests belong in
   it. See [Categories](https://www.tryrisotto.com/docs/dashboard/settings/categories#create-a-category).

4. **Set priority**

   On Security's **Priority** page, edit what each level means under
   **Urgency criteria**. Urgent might be a suspected breach, or a phishing link
   someone clicked. Risotto suggests a priority for each new request from these
   criteria. Click **Save**. See [Ticket
   Priority](https://www.tryrisotto.com/docs/dashboard/settings/ticket-priority#set-up-priority-for-a-department).

5. **Route to the sub-department**

   Requestors never pick a sub-department, so add a rule on Security's
   **Escalations** page. Click **Add rule**, add the ticket condition
   **Category** equals Phishing, choose **Hand off to a sub-department**, pick
   Incident Response, and click **Save**. See [How tickets reach a
   sub-department](https://www.tryrisotto.com/docs/dashboard/settings/sub-departments#how-tickets-reach-a-sub-department)
   and [Escalation
   routing](https://www.tryrisotto.com/docs/dashboard/settings/departments#escalation-routing).

6. **Connect a request source**

   In **Settings > Request Sources**, click **Manage in Slack**, then **Add
   Channel**, and join the ask-security channel. A new channel starts with
   **Silent mode** on, so turn it off, then set **Lock to department** to
   Security. See [Add a Slack
   channel](https://www.tryrisotto.com/docs/dashboard/settings/request-sources#add-a-slack-channel) and
   [Channel-specific
   routing](https://www.tryrisotto.com/docs/concepts/enterprise-routing#channel-specific-routing).

7. **Watch it work**

   In the IT help channel, an employee says she clicked a link in a fake
   payroll email. That channel isn't locked, so Risotto matches the request to
   Security's description. The ticket lands in Security's queue with the
   category Phishing and a suggested priority of Urgent, marked with the
   sparkles icon. Now Risotto starts working on it with Security's knowledge,
   runbooks, and tools: routing puts the ticket in the department, and the
   department's setup comes with it. If it escalates, the rule moves it to
   Incident Response. See
   [Context-aware
   routing](https://www.tryrisotto.com/docs/concepts/enterprise-routing#context-aware-routing) and
   [AI-suggested
   priority](https://www.tryrisotto.com/docs/dashboard/settings/ticket-priority#ai-suggested-priority).

To improve routing, start with the descriptions. A request that no department clearly handles goes to the [default department](https://www.tryrisotto.com/docs/concepts/enterprise-routing#org-default).

Source: https://www.tryrisotto.com/docs/guides/departments-video
