> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/request-management/request-and-service-management-service-catalog/category-services-management.md).

# Organize categories and services

Create Categories and Services in Siit so employees pick a category then a service from Slack, Teams or the portal, to route requests and track volume per service

One of Siit’s key strengths is its ability to easily categorize employee requests using the **Category & Services** feature. This helps:

**🔀 Automatically route requests** to the right team based on the selected service

📊 **Track request volume** per service to identify process gaps or missing knowledge base content

When submitting a request via **Slack, Teams or through our Request Portal**, employees can select a **Category** first, which will dynamically display the corresponding **Services**.

**🔧 Setting Up Categories & Services**

To configure them, follow these steps:

**Create Categories & Services**

1️⃣ **Create a Category**> Manage categories

2️⃣ **Create a Service** (from scratch or using a template) > + Add

3️⃣ **Name the Service**

4️⃣ **Link it to a Category**

5️⃣ **Pick a color** (💡 Best practice: use one color per category for all its services)

**Enable Automatic Assignment ⚡**

You can **automatically assign** a Service to a specific user or inbox (see [Inbox Management article](/guides/request-management/inboxes-management.md)). This ensures all requests for that service go directly to the right team—**no need for extra workflows!**

**Use Dynamic Forms 📝**

Want to collect more precise information when employees submit requests? Use Dynamic Service Forms to display specific questions based on the selected service (see [Service Forms article](/guides/request-management/request-and-service-management-service-catalog/create-forms.md)).

**Define the Audience 🎯**

Decide which employees the service will be visible by using our dedicated filters (department, office location, job title etc)

{% hint style="warning" %}
**Apply SLAs ⏳**

If you’re on the **Pro Plan**, you can enable **SLA tracking** to set response and resolution time targets (see [SLA Management article](/guides/request-management/request-and-service-management-slas/sla-management.md)).
{% endhint %}

🚀 **You’re all set!** Don’t forget to **save & publish** your service so it goes live!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/guides/request-management/request-and-service-management-service-catalog/category-services-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.