Cherwell Ticketing System: A Beginner's Guide

|

12 Mins

|

Last updated:

|

Last updated:

Share this article

TL;DR

  • The Cherwell ticketing system is Cherwell Service Management (CSM), owned by Ivanti since 2021. Technicians are Users, employees are Customers, and every ticket is an incident or a service request.

  • Tickets move through seven statuses. Pending can pause the SLA clock, and the out-of-the-box automation closes a Resolved ticket after three days.

  • Most of the daily work happens through One-Step Actions, the buttons that change status, assign owners and close records for you.

  • Per Ivanti's end-of-life FAQ, CSM reaches end of life on December 31, 2026, and cloud tenants become inaccessible 30 days later. Anything you build now has to survive a migration.

The Cherwell ticketing system has less than two months of vendor support left. Ivanti has set December 31, 2026, as the end of life for Cherwell Service Management, and plenty of IT teams will run their whole service desk on it right up to the switch. If you're learning it now, you're learning it on a deadline.

So this guide does two jobs. It explains how a Cherwell ticket works, for the analyst who inherited the queue last month. And it covers what the end of life means for whoever has to plan what comes next. Everything below was checked against Ivanti's CSM documentation on November 9, 2026. Cherwell is heavily customizable, so your admin's configuration will override the defaults described here; check your own instance before you rely on any of them.

What Is the Cherwell Ticketing System?

The Cherwell ticketing system is the incident and request engine inside Cherwell Service Management, an ITSM platform Ivanti acquired in 2021. It logs every employee issue as a record with a customer, an owner, a team, a status and a journal; that record then ties into a service catalog, a knowledge base and a CMDB.

The vocabulary is the first thing to get straight. In CSM a User is a technician who works tickets, and a Customer is the employee who raised one. Ivanti's incident workflow documentation also names the Requester (the person who initiates the ticket, typically a customer) and the Owner (the technician who investigates and resolves it), alongside the Creator and Task owner.

You'll meet CSM through several applications. Technicians work in the Desktop Client or the Browser Client, employees use the CSM Portal, and admins configure everything in CSM Administrator. Almost every form, field and rule in Cherwell is configurable, and you'd be surprised how little two Cherwell instances at two companies have in common.

Cherwell End of Life: What Happens After December 31, 2026?

Cherwell Service Management reaches end of life on December 31, 2026. After that date Ivanti stops supporting it, and its go-forward product for Cherwell customers is Ivanti Neurons for ITSM.

What happens next depends on how you run CSM, according to Ivanti's Cherwell End-of-Life FAQ as quoted by partner StrataCom, with matching answers on partner Service Quality's FAQ page:

Deployment

What happens after December 31, 2026

Cloud (hosted by Ivanti)

"Your tenant will be discontinued and will no longer be accessible 30 days following the end-of-life date."

On-premises, perpetual license

"The product will continue to run but Ivanti will no longer provide support after the end-of-life date."

New licenses

Allowed, provided the subscription or maintenance period doesn't extend beyond December 31, 2026.

One caveat on sourcing. Ivanti's public Cherwell refresh page only says CSM "may be nearing its end of life," and the end-of-life FAQ the partners quote sits on Ivanti's customer forums rather than in a public announcement. Get the dates for your own contract from your Ivanti account manager in writing.

If you're on the cloud version, your real deadline comes before the date in the FAQ; your data has to be exported before the tenant goes dark, and the export itself takes time. I believe the riskiest option is the one teams drift into without deciding: an on-premises instance still running in February because the migration slipped, with no vendor to call when something breaks. If you're already weighing the move, our roundup of Cherwell and Ivanti alternatives covers the wider market.

How Do You Log a Ticket in Cherwell?

Tickets come into Cherwell through the portal, email and technicians logging calls directly. The Incident form records which one in its Call Source field, with options like Phone, E-mail, Portal, Walk in, Chat Session, Mobile etc.

Here's how an employee logs an incident in the CSM Portal:

  • In the Service Catalog, select the tile for the team you need, such as IT Service Desk.

  • Pick the tile that fits the problem, then the link that submits a record (for example Report Outage or Error, then Submit Incident).

  • Fill in the form. To log it for a colleague, check Submit on behalf of another user.

  • Click Submit and note the Incident ID, then find the record later under My Items.

Email works through the Email and Event Monitor. It matches the sender against the email field on customer records, and if it can't find a match it attaches the ticket to a default customer record as a placeholder. Replies are matched to the existing incident by conversation ID, and an employee who puts "Reopen" in the subject line can reopen a resolved one.

That placeholder customer is the lost-and-found bin of your service desk. Tickets land there from anyone without a matching record, like a contractor or a new hire whose account hasn't synced yet. Their SLA clocks run the whole time, so ask your admin to put them on a view you check daily. Customer records usually arrive through a scheduled LDAP import, which Ivanti recommends running biweekly, so a new hire can go days without a customer record.

Chat takes more setup. Ivanti documents a Slack Integration mApp whose bot can create, check and close incidents (you install it through CSM Administrator, and Ivanti tested it on CSM 10.0 to 10.2). There's also a Teams chat feature that lets someone in CSM message a Teams channel from inside a record. Fuller Teams integrations come from partners such as StrataCom. Out of the box, the portal and email are the main ways employees reach the desk.

Which Is It: Incident or Service Request?

In Cherwell, an incident is something broken and a service request is something asked for. Ivanti's ITSM practices guide defines an incident as "an unplanned interruption to a service or a reduction in the quality of a service." A service request asks for information, advice, access or a standard change, like a password reset or printer access.

Classification runs on three tiers: Service, Category and Subcategory. The combination you pick tells Cherwell the record type, which form specifics appear, and which priority matrix and SLA apply. A wrong subcategory sends a ticket to the wrong queue with the wrong deadline, and every last Cherwell ticket goes through that field.

Set the Primary CI on every incident you can, too. That link to the CMDB is how someone spots the laptop model or server that keeps failing. The View Impacted CIs action opens a configuration map of the other CIs the incident affects, per Ivanti's incident logging guide.

Cherwell Ticket Statuses

A Cherwell incident moves through seven statuses, per the Incident form documentation:

Status

What it means

New

Being recorded, classified and assigned

Assigned

An owner has been set

In Progress

The owner is working on it

Pending

Paused, which stops the resolve clock if your SLA allows it

Resolved

Fixed, waiting to be closed

Closed

Done

Reopened

The fix didn't hold, or the issue came back

Two automations decide how long a ticket sits in some of those states. In Ivanti's out-of-the-box incident automation processes, "Resolve to Closed" closes a ticket that's still Resolved after three days. "Not Touched in 3 Days" emails the owner when a record has sat unmodified for three days. Your instance may have changed both.

That three-day window is what to explain to your team. The out-of-the-box Reopen action works on a Resolved incident, clears the resolution fields and restarts the SLA clock. You've probably seen the employee who replies "still broken" a week later; by then the ticket has closed, and whether that reply reopens anything depends on how your admin set up the email monitor.

How Do Priority and SLAs Work in Cherwell?

Cherwell sets priority from a matrix, not from a dropdown someone guesses at. "Priority is derived from an impact and urgency Priority Matrix," per Ivanti, where impact measures how many people are affected and urgency measures how long until the business feels it. Incidents and requests each get their own matrix.

Priority then sets the response and resolve deadlines through an SLA. The default Corporate SLA in Ivanti's ITSM practices guide looks like this:

Type

Priority

Respond within

Resolve within

Incidents (24x7)

1

1 hour

5 hours

Incidents (24x7)

3

2 hours

3 days

Incidents (24x7)

5

2 hours

9 days

Service Requests (8 to 5, Mon to Fri)

1

2 hours

2 days

Service Requests (8 to 5, Mon to Fri)

3

1 day

10 days

Those are Ivanti's starting values; check your own SLA records before you quote a deadline to anyone.

Three behaviors trip up new analysts. Your response time is recorded when you click Start Work In Progress, which moves the ticket to In Progress, and not when you send the first email. Set Pending uses Stop the Clock to pause the resolve timer, but only if the SLA has the "Allow 'Stop the Clock'" check box selected. And when a deadline gets close, the out-of-the-box warnings email the owner's manager, so a breach is never just your problem.

How to Work a Cherwell Ticket With One-Step Actions

One-Step Actions are Cherwell's buttons for routine work, each running a short sequence like changing a status and setting an owner. Say an employee emails that her VPN client won't connect after a password change. Here's how that ticket should go using the out-of-the-box incident One-Step Actions.

1. Take Ownership

Open the record from your team's queue and click Take Ownership. It makes you the owner and moves the ticket from New to Assigned. If it belongs to another team, use Assign to Team instead, and leave a journal note saying why.

2. Start Work In Progress

Click Start Work In Progress as soon as you start. It records the response time and sets the status to In Progress, and that click is what keeps your response SLA green.

3. Set Pending While You Wait

You ask her to sign out and back in with the new password. Click Set Pending so the resolve clock stops (if your SLA allows it) while the ticket waits on her, and use Remove Pending Status when she replies. Add a journal note saying what you asked her to try, because whoever picks the ticket up while you're out will need it.

4. Resolve With a Cause Code

When she confirms the VPN connects, click Resolve Incident. Cherwell prompts for a close description and cause code if they're empty, and it won't let you resolve while child tasks are still open. Write the description for the next analyst, because "Fixed" tells them nothing.

5. Nominate for KB If It Will Happen Again

If every password change breaks the VPN client, click Nominate for KB. It creates a draft knowledge article prefilled with the description and fix, and that article has its own review workflow before anyone else sees it.

For outages, there's one more action to know. Change to Major Incident turns an incident with company-wide impact into a major incident, and linked incidents close automatically when the major incident closes, per Ivanti's incident logging guide. Confirm every linked report is fixed before you close the major incident.

Cherwell Pricing: How Much Does It Cost in 2026?

Ivanti doesn't publish Cherwell pricing, and in 2026 the more useful question is how long you can pay for it at all. New subscriptions and maintenance can't run past December 31, 2026.

The licensing model still matters if you're auditing your last renewal. CSM uses concurrent licenses, a shared pool that caps how many people can be logged in at once. Under Ivanti's license consumption rules, a technician uses one license no matter how many clients they're signed into, and the REST API uses one too. Portal customers usually don't use one for their own records, though some edits do, so read those rules before you count seats for a final renewal.

Why Is Changing Cherwell So Hard?

Cherwell's flexibility comes from Blueprints and mApps. Blueprints are how admins change business objects, fields and forms in CSM Administrator, and mApps package that work to move between systems. That flexibility is also why a heavily customized instance gets hard to maintain.

Publishing a Blueprint has side effects worth knowing before you touch one. By default it locks the system so users can't log in (in Cherwell terms, that's every technician on your desk). It also pauses CSM's background services, like automation, email monitoring and scheduling, until they're restarted, per Ivanti. If two admins change the same object, the last Blueprint published can overwrite the other admin's work. Ivanti recommends publishing to a test system first and scheduling the live publish after hours, which is why a quick field change in Cherwell is never quick.

Cherwell Migration: What Should Teams Do Next?

You have three realistic paths:

  • Move to Ivanti Neurons for ITSM, which Ivanti offers as the replacement and says of its migration that "you're not going to lose any data" (Ivanti).

  • Move to another ITSM platform.

  • Keep an on-premises instance running without Ivanti support.

Partner Service Quality says customers may use both systems for a set period, such as six months, while they transition to Neurons.

What to Inventory Before You Migrate

Ask Ivanti or your partner now how and when you get your data. Service Quality's FAQ says that after the upgrade grace period, subscription customers have 30 days to request their data, which arrives "in a standard database export format." That's a file to archive or transform, not one to import. Then list what your instance actually runs: Blueprints and mApps, One-Step Actions, automation processes, email monitor rules, SLAs, LDAP imports, REST API integrations, reports, knowledge articles etc. Decide early whether you need closed-ticket history and attachments in the new tool or only in an archive you can search.

Whichever way you go, don't treat it as a copy job. A migration is your chance to drop the approval nobody needs and the subcategory nobody uses; our guide to what an ITSM migration should actually change covers what to keep and what to redesign. If you're comparing platforms, the same series covers Jira, ServiceNow, Freshservice and BMC Helix.

The test we'd use is the one we've used across this series: look at where your requests actually arrive. If it's mostly the portal and email, most ITSM platforms will feel familiar. If employees are already asking for help in Slack or Teams and someone is retyping those messages into Cherwell, that's the part of the job your next system should remove.

Ravenna: Ticketing That Starts in Slack and Teams

Ravenna runs ticketing inside Slack and Teams, so the conversation is where the ticket gets created (here's how that works in Slack). An employee asks in a channel, and our AI agents answer from your connected knowledge when the answer exists. When it doesn't, the request becomes a ticket for your team, kept in sync with the original thread. Employees don't have to leave Slack or Teams to get help (there's a portal for anyone who prefers one), and you still get the record, the owner and the ticket history.

The pieces a Cherwell team leans on are there too: forms with custom fields, workflows for approvals and routing, and SLAs with business hours and pause statuses. If you're comparing directly, our Ravenna vs Ivanti page puts the two side by side.

You have less than two months before the support ends, which is enough time to choose your next system deliberately even if the migration itself runs longer. If you want to see how your service desk would run in Slack or Teams, we're happy to walk you through it, or you can poke around the docs first.

Frequently Asked Questions

Is Cherwell a Ticketing System?

Yes. Cherwell Service Management includes a ticketing system for incidents and service requests, along with problem, change, asset and knowledge management. Ivanti has owned it since 2021.

Is Cherwell Being Discontinued?

Yes. Ivanti's end-of-life FAQ sets December 31, 2026, as the end of life for Cherwell Service Management. Cloud tenants become inaccessible 30 days after that date, and on-premises installs keep running without Ivanti support.

How Much Does Cherwell Cost?

Ivanti doesn't publish Cherwell pricing. CSM uses concurrent licensing, and new subscriptions or maintenance can't extend beyond December 31, 2026.

What Is the Best Cherwell Alternative?

Ivanti positions Ivanti Neurons for ITSM as the replacement for Cherwell customers. Teams also move to ServiceNow, Jira Service Management, Freshservice and Slack and Teams-native tools like Ravenna. The right choice depends on how much of your Cherwell customization you need to keep.

Cherwell vs ServiceNow: What's the Difference?

Both are full ITSM platforms with incident, request, problem and change management and a CMDB. ServiceNow is actively developed, and Cherwell reaches end of life on December 31, 2026, so for most teams the comparison is now about where to migrate rather than which to buy.

Modernize and automate your
service desk with Ravenna

Modernize and automate your
service desk with Ravenna