The Other Side of ITSM. The One Your Users Actually See.

We spend a lot of time talking about the back end of ITSM. Workflows, automations, SLAs, integrations, dashboards. All important. All invisible to the people the service desk exists for.

Because here is the uncomfortable truth. Your end users do not care how elegant your workflow engine is. They care about one thing: something is broken, and they need it fixed so they can get on with their day.

This article is about them. The other side of ITSM.

Your users are experts. Just not in IT.

Think about the people raising tickets in your organisation. The finance manager who closes month end without breaking a sweat. The nurse. The engineer. The sales lead who knows every client by name.

These people are brilliant at their jobs. They should not need to know the difference between a locked account and missing permissions. That distinction matters to your service desk. It means nothing to them. To them, both look the same: "I can't log in."

When an ITSM tool forces users to self-diagnose before they can ask for help, it has already failed. Category trees written in IT language, mandatory fields asking for information users do not have, forms that read like an exam. Every one of these is a small message that says: this system was built for IT, not for you.

AI helps the people who already understand IT

The AI revolution in service management is real, and it is exciting. Intelligent routing, suggested resolutions, summarised tickets, automated triage. But look closely at who benefits first: the people who already speak IT.

Your analysts get faster. Your managers get better reporting. Meanwhile, the end user is still staring at a form asking them to pick between "Access Management" and "Identity Services."

If AI only accelerates the back office, we have missed the point. The real opportunity is using it to remove complexity for the person raising the request. Plain language in, sensible action out. The user types "I can't get into my email" and the system quietly works out the rest.

That is the difference between putting AI to work and letting your people work. The technology should carry the effort, quietly, in the background. Your users should barely notice it is there.

The portal is your front door. Treat it like one.

For most employees, the self-service portal is the service desk. It is the only part of your ITSM investment they will ever touch. If it is cluttered, confusing or slow, that becomes their opinion of IT as a whole.

A good portal does a few things well:

It reads like your organisation talks. Not "Submit an incident pertaining to end-user computing." Just "Something's not working." Plain words, familiar names, no acronyms at the front door.

It makes reporting an issue effortless. Short forms. Smart defaults. Only ask what you genuinely need. If your form takes longer to fill in than the fix takes to apply, users will bypass it and email someone instead. And once they do, your carefully designed process is gone.

It shows people where things stand. Nothing erodes trust faster than a ticket disappearing into silence. Users should be able to see, at a glance, that their request was received, who is on it, and roughly when to expect news.

It helps people help themselves, without forcing it. Knowledge articles, guided answers and common fixes should be offered, never used as a wall between the user and a human.

This is one of the areas where HaloITSM quietly shines. The portal is genuinely configurable, so it can look and sound like your organisation rather than like an IT department. That flexibility matters more than any feature list.

Communication is a two-way street

Here is where most service desks lose goodwill: not in the fix, but in the follow-up.

The technical team resolves the issue, closes the ticket with "Resolved. GPO reapplied, cache cleared," and moves on. Job done, from their side. From the user's side? A notification full of jargon that explains nothing.

Good communication back to the end user means:

• Updates in human language. "We've found the cause and expect this fixed by 3pm" beats any technical note.
• Honesty when things take longer. Users handle delays far better than silence.
• A proper closing message. What was wrong, what was done, and what to do if it happens again. In words they would use themselves.

None of this requires more effort from your team. It requires templates, notification design and ticket workflows built with the reader in mind. Set it up once, and every ticket communicates well by default.

Measure what users feel, not just what IT delivers

An SLA can be green while your users are quietly furious. "Resolved within 8 hours" says nothing about whether the person felt heard, understood the outcome, or would willingly contact IT again.

This is why more organisations are looking past SLAs towards experience: short satisfaction surveys, feedback on knowledge articles, watching where users abandon forms. Small signals, honestly collected, tell you far more about your service desk than a wall of green metrics.

You do not need a complex programme to start. One question after ticket closure. Read the answers. Act on the patterns.

No two organisations are the same. And that is the point.

Here is what we will not tell you: that there is one correct portal layout, one perfect form, one right way to communicate.

You know your organisation. You know your users. You know that what works for a 200-person law firm will not work for a manufacturer running three shifts. You know which teams will embrace self-service and which will phone the service desk no matter what.

That knowledge is worth more than any best-practice template. Our job is to bring the platform expertise, the patterns we have seen work, and the honesty to say when something will not. Your job is to bring the understanding of your people that no consultant can shortcut.

We are in this journey together. The best user experiences we have built came from exactly that partnership: your insight, our implementation, and a willingness on both sides to learn, adjust and improve as real users start using the real thing.

Start with one question

If you take one thing from this article, take this. Open your portal and ask: could my least technical colleague report an issue here in under a minute, without asking anyone for help?

If the answer is no, that is where the work starts. Not with more automation. Not with more AI. With the front door.

The back end makes your service desk efficient. The front end makes it trusted. You need both, but only one of them is judged by every employee, every day.

Hikon helps organisations design ITSM experiences that work for the people using them, not just the teams running them. If you would like a fresh pair of eyes on your portal and user journey, get in touch.