Sorting
Set up Sorting so Atlas moves each new ticket to the right category, from rules written in plain words
Sorting (auto-route) reads a new ticket and moves it to the category of the first rule that fits it, optionally pinging a role. You describe each rule in plain words, and Atlas understands it in every language your members write in. The ticket gets a short Ticket Routed notice, and your alerts channel shows each move as Ticket Auto-Routed. This page is for the admin who organises ticket categories.
Sorting is an Enterprise feature. It needs the Atlas switch at the top of AI assistant → Atlas and at least one Discord category to move tickets into. On Pro, the card is shown locked with an Enterprise badge. Upgrade your plan
Setup
Open the card
Go to AI assistant → Atlas → Move tickets to the right category. It is in the Sort and flag new tickets section of the What Atlas does tab.
Turn it on
Switch on the Move tickets to the right category card.
Add your rules
Click Add a rule. Fill in Name, Which tickets go here, and Move to. Optionally pick a Role to ping and Staff who can see these tickets, and add Tags to add. Click Done to fold the rule, and Add a rule again for the next one.
Put the rules in order
Atlas checks the rules from top to bottom and uses the first one that fits. Open a rule and use Move up or Move down to put the most specific rules first.
Choose what happens when no rule fits, then save
Pick an option under When no rule fits, then click Save changes in the bar at the bottom of the page. Every rule needs a name and a category before the page saves.
When no rule fits
When no rule fits sits under the rules.
| Option | What happens |
|---|---|
| Leave it where it is (default) | Nothing. The ticket stays in the category it was opened in |
| Move it to a category | The ticket moves to the Category you pick. Staff who can see these tickets limits it to those staff roles; empty keeps the category's own permissions. Until you pick a category, those tickets stay where they are |
| Tell staff in the alerts channel | A ⚠️ Ticket Requires Manual Routing card is posted in your alerts channel |
Atlas decides on its own when it has read enough: as soon as the member has written a second message, or about 30 seconds after their first one. You do not need to set any timing.
Rules
Each rule shows as one line, for example Billing questions → Billing · ping @Billing Team, with off at the end when the rule is switched off. Click Edit to open it:
| Field | Values | What it does |
|---|---|---|
| Use this rule | On, Off | Switch the rule off to keep it without using it |
| Name | Up to 50 characters, required | Shown on the alerts channel card as Matched Rule, and available to the Ticket Routed notice |
| Which tickets go here | A sentence or two, up to 500 characters | Which tickets belong to this rule. Describe them the way a member would. Atlas understands it in every language |
| Move to | One of your ticket categories, required | Where matching tickets go |
| Role to ping | A role, or No ping | Mentioned on the alerts channel card when a ticket is moved here and Atlas is confident in the match |
| Staff who can see these tickets | Staff roles, optional | Only these staff roles can see the moved ticket. Leave it empty to keep the category's own permissions. If none of the roles exist any more, the ticket still moves and keeps the permissions it had |
| Tags to add | Up to 25 tags, 50 characters each, optional | Added to the ticket when it moves here, in lowercase. Type a tag and press Enter, or paste several separated by commas. Tags the ticket already has are kept |
Move up and Move down change the order, and Remove rule deletes it. Nothing changes for your server until you save.
Atlas only moves a ticket when it is confident a rule fits; otherwise When no rule fits applies. Rules created before plain-word descriptions existed may still use keywords, topics, sentiment, urgency, or language matching. They keep working until you fill in Which tickets go here, and then Atlas follows the description.
Worked example: a good rule description
A rule works best when it reads like a briefing for a new team member: what belongs, what does not, and what to do with borderline cases.
- Name:
Payments and billing - Which tickets go here:
Charges, invoices, failed or double payments, refund requests, and subscription changes. Not tickets that only mention a price while asking a product question. If the member is angry about a charge, this rule still applies. - Move to:
Billing - Role to ping:
@Billing Team
Compare a weak description such as billing stuff: Atlas has to guess where a refund request or a pricing question goes. Spell out both what belongs and what does not.
Put the most specific rules first. For example, place Refund requests above Payments and billing, so a refund ticket lands in the refund category even though both rules fit.
What happens
- A member opens a ticket and writes their first messages.
- Atlas reads them once the member has explained the problem (after their second message, or about 30 seconds after the first).
- It goes through your switched-on rules from top to bottom and picks the first one whose description fits, as long as it is confident.
- The ticket is moved to the rule's category. With Staff who can see these tickets set, only those staff roles keep access. The rule's Tags to add are added to the ticket.
- A 🤖 Ticket Routed notice is posted in the ticket:
This ticket has been automatically routed to the appropriate team.In a ModMail ticket the member also gets it in their DMs. You can change its wording on the Messages page (Ticket routed). - A 🤖 Ticket Auto-Routed card is posted in your alerts channel, showing the ticket, Matched Rule, Confidence, User, AI Reasoning, and, when relevant, Notify Role (the pinged Role to ping) and Restricted to Roles.
- If no rule fits, When no rule fits decides what happens.
The alerts channel is AI alerts under General → Where the bot posts; when it is not set, these cards go to your logs channel.
Example rule sets
Starting points for common servers. They are examples, not built-in templates: Sorting starts with no rules. Write each description in your own words and point it at your own categories.
| Example server | Example rules, most specific first |
|---|---|
| Online store | Returns and cancellations, Orders and shipping, Payments and billing, Product questions |
| Software product | Critical bugs, Login and account, Feature requests, General tech support |
| Gaming community | Player reports, Ban appeals, Technical issues, General questions |
| General support | Urgent issues, Technical problems, General questions |
Limits and gotchas
Moving a ticket changes its Discord category. Make sure the bot has Manage Channels on every target category and that the category has room; Discord caps a category at 50 channels.
- Move to and the no-rule Category only offer your server's ticket categories.
- Sorting decides once, at the start of the ticket, before staff join in. It does not move a ticket again later in the conversation.
- A ModMail ticket that Sorting moved stays in its rule's category: the ModMail waiting categories no longer move it as the member and staff reply. Its pinned status card still shows who it is waiting on.
- Sorting skips thread tickets entirely: a thread stays in its parent channel and cannot move to a category, so Atlas does not read it, and it gets no notice, role ping or alerts channel card (not even Ticket Requires Manual Routing).
- Sorting 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 never pings the member.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Tickets never move | The card or the Atlas switch is off, no rule is switched on, or the owner's plan is not Enterprise | Check both switches, switch on Use this rule, and check the plan |
| Thread tickets are never sorted | Sorting only moves channel tickets between categories; it skips thread tickets | Nothing to fix. Point each panel button at the right thread channel instead |
| The right rule exists but rarely fires | The description is vague, so Atlas is not confident enough | Rewrite Which tickets go here with examples of what belongs and what does not |
| Two rules both fit and the wrong one wins | The wrong rule is higher in the list | Move the more specific rule up |
| Staff are not pinged | The rule has No ping, or Atlas was not confident enough to ping | Pick a Role to ping, and sharpen the description |
| The page will not save | A rule has no name or no category | Open the marked rule and fill in Name and Move to |
| No card in the alerts channel | Neither an AI alerts channel nor a logs channel is set, or the bot cannot post there | Choose one under General → Where the bot posts, and give the bot View Channel and Send Messages in it |
| A rule matches but the ticket stays in place | The target category is full (50 channels) or the bot lacks Manage Channels on it | Create a second category or clean up closed tickets, and fix the category permissions |
Common questions
Which plan do I need? Enterprise. Pro sees a locked card with an Enterprise badge.
Does Atlas understand other languages? Yes. Write the rule in your language; Atlas applies it to tickets written in any language.
Can a rule send tickets to a person instead of a category? No. Rules move tickets between categories and ping a role. Use Staff who can see these tickets or category permissions to control which staff see them.
What if several rules match? Atlas checks the rules from top to bottom and uses the first one that fits. Put the most specific rules at the top with Move up.
Can I test my rules? Open a test ticket that describes the case and watch the 🤖 Ticket Auto-Routed card in your alerts channel. The AI Reasoning line tells you why the rule was chosen.
Does the member see that their ticket was moved? Yes. A short Ticket Routed notice is posted in the ticket (and, for ModMail, in their DMs). Change its wording on the Messages page.
Can a rule tag the tickets it moves? Yes. Add tags under Tags to add in the rule (up to 25, 50 characters each). They are added to the ticket when Atlas moves it to that rule's category, and you can filter by them on Tickets.
Does Sorting change priority? No. Priority is set separately by Automatic priority.
Set up auto-routing by topic, the short version
Join our Discord server for support
Was this page helpful?
Last updated on
Connect Claude Code or Codex
Connect Claude Code, Codex or another MCP-capable AI tool to your TicketCord tickets, knowledge base, bot messages and stats, with permissions and tools
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