---
title: Ticket Categories
slug: admin-guide/ticket-categories
docTags:
createdAt: 2025-04-21T14:13:49.461Z
---
How to create a new category? [Add a new category](docId:_9Exa67Ggm8JT4FkNPcb2)
How to define specific routing for a category? [Set up default routing](docId:_9Exa67Ggm8JT4FkNPcb2)
I’ve added a new category, but it’s not showing up in the ticket category list. [Display a new category in the ticket](docId:_9Exa67Ggm8JT4FkNPcb2)
***
# Categories overview
Categories enable you to group similar things together. In the ITCC system, you can use ticket categories to group together tickets that have something in common.
Each ticket can have up to three levels of categories.
Categories can be assigned automatically based on a ticket template or selected by the user when creating a ticket.
## Categories example
For example, in the following setup, the user must choose between communication, hardware, or software.
## Levels of categories
You can set up up to three levels of categories:
- Parent category
- Category
- Subcategory
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/VJpjqJEWSFaBL6VMMMWra_image.png" size="84" width="1108" height="82" position="center" showCaption="false"}
You can change the label of each level of category to meet your organization's needs. The labels can also be translated into other languages.
For example, in the New Incident screenshot above, the three levels are labeled as Category, Subcategory, and Item.
You can also omit one or two levels of categories.
For each ticket type, you can set default values for the categories.
## Category names
Each category is required to have three levels of names:
- Parent category
- Category
- Subcategory
Each name can be used more than once, but the combination of all three names must be unique.
An attempt to enter a combination of names that already exists in the system results in an error.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/CUYixS2482AuMVnRwskWV_image.png" size="70" width="430" height="80" position="center" showCaption="false"}
## Displaying categories as icons
You can display the categories as a dropdown list, as in the [example](docId:_9Exa67Ggm8JT4FkNPcb2) above.
You can also display categories as icons and allow the user to choose an icon when creating a new ticket. You can use up to three levels of categories to be displayed as icons.
In the following example, when creating a ticket of type Incident, the requestor can select one of the three available parent categories: Hardware, Internet & System, and Software.
If the requestor selects the Hardware parent category, the next level of categories appears. The requestor can select from Accessories, Printer, or Workstation categories.
If the requestor selects the Accessories category, the next level of categories appears. The requestor can select from Docking Station, Keyboard & Mouse, and Monitor - Display Issue subcategories.
If the requestor selects Docking Station, a ticket creation dialog opens, with the values of categories set to:
- Parent category: Hardware
- Category: Accessories
- Subcategory: Docking Station
To enable displaying categories as icons for any specific [ticket type](docId\:j72X-S41zFXQ-EkU8Z4p5):
:::Paragraph{indent="1"}
in this ticket type's [Categories settings](docId\:j72X-S41zFXQ-EkU8Z4p5), toggle the **Enable Category Selection via Icons** and specify the **Start Level **and the **End Level**.
:::
## Categories and ticket types
You can define separate ticket categories for each ticket type, or you can define categories that are available to more than one ticket type.
It is also possible to make a parent category available to multiple ticket types but limit the ticket types to which its subcategories are available.
For example, if your setup includes the ticket types *Incident* and *Reques*t, you may want to make the parent category *Communication* available to both. However, only some subcategories of *Communication* need to be available to both. The subcategory *Recording* can be either an *Incident*, where the user has trouble with a recording, or a *Request*, where the user requests a recording. However, the subcategory *Unable to Connect* can only be an *Incident* and not a *Request*. In [settings](docId:_9Exa67Ggm8JT4FkNPcb2), you can set up your categories so that *Recording* is available to both *Incident* and *Reques*t types and *Unable to Connect* is only available to *Incident *type.
The category settings override the ticket type settings.
For example, if the default ticket type severity is Medium and the default category severity is High, the ticket's severity is set to High.
# Setting up categories
You can set up categories at any time.
**To set up categories:**
::::WorkflowBlock
:::WorkflowBlockItem
On the left side menu, select **Administration**.
:::
:::WorkflowBlockItem
In the search bar under **Search for Admin Configuration Options**, type Categories and select the **Categories** option that appears.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/OaPhElufyR_gIbPWRuWYV_image.png" size="82" width="1507" height="884" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
From the **Categories** page that opens, you can:
- [Add or edit a category](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Configure categories' settings](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Set up ticket routing](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Duplicate a category](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Disable a category](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Rename a category](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Set up email notification settings](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Upload categories from a spreadsheet](docId:_9Exa67Ggm8JT4FkNPcb2)
:::
::::
## Adding or editing a category
You can add a new category or edit an existing category at any time.
**To add or edit a category:**
::::WorkflowBlock
:::WorkflowBlockItem
On the **Categories** page:
- To add a category: select **Add A New Category** and enter the new category's Parent Category, Category, and Subcategory names
- To edit a category: search for or scroll down to the category you want to edit
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/YUfQ6Oyr9r37q3C0sDtDb_image.png" size="88" width="2440" height="342" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
(Optional - can be done at a later stage) Configure the following:
- [Settings](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Ticket routing](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Enable or disable this category](docId:_9Exa67Ggm8JT4FkNPcb2)
- [Email notification settings](docId:_9Exa67Ggm8JT4FkNPcb2)
:::
:::WorkflowBlockItem
Select **Save**.
:::
::::
## Quick edits for one category
From the Categories page, you can make quick edits to one category at a time.
To configure multiple categories at the same time, see [Configuring categories' settings](docId:_9Exa67Ggm8JT4FkNPcb2).
The Categories page displays a spreadsheet with each category's settings.
The spreadsheet is fully customizable. Use **Actions->Columns** to choose which columns the spreadsheet displays.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/2MtANDvbrD9ZB2Gtc1asE_image.png" size="62" width="796" height="467" position="center" showCaption="false"}
In any setup, some columns are read-only and others are editable. Read-only columns are shaded in gray.
For example, the Active column is read-only. To [enable or disable a category](docId:_9Exa67Ggm8JT4FkNPcb2), you can enter current or future date into the Disable Date column or use the **Enable/Disable** button above the spreadsheet.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/eoePYycSeCqI_Po_jKjnI_image.png" size="62" width="775" height="358" position="center" showCaption="false"}
You can use the editable columns to make quick changes to a category's settings.
For example, you can use the Priority column to adjust a category's priority.
## Configuring categories' settings
You can make [quick edits](docId:_9Exa67Ggm8JT4FkNPcb2) to one category's settings from the spreadsheet on the Categories page. You can also configure a category's settings through the setup dialog.
When using the setup dialog, you can configure settings for multiple categories at the same time.
When configuring settings for multiple categories, for each field where different categories have different values, you can choose the value **\*Multiple, Keep Current Values**. This setting preserves the current values for each of the categories instead of overriding them.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/6i6oD_HRwE_HpacX6h7fW_image.png" size="38" width="320" height="84" position="center" showCaption="false"}
**To configure categories' settings:**
::::WorkflowBlock
:::WorkflowBlockItem
On the **Categories** page, search for or scroll down to the categories you want to set up and select the corresponding checkboxes in the leftmost column.
:::
:::WorkflowBlockItem
Select **Setup**. The setup dialog opens.
:::
:::WorkflowBlockItem
If configuring multiple categories: in the dialog that opens, some of the fields have values **\*Multiple, Keep Current Values**. If you want to override any of these values to be the same across all the selected categories, select the new value from the dropdown list.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/6i6oD_HRwE_HpacX6h7fW_image.png" size="38" width="320" height="84" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
Enter or edit the settings:
| Option | Description |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| End Users | Select Y if tickets in this category are available to end users or N if not available to end users |
| Externals | If available to end users, select:
- All: for all end users
- Externals: only for external end users
- Internals: only for internal end users |
| Organization | Select the organization for which this category is valid |
| Show CI | - Select Yes to display and enable selection from a dropdown list of Configuration Item assets
- Leave blank or select No to not display such list |
| Service | Select a service you want to relate to this category |
| Severity | Select a default severity for this category; overrides default severity for this ticket type |
| SLA | Select a default SLA template for this category; overrides default SLA template for this ticket type |
| Survey | Select a default survey for this category; overrides default survey for this ticket type |
| Auto Close | Select Yes if you want ITCC to automatically resolve the ticket and send a resolution email to the customer.
- When enabled, immediately after the ticket is submitted, its status changes to Resolved, and a resolution email is sent to the customer.
- When using this option, it is highly recommended to create a dedicated Resolution email template for the relevant category. The template should include either a link to a Knowledge Article **or** clear resolution steps written directly in the email body |
| Attach form | Select a form to customize tickets in this category with additional fields |
| Disable closure | Select "Yes" to disable closure of tickets of this category and require the agents to change the ticket's category before closing it (applicable to generic categories, such as "submitted by email"); select "No" to enable closure |
| Key | Numeric ID for this category |
| Missing Attachment Warning Text | Enter a message to be displayed if this category requires an attachment and no attachment is found on the ticket submission |
| Limit Types | If the parent category is available to more than one ticket type, you can limit this category to only some of these ticket types by selecting (in this field) ticket types to which this category is limited; leave blank to make this category available to all ticket types that its parent category is available to (see [Categories and ticket types](docId:_9Exa67Ggm8JT4FkNPcb2) for an example) |
| **HTML Text** | |
| Display HTML | Select:
- **No** to not display any HTML content
- **Yes** to display HTML content in every ticket of this category |
| Display HTML To | Select to whom the HTML is visible:
- All users
- End users
- Non-end users
- None |
| HTML Content | Enter content, in HTML, that you want each ticket in this category to display to the user |
| Additional Attributes | If needed, specify up to 5 additional attributes for these categories (used for internal codes from different systems integrated with ITCC) |
:::
:::WorkflowBlockItem
Select **Save**.
:::
::::
## Setting up ticket routing
Ticket routing determines to which group or agent a ticket is routed initially and where it is forwarded in case of escalation.
You can set up ticket routing for a category that overrides the default ticket routing for its ticket type.
You can set up ticket routing for multiple categories at the same time. For each of the fields, you can choose to keep the default options for each category or override them for all the categories you are setting up.
The ticket routing can be applied to all tickets in this category, or it can be conditional, based on the values of:
- ticket type
- severity
- user site
- user city
**To set up ticket routing:**
::::WorkflowBlock
:::WorkflowBlockItem
On the **Categories** page, search for or scroll down to the categories you want to set up and select the corresponding checkboxes in the leftmost column.
:::
:::WorkflowBlockItem
Select **Routing**.
:::
:::WorkflowBlockItem
In the dialog that opens, enter routing settings:
| Option | Description |
| ---------------- | -------------------------------------------------------------------------- |
| Default Group | Group to which tickets in this category are assigned by default |
| Escalation Group | Group to which tickets in this category are assigned in case of escalation |
| Default Assignee | The agent to whom tickets in this category are assigned by default |
| Follower 1 | User who receives all email updates related to tickets in this category |
| Follower 2 | User who receives all email updates related to tickets in this category |
:::
:::WorkflowBlockItem
If needed, [set up conditional routing](docId:_9Exa67Ggm8JT4FkNPcb2).
:::
:::WorkflowBlockItem
Select **Save**.
:::
::::
### Conditional routing
Your organization can use conditional routing, where the routing destination depends on certain conditions.
For example, if your organization supports multiple sites, you can use conditional routing to route each ticket to the local team that provides support to the site where the ticket originated.
The following conditions are available for determining the override routing:
| Condition | Description |
| ----------------- | -------------------------------------------------------------------------------------------- |
| When Type Is | Choose ticket type for this routing; keep the default *ALL* value to skip this condition |
| When Severity Is | Choose severity value for this routing; keep the default *ALL* value to skip this condition |
| When User Site Is | Choose user site value for this routing; keep the default *ALL* value to skip this condition |
| When User City Is | Choose user city value for this routing; keep the default *ALL* value to skip this condition |
The following can be set based on the above conditions:
| Option | Description |
| ----------- | ------------------------------------------------------------------------------------------------- |
| To Group | Group to which tickets in this category are routed if the conditions are met |
| To Assignee | Agent to whom tickets in this category are routed if the conditions are met |
| Follower 1 | User who receives all email updates related to tickets in this category if the conditions are met |
| Follower 2 | User who receives all email updates related to tickets in this category if the conditions are met |
You can add, edit, or delete conditional routing at any time.
**To set up conditional routing:**
::::WorkflowBlock
:::WorkflowBlockItem
In the **Routing** dialog, under **Override Routing Options**, select **Add Row**.
:::
:::WorkflowBlockItem
In the new row that appears, select conditions and values you want to apply (see [Override routing options](docId:_9Exa67Ggm8JT4FkNPcb2)).
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/lZyCw5U1GHhEB07TV1qDB_image.png" size="60" width="1270" height="246" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
Add as many conditions as you need. To delete existing conditions, select the corresponding checkboxes in the first column and select **Delete Checked**.
:::
:::WorkflowBlockItem
Select **Save**.
:::
::::
## Duplicating categories
You can duplicate one or more categories and save them under different names.
Duplication can be useful when you want to copy the settings of an existing category when creating a new category.
In some cases, you may want to duplicate a subcategory and use it under a different parent category. For example, if you have a subcategory *Unable to Connect* under *Communication* parent category and *Webex* category, you may want to reuse it under *Communication* parent category and *Zoom* category.
**To duplicate categories:**
::::WorkflowBlock
:::WorkflowBlockItem
On the **Categories** page, search for or scroll down to the categories you want to duplicate and select the corresponding checkboxes in the leftmost column.
:::
:::WorkflowBlockItem
Select **Duplicate.**
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/mNmpDqD45yO6RC9vEmIuA_image.png" size="54" width="2442" height="370" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
In the **Duplicate** dialog that opens, enter the new names for the duplicated categories. If you are duplicating more than one category, you can enter one parent category (Category 1) name and one category (Category 2) name for all of them and select **Apply**.
:::
:::WorkflowBlockItem
Select **Save**.
:::
::::
## Enabling or disabling a category
You can enable or disable a category at any time.
**To enable or disable a category:**
::::WorkflowBlock
:::WorkflowBlockItem
On the **Categories** page, search for or scroll down to the category you want to enable or disable and select the checkbox in the leftmost column.
:::
:::WorkflowBlockItem
Select **Enable/Disable**.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/AzN5eYyNFkybLvHkNEcpi_image.png" size="94" width="1022" height="294" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
In the dialog that opens:
- to enable the category: set the **Effective From** to today's date
- to disable the category: set **Effective End Date** to today's date
:::
:::WorkflowBlockItem
Select **Save**.
:::
::::
## Renaming categories
You can rename a category by editing its entry on the **Categories** page.
You can also rename multiple categories at the same time if they share their Parent Category name, Category name, or both. You can change the shared name for all of them to a different shared name. This can be useful, for example, if the shared name was originally misspelled.
**To rename multiple categories with a shared name:**
::::WorkflowBlock
:::WorkflowBlockItem
On the **Categories** page, search for or scroll down to the categories you want to rename and select the corresponding checkboxes in the leftmost column. (The categories you select must have the same Parent category name or Category name.)
:::
:::WorkflowBlockItem
Select **Rename**.
:::
:::WorkflowBlockItem
On the **Rename** dialog that opens, enter the new name or names and select **Rename**.
:::
::::
## Configuring email notification settings
By default, the system sends out an email whenever an event occurs. For example, when a ticket is created, an email is sent to the Requester. Whenever a ticket is assigned to an agent, an email is sent to this agent.
You can override the system-wide email notification settings using the settings you choose for this category.
**To set up email notifications:**
::::WorkflowBlock
:::WorkflowBlockItem
On the **Categories** page, search for or scroll down to the categories you want to set up and select the corresponding checkboxes in the leftmost column.
:::
:::WorkflowBlockItem
Select **Email Setup**.
:::
:::WorkflowBlockItem
Select or clear the following email rules for this category and for its subtasks:
| Email Rule | Description |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| !! Discard All Emails | Don't send emails upon any event |
| APPROVAL | Send an approval request to the designated approver(s) |
| AUTO-DISPATCH | Notify a group that a ticket has been automatically dispatched to them |
| CANCEL | Send a confirmation to the customer that their ticket has been cancelled |
| CLOSE | Send a confirmation to the customer when their ticket is closed, whether manually by an agent, resolution approved by the customer, or automatically closed due to no response to the resolution notifications |
| CREATE | Send a confirmation to the customer about their new ticket creation |
| DISPATCH | Notify a group that a ticket has been manually assigned to them |
| ESCALATION | Send to designated escalation group when a ticket is
answering an escalation condition |
| INTLOG | Notify users mentioned in an ITCC thread (internal note) |
| ITCC\_ICAL | Send a calendar invitation to the specified attendees |
| LOG | Notify the customer or group/owner that a new note has been added to the ticket |
| PAUSE | When agent changes ticket status to Pending Customer, a notification is sent to the customer with the pending remarks |
| PENDING\_CLOSURE | Notify the customer about the automatic closure of their ticket due to no response |
| PENDING\_REMINDER | When ticket status is Pending Customer and the customer is not responding, a reminder is sent to the customer after a specified number of hours |
| REASSIGN | Notify agent that a ticket has been assigned to them |
| REJECT\_TO\_REQUESTOR | Notify the requestor that their request has been rejected |
| REOPEN | Notify the handling group or assignee that a ticket has been reopened |
| RESOLUTION\_REMINDER | Remind the customer that a ticket is resolved and awaiting their approval/rejection |
| RESOLVE | Notify the customer that a ticket is resolved and awaiting their approval/rejection |
| RESOLVE\_NV | Notify the customer that a ticket will be resolved in next version |
| STATUS\_CHANGE | Administrators can set up alerts for changes in ticket status |
| TASK\_REMINDER | Send a reminder about an upcoming or overdue task |
| THIRD\_PARTY | Notify a third-party vendor that a ticket has been assigned to them |
:::
:::WorkflowBlockItem
Select **Save**.
:::
::::
## Uploading categories from a spreadsheet
You can upload categories in bulk from a spreadsheet.
If you need a template to help you format your spreadsheet, you can download it from the Categories page.
**To upload categories from a spreadsheet:**
::::WorkflowBlock
:::WorkflowBlockItem
If you need a template for your categories spreadsheet, select **Download Template**.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/TQx431FBjXMr7uIDnOhNS_image.png" size="52" width="1288" height="326" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
On the **Categories** page, select **Upload**. The **Upload Categories** page opens.
:::
:::WorkflowBlockItem
When your spreadsheet is ready, select **Choose File.**
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/0te-UApa5nUD4MCik4TW6_image.png" size="68" width="1225" height="309" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
Select the file you want to upload and select **Open**.
:::
:::WorkflowBlockItem
Select the **Load File** button that appears.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/0Qi6Lwwx7n2o3mq4RB2EV_image.png" size="40" width="1254" height="538" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
After your file is uploaded, the following message appears:
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/qGqrgXWV2Oqq_C8gSWsSD_image.png" size="60" width="656" height="152" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
Select the **Process All Records** button that appears.
:::
:::WorkflowBlockItem
After the records are processed, a success message appears.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/hbqwbP8vT3BbRJhD3MdRG_image.png" size="54" width="708" height="105" position="center" showCaption="false"}
:::
::::
## Making a new category available to a ticket type
When you create a new category, it is automatically available to those ticket types that have no parent category filters.
For ticket types with parent category filters, you must add the new parent category to the filter in order to make it available.
**To add a parent category to a ticket type filter:**
::::WorkflowBlock
:::WorkflowBlockItem
On the left side menu, select **Administration**.
:::
:::WorkflowBlockItem
In the search bar under **Search for Admin Configuration Options**, enter **Ticket Types** and select the **Ticket Types** option that appears.
:::
:::WorkflowBlockItem
Search for or scroll down to the ticket type to which you want to add the parent category and select its Edit icon.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/X_mdOCWC8rCJSjf5mKU-u_image.png" size="44" width="470" height="132" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
On the **Setup Admin** page that opens, on the menu on the right, select **Categories**.
::Image[]{src="https://api.archbee.com/api/optimize/zEVWKsZtpmpx-RIpALRPL/UD9lI8JBCHulDeSgBuYOI_image.png" size="42" width="479" height="757" position="center" showCaption="false"}
:::
:::WorkflowBlockItem
From the **Parent Category Filters** dropdown list, select the parent category you want to add.
:::
:::WorkflowBlockItem
Select **Save**.
:::
::::