ServiceDesk Plus Auto Assign Technician: Technician Auto Assign, Auto Assign Group, and Business Rules in ManageEngine

Why technician auto assign resets the technician your business rule just set

This is the single most expensive misconfiguration in ServiceDesk Plus routing, and it comes from a dropdown with two options. In the auto assign configuration you choose whether the rule applies to Unassigned Requests or to All Requests.

ManageEngine documents the difference without ambiguity. With All Requests selected, tech auto assign takes precedence, and in their words, even if the Business rule sets a technician, tech auto-assign will reset the technician value. With Unassigned Requests selected the order reverses: the business rule applies first, and Technician Auto-assign will get applied after the Business rule, filling in only the requests that came through with no technician on them.

The failure mode is nasty because nothing errors. Your business rules still evaluate, still match, still write a technician to the request. Auto assign then overwrites that value a moment later. What the service desk manager sees is round robin distribution and a set of business rules that appear to have stopped working, so the investigation starts in the wrong place and can run for weeks. If you have business rules doing any meaningful routing, Unassigned Requests is almost always the setting you want, with auto assign acting as the safety net for whatever the rules did not catch.

Round robin versus load balancing, and what ServiceDesk Plus counts as load

ServiceDesk Plus ships two deterministic methods plus Zia, and the difference between the first two is entirely about whether current workload is consulted.

Round robin is defined in the admin guide as assignment where technicians are assigned to the request irrespective of the load. Tickets go out equally and in order, the list restarts at the top, and nobody is skipped for being busy. It is predictable and easy to explain, which is why most teams start here.

Load balancing consults workload, but only one narrow measure of it. The guide is specific: the number of requests that are In Progress and assigned to a technician is taken as the load of the technician. Read that sentence carefully, because it is the whole story. Requests in Open, On Hold, or any status that is not In Progress do not count. A technician holding twenty-five On Hold tickets waiting on vendors, plus eight Open tickets they have not started, has a measured load of zero and will be first in line for the next request. Meanwhile a technician working properly, who moves tickets to In Progress as they touch them, is penalized for the discipline.

That is why load balancing sometimes appears to make distribution worse rather than better. It is not broken. It is measuring exactly what it says it measures, and status hygiene in your instance is what decides whether that measure means anything. Before you trust load balancing, check how many of your open tickets are actually sitting in the In Progress status. If the answer is a minority, load balancing is close to random.

Auto assign group versus auto assign technician

These are two different problems and ServiceDesk Plus solves them in two different places, which is why searching for one often turns up the other.

Choosing the group is classification work: which team owns this request. That is a business rules job, driven by category, requester department, site, or the mailbox the ticket arrived on. Technician auto assign does not classify. It has no opinion about which team should own a network fault.

Choosing the technician is distribution work: given that the request already belongs to a team, who on that team takes it. That is what auto assign does, and it respects scope. ManageEngine notes that for site specific requests, the technicians associated with the sites are auto-assigned, and the same applies to group associations, so a technician is not handed work from a site or group they do not belong to.

The practical sequence for most instances is therefore: business rules pick the group, auto assign set to Unassigned Requests picks the person inside it. Trying to do both jobs with one mechanism is what produces either rigid per-category single points of failure or a round robin that scatters specialist work across the whole desk.

What ServiceDesk Plus costs, and which edition you actually need for routing

The routing answer is the useful one first: you do not need to upgrade for assignment. The ManageEngine cloud comparison chart lists Business Rules and Technician Auto Assign with round robin, load balancing, and Zia across all three editions, Standard, Professional, and Enterprise. What the higher tiers add is asset management, change, projects, and, on cloud, Schedules and Custom Actions. If someone tells you fair distribution requires Enterprise, that is not what the comparison chart says.

List prices published on the ManageEngine ServiceDesk Plus pricing page, checked 10 September 2026:

On-premises is sold in bands of technicians and assets rather than per seat. The same page lists Standard as free at 2 technicians with 250 assets and at 5 technicians with 500 assets, then US$1,195 per year at 10 technicians, US$2,395 at 20, US$4,795 at 50, US$8,395 at 100, and US$11,995 at 200. Professional at the same bands runs US$495, US$1,195, US$2,295, US$4,545, US$10,795, US$19,195, and US$23,995. Enterprise runs US$1,195, US$2,995, US$5,995, US$10,795, US$21,595, US$29,995, and US$35,995.

Two licensing facts matter more than the headline rate. ManageEngine states that you pay for the number of administrators and technicians and that there is no restriction on the number of IT end users, so the cost driver is the size of your desk, not the size of your company. And the Custom Functions add-on is banded, not per seat: the pricing FAQ works an example where 25 technicians comes to US$3,195 per year, a figure that covers any team between 21 and 100 technicians. Prices change, so verify against the pricing page before you budget.

Why service requests sit unassigned while incidents route perfectly

This is the second support call ManageEngine fields on this feature, and it has a one-line cause. There is a setting named Do not assign technician before service request is approved. When it is disabled, technician auto assign applies to a service request as soon as it is created or edited, the same as an incident. When it is enabled, auto assign is held back and applied only after the service request has been approved.

That behavior is usually correct, and most organizations want it, because assigning fulfilment work before anybody has agreed to fund it wastes technician time. The problem is that the resulting queue looks identical to a broken routing rule. Service requests appear in the unassigned view, they age, they trip SLA warnings, and nobody looking at the auto assign configuration can see anything wrong with it, because there is nothing wrong with it.

The distinction worth internalizing is ManageEngine own definition: unassigned requests are the ones not assigned to technicians even after the application of business rules, category or default technician from the UI. If a request is unassigned, all three of those have already had their turn. So when you are debugging, work backwards through that list rather than staring at the auto assign screen, and check the approval setting before anything else.

The two numbers to pull before you buy anything

Before adding a routing product on top of ServiceDesk Plus, or moving editions, pull two figures out of the instance you already have. Both are available in the standard reports and both settle arguments quickly.

One: closed requests per technician within a single group, for the last quarter. Not across the whole desk, which mixes teams doing different work, but inside one group where the tickets are comparable. If the spread between the busiest and the quietest technician is inside roughly twenty percent, your distribution is fine and your problem is somewhere else, probably capacity or categorization. If one person is closing double another, you have a real distribution problem and it is worth solving.

Two: the share of your currently open tickets that sit in the In Progress status. This decides whether load balancing can help you at all. Because ServiceDesk Plus counts only In Progress requests as load, an instance where most active work sits in Open or On Hold gives load balancing almost nothing to work with, and switching to it will feel arbitrary. Fixing status discipline is free and may be the entire fix.

If both numbers come back healthy, buy nothing. If the spread is wide and your statuses are clean, the built-in methods are probably enough and you should change the scope setting rather than the software. The case for a routing layer beside ServiceDesk Plus starts where the built-in methods stop: when you need to weight people differently rather than equally, when routing has to consider live availability rather than a static list, when the same rules must cover work that lives outside ServiceDesk Plus as well as inside it, and when somebody senior needs an explanation of why a specific ticket went to a specific person.

How do I auto assign tickets to technicians in ServiceDesk Plus?

Open the admin configurations, find Technician Auto Assign, and enable it for the group or site you want covered. Choose an assignment method of round robin, load balancing, or Zia, then choose the scope: Unassigned Requests, which runs after your business rules, or All Requests, which overrides them. Set whether it triggers on created requests, edited requests, or both, and save. The feature is available in Standard, Professional, and Enterprise.

What is the difference between round robin and load balancing in ServiceDesk Plus?

Round robin assigns technicians to requests irrespective of the load, distributing tickets equally and in order, then restarting the list. Load balancing consults workload, but it defines load narrowly: the number of requests that are In Progress and assigned to a technician. Requests in Open or On Hold do not count toward load, so load balancing is only meaningful if your desk keeps the In Progress status current.

Why is technician auto assign overriding my business rules?

Because auto assign is set to All Requests. In that mode ManageEngine documents that even if the business rule sets a technician, tech auto-assign will reset the technician value. Change the scope to Unassigned Requests and the order reverses, so business rules apply first and auto assign only fills requests that arrived with no technician on them.

Does ServiceDesk Plus technician auto assign work on service requests?

Yes, but timing depends on one setting. If Do not assign technician before service request is approved is disabled, auto assign applies when the service request is created or edited. If it is enabled, auto assign is applied only after the service request has been approved, which is why service requests can look stuck in the unassigned view while incidents route normally.

Can ServiceDesk Plus auto assign a group instead of a technician?

Group selection is a business rules job, not an auto assign job. Business rules match on criteria such as category, requester department, site, or the mailbox the request arrived on, and set the support group. Technician auto assign then picks the person within that scope. ManageEngine notes that for site specific requests, the technicians associated with the sites are auto-assigned, and group associations behave the same way.

Which ServiceDesk Plus edition includes technician auto assign?

All of them. The ManageEngine cloud edition comparison lists Business Rules and Technician Auto Assign with round robin, load balancing, and Zia in Standard, Professional, and Enterprise. Standard is free for up to five technicians. Higher editions add asset management, change, projects, and, on cloud, Schedules and Custom Actions, but not the assignment engine itself.

How much does ManageEngine ServiceDesk Plus cost per technician?

The published pricing page, checked in September 2026, lists Standard from US$13 per technician per month, Professional from US$27, and Enterprise from US$67, with Standard free for up to five technicians. On-premises is sold in technician and asset bands instead, starting at US$495 per year for Professional at two technicians. You pay for administrators and technicians only, with no restriction on the number of end users.

Can I exclude certain technicians from auto assign?

Yes. The configuration has an include or exclude toggle where you name individual technicians, so a team lead, an on-call engineer, or a part-time contractor can be kept out of the rotation without removing them from the group. There is also a rules toggle that includes or excludes specific requests using multiple criteria joined with and or or logic.

Does auto assign only give tickets to technicians who are logged in?

Only if you tell it to. The configuration includes an option to assign only to online technicians. With it off, requests are distributed across the full eligible list regardless of whether anyone is signed in, which is how tickets end up assigned to somebody on annual leave. With it on, distribution narrows to whoever is currently online.

Will auto assign reassign a ticket that already has a technician?

Not during an edit. ManageEngine documents that when auto assign runs on edit it does not override an existing technician assignment. The one case where existing assignments are replaced is the All Requests scope on creation, where auto assign resets a technician set by a business rule or category. Deliberate reassignment stays a manual action.

Why is load balancing still giving work to my busiest technician?

Almost always a status problem rather than a routing problem. Load balancing counts only requests that are In Progress and assigned to that technician. If your busiest person has thirty tickets sitting in Open or On Hold, their measured load is zero and they will keep receiving new work. Check what share of your open tickets carry the In Progress status before concluding the feature is faulty.

What does ServiceDesk Plus auto assign not do?

It does not weight technicians differently, so a senior engineer and a first week starter are treated as equal recipients. It does not read skills, so specialist work is distributed as readily as password resets. It does not consider effort, only counts or In Progress totals. And it stops at the boundary of ServiceDesk Plus, so work that lives in other systems needs its own separate rules.