Helpdesk From Scratch

It is day zero and the queue is empty. There is a login page, a dashboard full of zeros, and a settings menu that could absorb the whole week if you let it. Somebody has said "set up a help desk" at an organization that has never had one. Or they have looked at the shared mailbox that has been the help desk all along and decided it is time for something real. Nobody is waiting on you yet. By tomorrow afternoon that will no longer be true. It will never be true again, which is the point of the thing you are about to build.

This series is for the administrator holding that empty queue. It covers the six things a desk needs before its first ticket and the four decisions that are hard to undo. It covers how to choose the first tool for the desk you will have in eighteen months rather than the company you hope to be. The trial is built on real tickets. The series covers the first five processes, each on one page, and the first three metrics and the eight you should not measure yet. It covers how to announce the desk so that people use it instead of walking over. And it covers the whole of the first ninety days on one page. That ends with the week the desk ran without you and nobody noticed.

Articles in This Series

• Day Zero: What You Need Before the First Ticket
  The minimum that works: one queue, one address and one form, and three categories. It also needs one owner, one reply template and a page that says how to reach the desk. Also covers what can wait a month, the four decisions you cannot easily undo, and a day-zero checklist.
• Choosing the First Helpdesk Tool
  The ten requirements that matter and the ones that depend on you; the trap of buying for the company you hope to be. Covers a two-week trial on ten real tickets with a scorecard. Also covers the cost of changing later, and the hosting question answered plainly.
• The First Five Helpdesk Processes
  Intake, triage, escalation, close and the weekly review: what each is, the one-page version, the template and the failure it prevents. All five are on a single page to copy, with the loop drawn.
• The First Three Helpdesk Metrics
  Volume, age and reopen rate: what each tells you in month one and what it does not. Covers how to get them from any tool, and what not to measure yet and why. Also includes a month-one metrics sheet with a column for the decision taken.
• Announcing the Helpdesk to the Organization
  One address, one reason, one promise; the launch message and its timing; and the walk-up redirect that does not insult anyone. Also covers winning the first fifty tickets, the five-minute managers' briefing, and how to tell whether the launch took.
• The Greenfield Playbook: Ninety Days on One Page
  Month one to run, month two to tune, month three to hand over: the week-by-week plan. Covers the things that will go wrong and when, the handover test, and the decision about what comes next.
• The Help Desk SOP
  Standard operating procedures for a small desk: the eight to write first, the one-page shape that gets followed, an afternoon's method, and a copyable template with one procedure filled in.

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.