Priorities
Rename, recolor, order and hide your project's priorities, and add your own
Every project starts with four priorities: Urgent, High, Medium and Low. Feedback can also have No priority. You can rename and recolor the four, put them in your own order, hide the ones you don't use, and add your own, such as "P0 – Outage" or "VIP".
Changing priorities requires a Pro or Pro Max plan. On other plans, projects use the four built-in priorities. If a workspace moves to another plan, its projects keep the priorities they have, but they can't be changed.
Where to Find Them
- Open a project and click Settings
- Go to the Feedback tab
- Expand Priorities
The list shows the project's priorities, most urgent first. Each change is saved as you make it. Owners and Admins can change priorities; other roles see the list.
Built-in Priorities
Urgent, High, Medium and Low are built in. You can:
- Rename one: click the pencil and type a name. Leave the name empty to go back to the built-in name, which is shown in each person's language. A name you type is shown as typed in every language
- Recolor one: pick a color, or type a hex code such as
#7c3aed - Hide one you don't use (see Hiding a Priority)
Built-in priorities can't be deleted.
Adding Your Own
- Click Add Priority
- Enter a Name and pick a Color
- Under Works like, choose the built-in priority it is closest to. Places that only know four priorities use it: workflow items, Jira and Linear
- Click Save
A new priority is added at the bottom of the list. Drag it to its place.
Each priority has an ID, shown under its name. For your own priorities, the ID is made from the name when you add it (for example, "P0 – Outage" gets p0-outage), and it never changes, even when you rename the priority. Use the ID with the REST API and the MCP server.
Setting the Order
Drag a priority by its handle to move it. With a keyboard, focus the handle, press Space, move it with the arrow keys and press Space again. Put the most urgent at the top. The order is used:
- In every list of priorities: the priority menu on feedback, the inbox filter, automations, routing rules, intake rules and the SLA rules
- When feedback is reopened: it keeps its priority if that is High or above in your order; otherwise it is raised to High (by the name you gave it). This applies however feedback is reopened: in the dashboard, by the customer from their feedback link, a portal or email, by an automation or macro, or through the API or MCP server
Hiding a Priority
A hidden priority isn't offered when someone picks a priority for feedback, in an automation's Set priority action, or through the API. Feedback that already has it keeps it, and it still shows its name and color. The inbox filter and the conditions of automations, routing rules and intake rules still list it, and its SLA rule keeps setting due dates.
Click the eye icon to hide a priority, and again to show it. At least one priority stays visible.
Deleting a Priority
You can delete a priority you added when nothing uses it. Click the trash icon; its SLA rule is removed with it. If feedback has it, or an automation, macro, routing rule or intake rule uses it, the dialog lists what uses it and offers Hide Instead.
Where Priorities Are Used
Everywhere a priority is shown or picked, it uses your project's names and colors:
- Feedback: the priority menu and badge in the side panel and on the full page, and the activity log
- Inbox: the Priority filter lists the priorities of the projects you're viewing, with No priority (see Feedback Inbox)
- SLA & Business Hours: one row per priority, in your order (see SLA Rules)
- Automations and macros: conditions on priority and the Set priority action (see Triggers)
- Routing rules and intake rules: the Priority condition (see Routing Rules and Intake Rules)
- Analytics: the By Priority chart
- Export: the Priority column
- Notifications and emails to your team
Workflows, Jira and Linear
Workflow items have the four built-in priorities, shown with your project's names and colors. When feedback creates a workflow item, the item gets:
- The Item priority of the intake rule or of the automation's Add to workflow step, if it has one
- Otherwise, the priority the feedback's priority works like (a built-in priority is itself)
- Otherwise, Medium
Jira and Linear get the item's priority, and with Two-way Sync on, a priority changed there comes back to the item. See Managing Items and Sync Adapters.
Moving Feedback to Another Project
Feedback moved to another project keeps its priority until someone changes it, even if the other project doesn't have that priority. It keeps the name and colour it has in the project it came from, everywhere it shows: the feedback, its activity, customer timelines, analytics, exports and the MCP server. In the new project it isn't offered for other feedback.
Imports
Imports from Freshdesk, CSV and JSON set the built-in priorities. See Migration.