Where the help desk is heading
Drafts instead of blank pages, a quieter queue and every language on equal footing: an opinionated look at what the help desk becomes, and what it should never stop being.
The nabudesk team2 min read
Predictions about software are usually wrong in the details and right about the direction. So this is a direction, not a forecast. The help desk is moving from a place where tickets are stored to a place where work gets finished, with less typing, less sorting and fewer repeat questions.
Drafting becomes the default, judgement stays human
Writing a first reply from a whole conversation is something software can already do passably. We expect a draft to become the starting point of most replies, the way spell check became the starting point of every email. What will not move is the decision to send: the tone, the exception, and the moment a customer needs a person rather than a paragraph. The teams that do best will treat AI like a fast junior colleague: useful, tireless and always reviewed.
Fewer tickets, better ones
The best support interaction is the one that never has to happen, because the answer was found before the question was asked. As knowledge bases get easier to write, with drafts produced from solved tickets and approved by people, more of the routine volume will be absorbed before it arrives. What remains will be harder, more specific and more human. That changes what agents do all day, and it changes what a good agent is.
Routing gets quieter
Assigning, tagging and prioritising are where agents lose their mornings. They are pattern problems, and desks will increasingly do them without being asked. The risk is routing nobody can explain. A rule you can read and change will beat a model you have to trust, especially for a small team that cannot afford a mystery in the middle of its queue.
Every language, every working day
Customers will expect to be helped in their own language and inside their own working day. Tools designed around one language and one time zone, with the rest added later, will start to feel dated. Language is not a feature to bolt on. It is a property of the whole desk: the interface, the templates, the schedules, the holidays.
What should not change
- A person can always be reached. Automation should shorten the path to a human, never hide it.
- You choose your tools. Teams should decide which AI vendor sees their tickets, and be able to switch it off.
- Calm. More automation must not mean more notifications. A faster desk should feel quieter, not busier.
The best version of the future desk is not the most automated one. It is the one where the people on the team spend their attention on the conversations that deserve it.