Every office already runs a helpdesk. It is called WhatsApp, phone calls, and someone walking up to the IT desk saying the printer is not working again. ServiceDesk Plus replaces that chaos with one queue where every request is logged, assigned, timed and answered.
ServiceDesk Plus is ManageEngine's IT service management platform. At its centre sits one simple idea: every request becomes a ticket. A ticket has a requester, a technician who owns it, a priority, a category and an SLA clock that measures how fast you respond and resolve. Around that centre, the product adds a self-service portal for staff, a knowledge base for repeated questions, and - in the higher editions - asset management, problem and change management, a service catalog and a CMDB. It runs in the cloud or on your own server, with the same three editions on both sides. This guide walks the setup in the order that avoids rework, and it stays honest about the one thing no software can do for you: a helpdesk only works if people actually use it.
Two decisions come before any installation, because changing them later means migration work. Home: the cloud version runs on ManageEngine's own servers - no server to maintain, updates arrive on their own, and staff can raise tickets from anywhere. The on-premises version installs on your Windows server inside your network, so ticket data never leaves the building and the desk keeps working on the LAN even if the internet is down. Edition: Standard is the help desk itself - incidents, portal, knowledge base, SLA and reports - and it is free for up to five technicians. Professional adds IT asset management, purchase orders and contracts. Enterprise adds problem, change and release management, the service catalog, IT projects and the CMDB. Licences are counted per technician; the staff who raise tickets, the requesters, are unlimited and free. Pick the edition for the process you will actually run this quarter, not the one you might run someday - upgrading later keeps your data.
On-premises, the installer sets up the application with its bundled database on your server; in the cloud you simply sign up, name your organisation and choose your data region. Either way, the first hour of configuration decides whether day one feels smooth or broken:
Now create the skeleton. Add your technicians and give each one a role - an administrator who can change settings, and technicians who work tickets. Group them the way work actually arrives: a hardware group, a network group, a software and accounts group. Then build a short category tree: Category, Sub Category and Item, in words your staff use, not words IT wishes they used. "Internet not working" will get picked; "Layer 3 connectivity incident" will not. Fifteen honest categories beat a hundred clever ones, because every report you ever show management is grouped by these words. Finally, create request templates for the five things people ask for most - new user account, password reset, software install, printer problem, VPN access - with exactly the fields a technician needs to start work without a follow-up call.
The last setup step is the promise and the door. Define SLA policies per priority: how fast a technician must first respond, and how fast the ticket should be resolved, with escalation levels that notify the group lead and then the manager as a breach approaches. Keep the numbers close to what your team already achieves on a normal week - the deep dive on honest SLA targets has its own guide in this series. Then open the self-service portal: this is the only screen most of your staff will ever see, so it decides whether the system lives. A big new-request button, the templates from step 3, a knowledge base seeded with your ten most repeated answers, and a "my requests" view where people can watch their ticket move. Announce it in a team meeting, keep email-to-ticket switched on during the transition, and for the first month, log walk-in requests into the portal yourself while the person watches. Habits change when people see their ticket get a number, an owner and a reply.
Go live with one department and real tickets, not the whole company and not demo data. Real tickets expose the missing category, the wrong template field and the SLA that was set in fantasy - within a week, while fixing them is still cheap. And one connection worth knowing about from day one: ServiceDesk Plus integrates natively with Endpoint Central, ManageEngine's endpoint management platform, so the computer behind a ticket can be identified and reached from the ticket itself. You do not need it to start. But if your office already runs Endpoint Central, link the two early - it removes the oldest question in support, "which PC is it?", from every conversation.
The full walkthrough - setup screens, ticket flow and the settings that matter - is shown live in the video.
Watch Full VideoThe Standard edition is free for up to five technicians, and it is a real help desk - incidents, self-service portal, knowledge base, SLA and reports. Paid editions and add-ons start when you need asset management (Professional) or problem, change and CMDB (Enterprise). ManageEngine also offers a 30-day free trial, which is the right way to test a paid edition.
Pick cloud if you have no spare server and want updates handled for you - your data then lives in ManageEngine's own data centres. Pick on-premises if ticket data must stay inside your building, or if the desk must keep working on the LAN when the internet is down. The editions and the core help desk are the same on both sides.
No. Licensing is counted per technician - the people who work the tickets. Requesters, the staff who raise tickets through the portal, email or the mobile app, are unlimited and do not consume licences. On the Professional and Enterprise editions, the IT assets you manage are counted as well.