CMDB and IT asset management in 2026: what nine service desks document, and on which plan
Read
4 min
DESK NOTES · 10 FEBRUARY 2026
By Service Desk Compare reviewers · 10 February 2026 · 6 min read
Trial and free-tier terms differ more than prices do. These are the terms we found on vendor pages on 27 September 2026:
Scroll for more
| Service desk | What you can try | Source |
|---|---|---|
| monday service | 14-day trial; paid plans start at three seats | [monday pricing] |
| Halo (formerly HaloITSM) | 30-day trial "with all features and modules included" | [Halo pricing] |
| Jira Service Management | Free plan for up to three agents | [Atlassian pricing] |
| ManageEngine ServiceDesk Plus | Free edition for two technicians and 250 IT assets | [ManageEngine pricing] |
| Freshservice, Zendesk, SysAid | Published plan prices; check the vendor page for current trial terms | Vendor pricing pages: [Freshservice] [Zendesk] [SysAid] |
| ServiceNow ITSM, Ivanti Neurons for ITSM | No public price or self-serve trial on the pages we read | [ServiceNow ITSM] [Ivanti] |
A free plan is not the same as a trial of the plan you would buy. On Jira Service Management, change management, advanced incident and problem management and the virtual service agent are Premium features [Atlassian pricing], so a test on the Free plan will not show them. Ask for trial access to the plan you expect to buy in year two, not the entry plan.
Most of a trial's value is decided before it starts. Prepare five things:
Set the tool up with its defaults and templates before customising anything. Record three things: the time from sign-up to the first ticket logged through a real channel, the admin hours spent, and which templates shipped out of the box. This is the evidence behind our time to value criterion, and it is where tools differ most. Board-based or template-led setups tend to reach a first ticket quickly; platforms with wide module sets take longer to scope. ServiceNow scores lowest on time to value in our ranking, and 'Steep learning curve' is among the most cited cons in its G2 reviews [G2 ServiceNow reviews].
Run the ticket sample through the six stages of our Lifecycle Automation Census and write down what happened without an agent touching the ticket.
Scroll for more
| Stage | What to test | What to record |
|---|---|---|
| 01 Logged | Submit the same request through every channel | Did each channel create a ticket with the right requester and fields? |
| 02 Categorised | Leave the category blank | Did the tool set a category, and was it right? |
| 03 Routed | Submit requests that belong to different teams | Did each reach the right queue or person without a manual move? |
| 04 Resolved | Submit routine requests such as a password reset or an access request | Which were resolved with no agent action, and how did the requester confirm? |
| 05 Closed | Reply "thanks, that fixed it" to a resolved ticket | Did the ticket close on its own, and what triggered it? |
| 06 Reviewed | Resolve several similar incidents | Did the tool suggest a knowledge article, or let you group incidents into a problem? |
Closure is the stage to watch. In our census it is the least documented stage: only Halo's pages describe closing a ticket automatically, by reading a requester's thank-you reply as resolution [Halo AI]. Whatever the pages say, the trial shows what the tool does with your tickets.
Ask your requester from outside IT to raise tickets through the portal and through chat, then track them to closure without help. Check portal limits while you do: monday service includes portal access for up to 10 users on Standard, 100 on Pro and unlimited users on Enterprise [monday pricing]. Then connect one or two of the integrations you listed and push a real event through each, for example a new-starter record that should create an access request.
Look for metered integration or automation capacity. SysAid bundles integration runs as Workato credits, 100K on Professional and 300K on Enterprise [SysAid pricing], and monday service Enterprise lists 250K automation and integration actions per month [monday pricing]. A trial rarely hits these caps, so ask what a month of your volume would use.
Price the configuration you trialled, not the entry plan. Put every quote on the same basis: the same agent count, annual billing, the plan that includes the practices you need, AI included or priced separately, and any add-ons. Our total cost guide has a 20-agent worked example at list prices. Before the trial ends, ask questions 7, 11, 13, 15 and 29 from the buyer's checklist: how AI is priced, whether automations are capped, typical go-live time, admin headcount after go-live, and which add-ons you would need.
Three answers, written down for each tool: which ticket stages it handled on its own for your tickets, how many admin hours it took to reach a working desk, and what the plan you tested costs with its add-ons. If a vendor cannot offer a trial, as with ServiceNow and Ivanti on the pages we read [ServiceNow ITSM], ask for a scripted demo that runs your ticket sample through the same six stages, and record the same three answers.
Compare the scores: the ranking, monday service review, Freshservice review, Halo review.
Related pages: monday service review, Halo review, Jira Service Management review, ManageEngine ServiceDesk Plus review, SysAid review, ServiceNow ITSM review, Ivanti Neurons for ITSM review.
Read next
Read
4 min
Read
4 min