Docs

Admin / Organization

Write effective department descriptions

How Risotto uses department descriptions to route new requests, and how to write descriptions that send each request to the right team

Every department has a required Description that says what the department is responsible for. When a new request arrives, Risotto compares it with the name and description of each top-level department, and sends it to the department that handles what the request is about.

A clear description is the most effective way to improve routing. The field's hint in the dashboard says it too: "A detailed description will help Risotto route requests correctly."

Where the description is used

  • Routing new requests. Risotto reads each top-level department as its name and description, for example "IT - Manages all technology-related services…". If no department fits the request well enough, the ticket goes to the default department.
  • Suggested categories. When you create a department, Risotto suggests its first categories from its name and description.
  • The Slack App Home. When employees start a request from the Home tab of the Risotto app, the department list shows each department's description under its name. Slack shows only about the first 70 characters, so put the summary first.

Some requests skip the comparison:

  • A request from a channel or direct message that is locked to a department goes to that department. See Channel-specific routing.
  • A request from the Slack App Home goes to the department the employee picks.

Sub-departments are never compared, so their descriptions don't affect routing. A ticket reaches a sub-department from its parent, through an escalation rule or a manual move.

Edit a description

You set the description when you create a department. To change it, open Settings, click the department, and on its General page edit Description, then click Save. Risotto uses the new description for the next request it routes. Tickets that already have a department keep it.

What to include

Every department description should cover two things:

  1. The department's core function: what the team is responsible for.
  2. The requests it should receive: the services, systems, and topics it owns.

How to write a good description

  • State what your department owns. List the domains, services, and types of requests your team handles. The list does not need to be complete, but it should cover the main areas of your team's work. Be specific: "software access, hardware maintenance, network security, and employee technical support" is better than "technology stuff".
  • Use the words employees use. Name the tools and systems that come up in real requests to your team.
  • Draw the line between departments. If HR handles "employee onboarding" and IT handles "account setup for new hires", say so in both descriptions, so that Risotto can tell them apart.
  • Describe the request, not the requester. Risotto routes on what the message is about. It does not check who sent it, so it ignores conditions such as "requests from the Sales team". To send all requests from one place to one department, lock the channel instead.
  • Keep it focused. There is no length limit, but a few sentences that name the main request types are usually enough. Lead with the summary, because the Slack App Home shows only the start.

Examples

These examples show descriptions for common departments.

IT / Information Technology

The Information Technology (IT) department manages all technology-related services and requests, including software access, hardware maintenance, network security, and employee technical support.

Why it works: Covers the core domains (software, hardware, network, support) and uses terms employees naturally reach for.

Human Resources

The Human Resources department handles employee onboarding, benefits enrollment, payroll questions, leave requests, and workplace policy inquiries.

Why it works: Lists HR-specific processes, and claims onboarding paperwork without claiming account setup, which belongs to IT.

Finance

The Finance department handles expense reports, purchase orders, budget approvals, corporate card requests, and vendor payment inquiries.

Why it works: Focuses on the day-to-day requests employees actually send to Finance, not accounting functions they would never ask about in chat.

Facilities / Office Operations

The Facilities department manages office access, building maintenance requests, desk and conference room bookings, and physical security badge issues.

Why it works: Separates physical-space requests from IT requests, a common source of misrouting.

Common mistakes

  • Too broad: "Handles everything related to employees" overlaps with almost every department.
  • Too narrow: "Resets passwords" misses all the other IT requests your team handles.
  • Duplicated scope: If two departments both claim "software access", Risotto has to pick one. Make ownership explicit in each description.
  • Conditions on the requester: "Route here when the requester is in Sales" can't be checked when Risotto routes. Lock the Sales channel to the department instead.

Next steps

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