The Request That Never Reached the Helpdesk: Building an IT Service Catalogue for Your SME

  • 2 days ago
  • 0

Somewhere in your business there is a request that will never appear in any IT report. It went to a person, not a process: a Teams message to the operations manager at 4:40 on a Friday asking for a new starter’s laptop, a text to the one colleague who understands the phone system, a card payment for a monitor that nobody will ever add to an asset register. The request was made. It simply never reached the helpdesk.

A business without a service catalogue does not have zero demand. It has demand it cannot see, price or refuse. The answer is not to tell people to log more tickets. It is to make the proper front door faster and clearer than the shortcut.

Requests travel towards people, not processes

Without a catalogue, the organisation chart becomes the menu. Staff ask whoever is nearby, quick to reply or known to have solved the problem before. One person handles a request in a message; another asks for an email; a third orders the equipment and sends the bill to whichever budget seems nearest.

The result is invisible demand, inconsistent priorities, missing records and unclear costs. The person who understands how the phone system is licensed becomes a single point of failure. If they leave, the knowledge of how requests are meant to work may leave with them.

Ticket volume is a floor, not a total. The more interesting number is demand that never became a ticket: what people asked for informally, arranged themselves or gave up trying to obtain.

A catalogue is a set of decisions already made

A service catalogue is not merely a document or an intranet page nobody opens. It records what the business has already decided: what people are entitled to, who approves exceptions, what it costs and how long it should take. That way, an individual does not have to re-decide it at 4:40 on a Friday.

Someone senior must own those decisions. Each entry affects funding, risk or working practices; it is not just an IT preference. This is strategic IT Consultancy work: the point where business strategy becomes something a member of staff can actually action.

What belongs in it for an SME?

Keep it useful and short: a dozen to twenty entries, not two hundred. Start with the requests your people actually need to make:

  • A person joins or leaves.
  • A person needs a device.
  • A person needs access to a system, folder or mailbox.
  • A person needs a phone, number or line.
  • A site needs connectivity or a network change.
  • A team needs software or a licence.
  • Something is broken, something is changing, or someone needs guidance.

Include access to Business Central and system change requests. A governed Dynamics 365 Jump Start is a route for assessing and authorising a systems change, not a form asking someone to guess the technical answer. IBM i Management access, terminal emulation and vendor logins should follow that same route rather than being arranged directly with a supplier.

Some requests are compliance events dressed as admin. A client asking for a copy of their data, a subject access request arriving in a general inbox, or contact from a journalist or regulator should reach the right person promptly. A right-of-access request can have a legal clock attached; the ICO guidance explains how organisations should recognise and handle it.

Plain cardboard boxes and neatly coiled cables beside dark metal shelving, lit by a restrained warm gold glow

The parts of an entry that make it work

Each entry needs seven fields:

  1. Who is entitled to request it.
  2. What the standard offer is.
  3. Who pays, and from which budget.
  4. Who approves it.
  5. How long it should take.
  6. What happens if it is refused or needs escalation.
  7. What gets recorded afterwards.

The most neglected field is the standard. “A laptop” is not a standard offer. A defined device build, with an agreed purpose and cost, is. Without a standard, every request becomes a fresh procurement conversation; every team can end up with a different device, handset and support experience.

The second most neglected field is the refusal route. A catalogue that describes only successful requests teaches people to bypass it. Staff need to know who can reconsider a refusal, what information to provide and how an exception is decided.

For access requests, a clear approval route is also a security control. The NCSC describes user access control as one of the core areas in its Cyber Essentials overview. The ICO’s data security guidance sets out the need for appropriate technical and organisational measures. A catalogue helps put those principles into day-to-day practice: the right person requests access, the right owner approves it, and the decision is recorded.

Three routes, and making the slow one unnecessary

Separate three kinds of request:

  • Self-service for trivial, reversible tasks: resetting a password, printing an MFA code or checking a mailbox size.
  • A logged request for anything involving a cost, permission or asset.
  • A conversation for genuine design questions, where the answer is not a form.

Then make the routine route genuinely easy. If a self-service reset takes seconds and asking a colleague takes a day, behaviour changes without a policy memo.

Good Helpdesk Support makes the request route accessible and visible. But self-service done badly (a portal nobody can find or a form with fourteen fields) sends people straight back to the shortcut. A catalogue should remove friction, not rearrange it.

The shortcuts a catalogue actually stops

The behaviours are familiar: a card purchase that never reaches the asset register; a shared login created because an access request took a week; a free app trial holding a client file; a personal cloud drive used because folder permission was not granted; broadband ordered for a site by someone unaware of an existing contract; or a handset bought on a personal contract and expensed.

These are signs that the front door is not working, not proof that the workforce has a character flaw. Shadow IT often points to a slow or confusing request route. The fix is usually response time and clarity, not another acceptable-use reminder.

Where a request involves a supplier or vendor, the catalogue should identify who checks that involvement and what assurance is needed. The NCSC’s supply chain security guidance emphasises the importance of effective oversight of suppliers.

A wall-mounted telephone handset in a dark office corridor, with brushed metal details and shallow focus

What it does for the cost side

A catalogue is the honest basis for pricing a support arrangement. It establishes what is included in the managed service, what is chargeable, what is priced per site and what is a project. Monthly request volume by type becomes a capacity conversation rather than a complaint. “Can you just” is one of the most expensive sentences in an SME’s IT budget; the catalogue is where the work gets scoped and quoted.

Technology Expense Management complements the catalogue. The catalogue decides what should exist; expense management checks what is actually being paid for. Together they help reveal duplicate lines, orphaned licences and equipment nobody requested.

The same discipline applies when someone leaves. Accounts, numbers, phones and subscriptions should be closed through a recorded request, not left to someone’s memory. Voice and Connectivity and Cloud Solutions can then support defined standards for phone services, identity and tenancy. The cost and approval rules are already set, rather than improvised each time.

It has to survive contact with a new starter

People learn the catalogue in their first week or often not at all. Put it in induction, walk new joiners through the three routes and give line managers a one-page version. Managers are the people most likely to escalate informally on a colleague’s behalf.

Review the catalogue when a request is refused twice (the entry may be wrong) as well as when a standard changes. Revisit it after a continuity event, too. A disaster is a poor time to discover that nobody knows who can authorise an emergency purchase. Disaster Recovery planning is where that approval authority should be agreed in advance, rather than improvised.

Keeping it honest

A few small disciplines keep the catalogue useful:

  • Name an owner and set a review date.
  • Count requests by type each month; the four or five that dominate show where a standard or route may need attention.
  • Record anything bought outside the catalogue, so informal demand does not vanish from view.
  • Keep a short note of what was refused and why, so decisions are consistent rather than personal.
  • Publish it where people actually look, not only on the intranet.

Keep it to a page or two that a manager can read on a phone. Managed IT Services and Network Solutions can help deliver agreed standards, while a capable Helpdesk Support route makes them practical to use. These are execution services in support of the decisions, not a substitute for making them.

An orderly row of identical closed dark laptops on a quiet workshop bench, with a fine gold reflection along their lids

A business without a catalogue is not disorganised. It is simply making the same dozen decisions again every week, differently, by whoever is nearest. A Fractal IT Director sets the choices and standards; Managed IT Services, Network Solutions, Helpdesk Support, Cloud Solutions and Voice and Connectivity make the standard offer real once those decisions exist. For the wider Evestaff group of services, visit evestaff.co.uk. A catalogue is not a form. It is the answer to: “What have we already decided?”

SEO keywords:
Cloud Solutions
Disaster Recovery
Dynamics 365 Jump Start
Helpdesk Support
IBM i Management
Managed IT Services
Network Solutions
Technology Expense Management
Voice and Connectivity
Fractal IT Director
IT Consultancy

Join The Discussion