Automatic priority
Set up Automatic priority so new tickets get a Low, Medium, High, or Urgent priority and a priority emoji in the channel name
Automatic priority reads the first messages of a ticket and assigns a priority based on urgency, business impact, and how the member is expressing themselves. Urgent and high tickets are flagged in the channel name and posted for staff in your alerts channel; routine questions stay at a normal priority. Staff can always change the priority. This page is for the admin who wants staff to see the important tickets first.
Automatic priority is available on Pro and Enterprise. It needs the Atlas switch at the top of AI assistant → Atlas. Upgrade your plan
Setup
Open the card
Go to AI assistant → Atlas → Set priority automatically. It is in the Sort and flag new tickets section of the What Atlas does tab.
Switch it on
Turn on the switch on the Set priority automatically card.
Choose the channel name emoji
Leave Add a priority emoji to the channel name on to show the priority in Discord, or turn it off to keep channel names as they are.
Save
Click Save changes in the bar at the bottom of the page.
Settings
| Setting | Values | Default | What it does |
|---|---|---|---|
| Set priority automatically (the card's switch) | On, Off | Off | Master switch for this feature |
| Add a priority emoji to the channel name | On, Off | On | Adds the priority emoji to the ticket channel name |
| Post urgent and high tickets in the alerts channel | On, Off | On | Posts a card for each High or Urgent ticket in your alerts channel. When off, the priority is still set, but nothing is posted |
| Change priorities staff set | On, Off | Off | When off, Atlas only sets a priority on tickets that have none. When on, it also replaces a priority that is already set, including one staff set, and checks again as the member writes more |
Everything else is handled for you: Atlas waits until the member has explained the problem and only sets a priority it is confident about. The alerts channel is AI alerts under General → Where the bot posts; when it is not set, the cards go to your logs channel.
Priority levels
| Priority | Emoji | What the AI puts here |
|---|---|---|
| Urgent | 🔴 | Outages, security problems, anything that costs money. The AI calls this level "Critical" in its analysis |
| High | 🟠 | Something is blocked or an important feature is broken |
| Medium | 🟡 | A bug with a workaround, or a feature request |
| Low | 🟢 | General questions, small issues, help with the docs |
What happens
- A member opens a ticket and writes.
- Atlas waits until the member has explained the problem: it checks after their second message, or about 30 seconds after the first, so quick follow-ups are read together.
- The AI assigns a priority with a confidence score. When it is not confident, nothing changes.
- With Add a priority emoji to the channel name on, the channel is renamed with the emoji, for example
🔴-ticket-0001. Discord allows two renames per channel every 10 minutes, so on a busy ticket the emoji can appear a few minutes after the priority is recorded. It goes in its fixed place next to the pin and claim markers (Channel name markers). - For High and Urgent only, and while Post urgent and high tickets in the alerts channel is on, a 🤖 AI Priority Detection card is posted in your alerts channel showing the ticket, Priority, Confidence, User, AI Analysis (the reasoning), and Urgency Indicators when any were found. Nobody is pinged. Change its wording on the Messages page (AI priority alert).
- The priority is stored on the ticket and shows in the dashboard, the same as a priority set with
/priority. If you use Response targets, the ticket's targets follow its new priority.
Working with staff
- Staff set or change priority at any time with
/priority level:<urgent|high|medium|low|none>. - Atlas only sets a priority on tickets that have none, so a priority set by staff is never changed. Turn on Change priorities staff set if Atlas should replace it; Atlas then checks again as the member writes more, and its priority wins over the one staff set.
- Once staff have replied to or claimed a ticket with no priority, Atlas stops checking it and leaves the priority to them, unless Change priorities staff set is on.
- A ticket that opened at a role's priority under Priority support can still be raised by Atlas, but never set below that priority, even with Change priorities staff set on.
- Automatic priority does not move tickets or ping roles. Combine it with Sorting to move tickets and Tone alerts for alerts.
Limits and gotchas
Atlas skips tickets from members on AI assistant → Atlas → Keep Atlas away from, and tickets opened from a panel button that turns Atlas off.
- The alerts channel card only appears for High and Urgent, and only while Post urgent and high tickets in the alerts channel is on. Medium and Low priorities are recorded silently.
- Channel renames count against Discord's limit of two renames per 10 minutes per channel.
- Each check draws tokens from the bot owner's monthly allowance. See AI usage.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No priority is ever set | The card or the Atlas switch is off, or the bot owner's plan is below Pro | Check both switches and the plan |
| A ticket keeps no priority | The AI was not confident, or the member is on Keep Atlas away from | Set it with /priority |
| Priority is recorded but the channel name does not change | Add a priority emoji to the channel name is off, or the channel has used Discord's two renames for the last 10 minutes | Turn the setting on. A rename held back by the limit happens on its own once the limit resets |
| No card in the alerts channel | The priority was Medium or Low, Post urgent and high tickets in the alerts channel is off, or neither an AI alerts channel nor a logs channel is set | Only High and Urgent are posted. Turn the setting on, and choose a channel under General → Where the bot posts |
| Atlas changed a priority staff set | Change priorities staff set is on | Turn it off on AI assistant → Atlas → Set priority automatically |
/priority replies with TC002 | The user is not staff | Give them a configured staff role |
/priority replies with TC017 | The command was used outside a ticket channel | Run it inside the ticket |
Common questions
Which plan do I need? Pro or Enterprise. On lower plans the whole AI assistant page is locked with a Pro+ badge.
Does the AI ping anyone? No. Urgent and high tickets are posted as a card without mentions. Use Tone alerts to ping a role when a member is upset.
Why is the AI's "Critical" shown as Urgent?
The AI's four analysis levels are Critical, High, Medium, and Low. Critical is stored as the ticket priority Urgent so it matches /priority.
How long does Atlas wait before it decides? Until the member's second message, or about 30 seconds after their first one. You do not need to set any timing.
Will it change the priority again later in the ticket? Not by default: a ticket that already has a priority, from staff or from Atlas, is left alone. With Change priorities staff set on, Atlas checks again as the member writes more and can replace any priority, including one staff set.
Can I stop the urgent ticket cards in the alerts channel? Yes. Turn off Post urgent and high tickets in the alerts channel on AI assistant → Atlas → Set priority automatically. Atlas still sets priorities and the channel emoji.
Where do I see the detected priority? On the ticket in the dashboard and, with Add a priority emoji to the channel name on, as the emoji at the start of the ticket channel name in Discord.
Join our Discord server for support
Was this page helpful?
Last updated on