ServiceDesk Plus Technician License Cost: What You Pay and How Many Licenses You Need

ManageEngine ServiceDesk Plus is licensed per technician, not per employee. The published cloud rates start at US$13 per technician per month for Standard, US$27 for Professional, and US$67 for Enterprise, and Standard is free for up to five technicians. There is no charge for the people raising tickets. That single fact decides most of the bill, because the number you are buying is the size of your service desk, and that number is usually softer than it looks.

ManageEngine puts it plainly in the pricing FAQ: you pay for the number of administrators and technicians, and there is no restriction on the number of IT end users. So a 40 person company and a 4,000 person company running the same eight technician desk pay the same. Everything below was checked against the ServiceDesk Plus pricing page on 10 September 2026. Vendors move prices, so confirm before you sign.

What a ServiceDesk Plus technician license actually costs

On-premises is not sold per seat at all. It is sold in bands of technicians and assets, billed annually, and the jumps between bands are large enough that sizing matters. Standard is free at 2 technicians with 250 assets and again at 5 technicians with 500 assets, then costs 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 across 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.

The band structure is the part that catches people. Going from 10 technicians to 11 on Professional on-premises does not add one technician of cost, it moves you into the 20 technician band and roughly doubles the line. If you are close to a boundary, the question of whether a particular person truly needs a technician license is worth several thousand dollars a year rather than a few hundred.

Who actually needs a technician license

This is where most quotes are wrong in the customer's favor, and where a little discipline pays. A technician license is for someone who works tickets or administers the system. It is not for someone who reads them, approves them, or is merely mentioned on them.

Four roles get counted by default and should be checked one at a time:

• Administrators. These do consume a license. ManageEngine counts administrators and technicians together, so the two people who configure the instance are part of the bill even if they never resolve a ticket.
• Approvers. Line managers who approve service requests are usually end users, not technicians, and end users are unlimited. If approvers have been given technician logins for convenience, that is paid convenience.
• Read-only stakeholders. A service delivery manager who wants dashboards does not necessarily need a technician seat. Check what your reporting can be shared as before buying seats for visibility.
• Occasional second-line staff. The infrastructure engineer who touches four tickets a quarter is the genuinely hard case, and the honest answer depends on whether tickets are assigned to them or merely discussed with them.

Run that list before requesting a quote. On a 25 person desk it commonly removes three to five seats, and if it drops you under a band boundary on-premises the saving is disproportionate.

The add-ons that are not per technician

Not every line on a ServiceDesk Plus quote scales the way the base license does, and assuming it does leads to unpleasant surprises at renewal. The Custom Functions add-on is banded rather than per seat. ManageEngine works the example on their own pricing page: at 25 technicians the add-on comes to US$3,195 per year, and that figure covers any team size between 21 and 100 technicians. So a desk of 25 and a desk of 95 pay the same for it, which means the add-on gets cheaper per head as you grow and brutally expensive per head if you buy it at 22 technicians.

Annual maintenance service is the opposite shape. It is priced at US$35 per technician annually, or US$3.50 monthly, and it applies only to the free edition of up to five technicians. Service catalog, change and release management, project management, problem management, and CMDB are add-ons on Standard and Professional but come out of the box on Enterprise, which is often what actually justifies the Enterprise rate rather than any single headline feature.

Does routing require a more expensive edition?

No, and this is worth stating clearly because it is a common upsell. The ManageEngine cloud edition comparison lists Business Rules and Technician Auto Assign, with round robin, load balancing, and Zia, across Standard, Professional, and Enterprise alike. Automated assignment is not a premium capability in ServiceDesk Plus. If a reseller quotes you Enterprise on the grounds that you need automated ticket distribution, ask them to point at the row in the comparison chart.

What you should check instead is whether the built-in methods measure what you think they measure. Round robin is documented as assigning technicians to requests irrespective of the load, so it distributes ticket counts rather than effort. Load balancing does read workload, but with a narrow definition: the number of requests that are In Progress and assigned to a technician is taken as their load. Tickets sitting in Open or On Hold contribute nothing, so a technician with a large stalled backlog reads as idle and keeps receiving work. The mechanics of both, and the scope setting that makes auto assign silently override your business rules, are covered in detail on our ServiceDesk Plus technician auto assign page.

How to size the number of licenses you need

Three numbers, all available from reports you already have, will size a desk more accurately than a headcount conversation.

Tickets closed per technician per month, over the last two quarters. This gives you a real throughput figure for your environment rather than an industry benchmark that assumes a different ticket mix. Divide projected volume by it. If the answer is meaningfully below your current seat count, you are buying licenses for organizational structure rather than for work.

The share of tickets that are duplicates of a single underlying incident. On most desks this is larger than anyone expects, because one outage produces one ticket per affected person. Teams that put proper uptime monitoring on their sites, APIs and ports in front of the service desk tend to find that a visible portion of monthly volume was the same event reported thirty times, which changes the throughput math before any license is bought.

Your distance from the next band, if you are on-premises. At 18 technicians you are paying the 20 band. At 21 you are paying the 50 band. Knowing where you sit turns a vague headcount plan into a specific budget decision, and it is the one place where deferring a hire for a quarter has a directly quantifiable saving.

When more licenses is the wrong purchase

The reason a desk feels understaffed is not always that it is understaffed. Before adding seats, look at whether the work is landing evenly on the ones you have. Pull closed requests per technician inside a single group for the last quarter, comparing like with like rather than across teams that handle different work. A spread inside roughly twenty percent means distribution is healthy and the shortfall is real. One person closing double another inside the same group means you are running a desk where some capacity is already idle, and buying more of it will not help.

That imbalance is common and it usually has a mechanical cause rather than a motivational one: cherry picking from a shared unassigned view, a business rule sending an entire category to one named person, or load balancing measuring a status your team does not maintain. Each of those is fixable without spending anything. The comparison of every mechanism ServiceDesk Plus offers, and which one overrides which, sits on our ServiceDesk Plus auto assign page, and the vendor-neutral version of the same problem is on support ticket routing. If you are also weighing the platform decision itself, Freshservice ticket assignment and Jira Service Management queues are the two products most often shortlisted against ServiceDesk Plus at this size.

Frequently asked questions

Is ServiceDesk Plus priced per user or per technician? Per technician. 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. The employees raising tickets are free, which is why company headcount is close to irrelevant to the quote.

Is there a free version of ServiceDesk Plus? Yes. The Standard edition is free for up to five technicians, and on-premises it is listed as free at both the 2 technician with 250 assets band and the 5 technician with 500 assets band. Business rules and technician auto assign are included, so a small desk can run automated ticket distribution at no license cost.

How much does ServiceDesk Plus cost for 50 technicians? On-premises, the published annual figures at the 50 technician band are US$4,795 for Standard, US$10,795 for Professional, and US$21,595 for Enterprise. On cloud, apply the per technician rate to your seat count and confirm with a quote, since the published rates are starting prices and the pricing page routes larger deals through sales.

Do I need Enterprise to get automated ticket assignment? No. Business Rules and Technician Auto Assign with round robin, load balancing, and Zia are listed in all three editions. Enterprise adds change, projects, CMDB out of the box, and on cloud the Schedules and Custom Actions features, none of which are the assignment engine.

Can I reduce the number of technician licenses I pay for? Often, yes. Audit who genuinely works or administers tickets versus who approves, reads, or is merely copied. Approvers and stakeholders are usually end users, and end users are unlimited. Administrators, however, do count toward the technician total.

Where a routing layer fits

Assigner sits beside ServiceDesk Plus rather than replacing it, and it exists for the cases the built-in methods do not cover: weighting technicians differently instead of equally, routing on live availability rather than a static list, applying one set of rules to work that lives outside the service desk as well as inside it, and being able to explain to a manager exactly why a given ticket went to a given person. Pricing is $12 per user per month billed yearly, or $15 per month billed monthly. It is a companion, not a replacement, and not a live two-way sync. If your ServiceDesk Plus distribution is already even and your statuses are clean, you do not need it, and that is a fine answer.