Ticket Workflow Automation
The automation rule was simple: any ticket containing the word "urgent" is set to Urgent. It was written in a quiet week and it worked perfectly, in the sense that it did exactly what it said. Within a month every ticket arrived with "urgent" in the subject line. The users had worked out the rule faster than the desk had written it, and the priority field meant nothing at all. The rule was switched off, quietly, and the desk went back to reading tickets. Automation is wonderful for the parts of the work that are shaped like rules. It is a disaster for the parts that are shaped like judgement, and it does not know which is which.
This series is about knowing which is which. It covers what to automate first and what never, with the ladder from acknowledgments to routing to timers. It covers auto-routing rules that do not misfire, tested on real tickets before anyone trusts them. It covers auto-categorization and its limits, which are considerable. Then come SLA timers and escalation triggers that warn a person rather than a channel. It covers approvals without a workflow engine, because most small-team tools do not have one and do not need one. And it covers automating without losing judgment, with the monthly audit that catches the rule that has started filing everything as Other. Automate the acknowledgment. Read the ticket.
Articles in This Series
- What to Automate First, and What Never to Automate
The repetitive and rule-shaped first, never a judgement call, the automation ladder from acknowledgment to routing to timers to remediation, and the candidate list. - Auto-Routing Rules That Do Not Misfire on Real Tickets
Routing by mailbox, by form, by requester domain, by keyword; the default department as the safety net; testing a rule on ten real tickets; and the routing rule register. - Auto-Categorization and the Limits of Keyword Rules
Keyword rules, the misfile cost, why categorize-at-close is still needed, the rule that quietly files everything as Other, and the keyword rule table. - SLA Timers and Escalation Triggers That Warn a Person
Targets per priority, the warning before the breach, what an automatic escalation should and should not do, breach notifications to a person, and the timer and trigger table. - Approvals Without a Workflow Engine or an Approval Step
Approval captured by the approver's reply, the approver list by request type, linked tickets, what to do when the tool has no approval step, and the approval convention. - Automating the Desk Without Losing Your Judgment
The human checkpoints, the monthly audit of what the automation did, the misfire log, switching a rule off without shame, and the automation review sheet.
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.