Walk past any service desk and watch what the agents are actually doing. In most organisations, it looks something like this: read the ticket, open the knowledge base, search, open a second system to check the user's kit, search again, ask the user a question they have already answered somewhere else, then finally start working on the fix.
That is not problem solving. That is professional Googling, with extra steps.
The frustrating part is that none of this is the agent's fault. It is a design problem. When an implementation treats the ITSM tool as a place to log tickets rather than a place to resolve them, agents are left to bridge every gap manually. They become the integration layer between systems that should have been talking to each other from day one.
At Hikon, this is one of the first things we look at in any Halo implementation. Not the ticket volumes, not the SLA reports, but a simple question: when an agent opens a ticket, how much of what they need is already in front of them?
A lookup desk answers the question "where is the information?" A problem-solving desk answers the question "what should we do about it?" The gap between the two is not talent or headcount. It is how much thinking the platform does before the human gets involved.
Here are the shifts that make the difference.
If your agents have to leave the ticket to find an answer, you have already lost time. In Halo, knowledge articles can be surfaced directly within the ticket based on its category, keywords and history. The agent stays in one place and relevant guidance comes to them. Even better, the same articles can be offered to end users at the point they raise a request, which means a good portion of tickets never need an agent at all.
A ticket that arrives with the user's device details, recent tickets, related incidents and affected services attached is a ticket that starts at step three instead of step one. Asset data, user history and service relationships should be visible the moment the ticket opens. No second system, no asking the user what laptop they have. This is configuration work, not magic, and it is where a large part of the resolution time hides.
Password resets, access requests, standard software installs, starter and leaver processes. Every service desk resolves these hundreds of times a year, the same way, every time. These belong in automated workflows with self-service front ends, so end users get an instant outcome and agents get their time back for the tickets that genuinely need a human brain.
The best source of knowledge in your organisation is the fix your agent applied twenty minutes ago. A well-set-up desk makes it a natural part of closing a ticket to capture the resolution as a draft article. Over months, the knowledge base stops being a static library and becomes a living record of how your organisation actually solves things. New starters ramp up faster, and the whole team benefits from every individual fix.
For complex or high-impact tickets, agents should not be improvising. Embedded checklists, decision steps and guided workflows inside the ticket mean a first-year agent can handle an incident with the consistency of a ten-year veteran. It also means your process is in the platform, not in someone's head, which matters the day that someone hands in their notice.
If the same incident keeps arriving, the answer is not a faster agent. It is problem management. Linking recurring incidents to a single problem record, tracking the root cause and pushing through a permanent fix is how a service desk stops running on a treadmill. It is also one of the most under-used capabilities we see when we review existing implementations.
Do these six things well and something interesting happens. End users stop noticing the service desk, in the best possible way. Answers arrive quickly, routine requests complete themselves, and when a human does get involved, they turn up already informed.
Your agents notice too. The job shifts from searching to solving, which is better work, done by happier people, who stay longer.
None of this requires a bigger team or a heroic effort. It requires an implementation designed around resolution rather than logging. That is the work we do.
If your service desk feels more like a search engine than a solutions team, we would be glad to take a look. Get in touch through hikon.co.uk.
Talk it through with the people who wrote it — a free 20-minute call, no pitch.
Let's talk →Book a free 20-minute call about your platform and your plans — no pitch, no obligation.
Start the conversation