Create Accountor Login
Docs

Assignment Rules

Part of the MountDev Ops Helpdesk documentation. Updated November 16, 2026

MountDev Ops Helpdesk documentation | Updated November 16, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 5,581 automated checks before it ships, and every screen change is walked through before release.

What a Rule Does

A rule belongs to a team and says how a new ticket is given out. There are three ways, each your company's own setting:

  • Everyone Hears About It is the start for every team, and it is how Helpdesk worked before: the team hears about each ticket. Nothing changes until you set another rule.
  • Round Robin gives each new ticket to the next person on the team, one at a time, then starts again at the top.
  • Fewest Open Tickets gives each new ticket to whoever has the fewest open tickets now. The earliest turn wins a tie. An open ticket is one in the Inbox's Open tab: not Closed, not Waiting on Customer, and not spam.

A team's people are the people in it and in the teams inside it. A leader takes tickets only by being in the team. Nobody is ever added to or removed from a team by assigning.

Who Counts

Two switches, both on at the start of any rule:

  • Only People Who Are Working Now: nobody counts while the company is outside its Business Hours.
  • Skip People Who Are Away: anyone marked Away is skipped (Available or Away).

An AI assistant, someone with no access to Helpdesk, someone who cannot see the ticket, and (for an address for owners and admins only) anyone who is not an owner or admin is never picked.

When Nobody Is Available

You choose what happens: Keep It With the Team (the start: it stays assigned to the team and everyone hears about it), Leave It Unassigned, or Give It to One Person (a named person on the team, checked again when it is used; if they have left, it falls back to Keep It With the Team).

Where a Rule Applies

In order: an address's own New Tickets Go To (a person means no rule; a team means that team's rule), otherwise the rule of the address's department, otherwise nobody, as before. It runs when a ticket arrives and when someone, a Workflow, or an AI assistant asks for it (action helpdesk.ticket.assign_by_rule). It never takes a ticket from a person on its own.

Set Rule

Owners and admins open Set Rule on a department on the Departments page (action helpdesk.assign_rules.save). Each department shows its rule in one line, such as "Round robin | Working now only | Skips people who are away | If nobody: stays with the team". Set Rule is a pop up in three steps (one if Everyone Hears About It is chosen): How to Pick Someone, Who Counts (the team's people, each with their open tickets and whether they Count or are Skipped; action helpdesk.assign_rules.preview), and If Nobody Is Available, which says who the next ticket would go to right now. Every step ends with In Plain Words, a sentence that matches the saved rule.

What the Person Sees

The person a rule picks gets one notice in the bell and Helpdesk's notifications: "T-1040 Printer will not connect was assigned to you. Support's round robin picked you." Their row in the Inbox says "Assigned to you | Support's round robin". They are never told about something they did themselves, and a person who is Away is never picked.

Moving a Ticket into a Department

Moving a ticket into a department that has a rule (Departments, Move to Department) gives it to whoever the rule picks when nobody has it, or when you choose Assign by the department's rule. It never takes a ticket from a person on its own. If the rule leaves a new ticket unassigned (Leave It Unassigned), the team's leaders are told.

Pass It On

Pass It On is on a ticket you have: it gives the ticket to the next person by the department's rule, skipping you (action helpdesk.ticket.pass_on). Only the person who has the ticket and managers can use it, and the person who had it is told once, in a line. To pick a person yourself or give the ticket to a team, use Assigned to on the ticket (Assigning Tickets).

Workflows and AI Assistants

helpdesk.assign_rules.list (read) gives each team's rule in words. helpdesk.ticket.assign_by_rule (write) gives a ticket that has nobody to whoever the rule picks; it cannot name a person. Creating or changing a rule, and adding or removing people on a team, are a person's steps on the screen, never for a Workflow, an AI assistant, or a key.

Ask Us Anything

We’d love to hear from you!