Choosing a Ticketing System
The demo was excellent. Forty minutes, a confident presenter, a dashboard with a weather map on it, and a workflow builder that drew boxes and arrows while everyone nodded. By the end the desk wanted the workflow builder, the weather map and a thing called sentiment scoring. None of those had been on the list that morning, because there had been no list that morning. Six weeks later the contract was signed and the desk discovered that e-mail replies did not thread into tickets. That was the one thing it had done four hundred times a week on the old system. Nobody had asked, because the demo had not shown it. And the demo had not shown it because the presenter chose what to show.
This series is about choosing with a list in your hand. It covers writing the requirements before you watch a demo, from the queue rather than the brochure. It covers evaluation criteria that actually matter, and the ones that merely sound as if they do. It covers designing a fair trial with real tickets and five scenarios every candidate must survive. Then come hosting and licensing models in plain words, including what each costs in control as well as money. It covers migration cost as part of the decision rather than a surprise after it. And it covers making the decision and writing it down, so the person who asks why in two years gets an answer. A ticketing system is a ten-year relationship entered into after a forty-minute date. Bring questions.
Articles in This Series
- Write the Requirements Before You Watch a Demo
The must, should and nice list drawn from the queue, and the ten questions to answer before any vendor call. Also covers why a demo rewrites your requirements if you let it, and the requirements worksheet. - Evaluation Criteria That Actually Matter
Channels into one queue, routing, service levels, knowledge base, reports, permissions, integration, hosting, licensing model and the exit. Also covers scoring without theatre, the criteria that only sound important, and the scoring sheet. - Designing a Fair Trial: Real Tickets, Two Weeks, Five Scenarios
Real tickets, two weeks, the whole team, five scenarios every candidate must survive, exit criteria written before day one, and the trial plan. - Hosting and Licensing Models in Plain Words
Cloud versus self-hosted, and per agent per month versus per installation. Covers what each costs in control, data location and money over years, and a total-cost worksheet in categories and hours. - Cloud-Based Help Desk Software vs Self-Hosted: What You Are Actually Choosing
What cloud-based, web-based and online mean, what you buy and give up with each, the rented-server hybrid, who should choose which, the seven brochure claims decoded, and the hosting decision sheet. - Migration Cost Is Part of the Decision, Not a Footnote
History, categories, retraining, templates and knowledge rebuilt, the double-running period, the cost that never appears in the quote, and the migration cost sheet. - Making the Decision and Writing It Down: The Decision Record
What was chosen, why, what was rejected, who signed, what will be revisited and when, the exit plan, and the one-page decision record.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.