A service desk is the one door a company has agreed its requests go through, with a name against each request and a record of what became of it, and the whole weight of the idea sits on the word one. Most companies past about twenty people are already running the desk. What they have not got is the one, on account of the asking arriving at two inboxes and a chat thread and whoever happened to be stood beside the kettle at the time, and nobody ever having sat down and given that arrangement a name.
Nobody built that arrangement. It grew, the way these things do, one helpful person at a time.
You find that out on an ordinary week rather than a bad one. The same question gets asked twice, on the Tuesday by one person and the Wednesday by another, and it gets answered twice by two people who each had every reason to believe they were the only one being asked, and the two answers do not match, not because either of them was wrong but because each was a different half of the thing. Neither asking was written down. The second person went and told four others what they had been told, and the version that spread through the building was the half that was easier to remember, which is the way of it.
That is most of the case for a service desk, truth be told, and it has less to do with software than the quotes in your inbox suggest. One door, so that the same question cannot get asked twice without somebody being able to see that it was.
Before we go on, we sell help desk software, and you may as well have that in your hand while you read the rest. A fair part of this page argues that what makes a desk work gets written down rather than installed, which is a strange thing for a company with a product to spend its afternoon on, and is the honest shape of it all the same.
Why the one door matters more than whatever sits behind it
Single point of contact is the phrase the trade uses, and it lands like a tidiness argument, a matter of keeping the place neat and the inboxes down to a sensible number. It is nothing of the sort. The door is there so the work can be counted, and counting is the dull thing everything else in this article eventually leans on.
The trouble is that a corridor cannot be counted, and when four people are being asked things in four places there is no honest answer to how much comes in of a week, or what it is mostly about, or which of it took the longest, so every conversation you have about the desk afterwards runs on somebody’s impression of a bad month. The person who shouts loudest about their own workload wins that conversation. The one quietly carrying the most of it does not, generally, on account of being the sort who gets on with it.
There is a plainer benefit as well, and it is the one people feel first. A thing that arrives through the door cannot vanish quietly. A thing told to somebody in a corridor at ten to five on a Friday goes wherever that person’s memory goes, and their memory has a weekend in the middle of it, and by the Monday they are on something else entirely and the asker is left with the belief that it is being seen to. That belief is the dangerous part. Nobody chases a thing they believe is already in hand, so the requests that go missing tend to be the ones somebody was reassured about.
Mind you, one door does not have to mean one way in. Most desks that work run a mail address as the front of it and let the awkward requests arrive however they arrive, then get put through the same door by whoever caught them. The rule that matters is not where a thing was said, it is that everything ends up in the one place with an owner on it before the day is out.
What actually comes through the door
Four sorts of thing arrive, and telling them apart is the greater part of the skill of running a desk.
The first is the broken thing. A laptop will not wake up, the payroll system is throwing an error at the one person who needs it this afternoon, the printer on the second floor has gone the way printers go. These are the ones with a clock ticking whether or not anybody set one, and they are a practice of their own once there are enough of them, which is why incident management gets written up separately.
Then there is the wanted thing. A new starter arriving on the first Monday of next month and needing a laptop, an account and a door pass. Access to a system somebody has just been made responsible for. A licence for the software their new job apparently requires. Nothing is broken in the least, somebody simply needs a thing they have not got, and the work is nearly always the same work as the last time it was asked for.
Questions are the third sort, and the sort everybody underestimates. How do I, where do I find, is it meant to look like this. Questions cost little each and a great deal in aggregate, since the same twelve of them come round and round forever, and a desk with nowhere to keep answers is a desk that answers the very same one fresh every time. That is what a knowledge base is for, and it costs less than anything else named anywhere on this page.
And then the one nobody plans for at all, the request that was never yours to begin with. The desk gets asked about the car park, about a payslip, about the meeting room booking system that belongs to whoever runs the building, about a supplier invoice. It arrives at your door on account of your door being the only one in the place that reliably answers, and that is a compliment of a kind and a problem regardless, since the not-ours pile grows quietly and nobody has ever budgeted an hour for it. A desk of any age has one. Ask yours.
Whether the invoice ends up saying help desk or service desk is a separate argument with real money in it, and we have gone at that one properly elsewhere rather than here. This page is about the thing its self, whatever the quote calls it.
A day on the desk, told the way it actually goes
Half eight and the overnight pile is sat there waiting. Nine or ten things, most of them small, one of them from somebody who wrote at eleven the previous night in the tone people use at eleven at night. First job is not answering, it is sorting: what is broken, what is wanted, what is a question with an answer already written down somewhere, and which of the lot is going to eat the morning.
By half nine the small ones are gone and the shape of the day is visible. There is one thing in there that will not be quick, the sort that wants somebody else to look at it, and getting it in front of that somebody is its own small piece of work. Every desk has an escalation route for exactly this and most of them have never written it down, so it runs on knowing that the second-line fellow does not answer chat before eleven and prefers to be asked in the morning.
Then eleven happens. Something falls over that affects a floor, or a department, or the entire sales team fifteen minutes before a demo, and the queue you had a plan for goes out the window entirely. This is the part of desk work that never survives contact with a process diagram, and it is also the part everybody who has done the job remembers, on account of it being the day’s whole texture. The afternoon goes on catching up with what the morning was meant to be for, funnily enough, and nobody writes that hour down anywhere.
And then there is the thing from Monday. It is Wednesday now. It is not urgent, it never was, and it has been quietly moved down the queue three days running by things that were, and it will keep on being moved until either somebody notices or the person who asked gives up and does without. Every desk in the world has one of these sat in it right now. The clock on it is the useful invention, which is what SLA compliance is actually for, not the reporting so much as the fact that a promise with a date on it eventually gets loud enough to be heard over the noise of a Wednesday.
Five o’clock and the queue looks about the same size it did at nine, funnily enough, which is the honest experience of desk work and not a failure of any kind. Different things in it, mind you, which is the only measure of the day that means anything and the one nobody feels at five o’clock.
What wants writing down before the door opens
Standing a desk up takes a morning, and the morning is mostly writing rather than configuring.
You need the address, first, the one place things go, and it needs to be a place and not a person. Support at, or ithelp at, or whatever suits, so that the door survives the person behind it going on holiday or leaving in the spring. Then somebody owns it, and owning it means a name against the desk on each day of the week rather than a general understanding that the two of them keep an eye on it between them. A general understanding is what you have got already. It is the thing you are replacing.
Then the hours, which people skip and then regret. What time the desk starts, what time it stops, and what somebody is meant to do at half seven in the evening when the thing they need is genuinely on fire. Say it out loud and write it somewhere. A desk with no stated hours gets judged against whatever hours the asker imagined, and the asker imagines generously.
The promises themselves want writing down as well, and people go wrong here by trying to write the lot of them at once. Two will do to begin with. Pick the two requests you get most often, put an honest time against each, and leave the rest of the list for the day you have got evidence to build it from. A list of promises with owners and clocks on it has a name and a whole discipline behind it, and there is a longer piece on building one properly, but nothing about the first morning needs any of that. Two rows, kept. The list grows its self out of the evidence soon enough, once the desk has been running a while and you can see what it is people actually ask for.
And last, somewhere for answers to live, so the twelve recurring questions get written once. This is the single highest-return half hour on the whole of the list and it is nearly always the thing that gets left until never.
What service desk software has to do, and what it will not do for you
Software has less to do on a desk than the category implies, and the little it has to do it wants to do without complaint.
The record comes before anything else, so that what was asked and what was said back and who did what to it outlives the memory of whoever happened to be on that day. Then getting the thing to the right person, by rule where the rule is obvious and by hand where it is not, which is what helpdesk automation does when it works well and what nobody notices at all when it works very well. The clock is the awkward one of them, since a clock is only worth having if it runs on the requests you would sooner it did not. And the remembering, last, meaning the answer somebody gave in March can be found in November by a person who was not there in March.
That is close enough to the whole of it. Everything else the category advertises sits on top of those and a good deal of it is optional.
What software will not do is decide what you have promised. It has no view on whether a new laptop inside three days is a reasonable thing for your company to say out loud, and it cannot tell you whether the request that came in at four is more important than the one at two, and it certainly will not go and answer anything on your behalf. The judgement stays with a person. The tool exists so the person spends their judgement on the hard tenth of the queue rather than on remembering what happened to a thing last Tuesday.
Over here at Maxdesk the desk is a help desk by the plain name of it, and the internal shape of it is written up on the IT ticketing system page rather than this one. Mail arrives and becomes a ticket with an owner, a state and a clock on it. SLAs, roles and the audit trail sit in the free plan, and the plan holds as many people as you want in it, since we bill per workspace and not per person, which matters most on an internal desk where half a building has some occasional reason to be logged in.
Where a desk quietly stops working
A desk rarely collapses. It erodes, and it erodes much the same way in most places, which at least makes the thing easy enough to watch for, every bit of it being easier to prevent than to reverse.
The second door reopens before anything else does. Somebody messages the desk directly on account of it being quicker, and it works, and it works again, and inside two months a third of the real workload is arriving somewhere it cannot be counted. The corridor never truly closes, it only goes quiet for a while, and keeping it shut is a habit rather than a setting. The fix is unglamorous and it is the same every time: the thing gets logged anyway, by whoever caught it, before anybody goes and answers it.
Somewhere after that, things begin arriving and not leaving. Tickets sit open because closing them feels like a claim nobody wants to make, and the queue turns into a shelf, and once a queue is a shelf nobody looks at the whole of it any more. They look at the top of it. Everything below has effectively gone.
Answering without writing is the quieter one. A desk under pressure answers and moves on, sensibly enough in the moment, and six months of that leaves you with a team that knows a great deal and a company that has recorded none of it. Then somebody leaves, and the day they go is the day you find out how much of the desk was sat in their head rather than in the system.
And the not-ours pile grows away in the background until the desk is carrying the building. Two people who signed up to look after IT are now the front door for facilities, HR onboarding, the phone system and the visitor badges, and none of that appears in any plan anywhere. It is worth counting separately even if you go on doing every bit of it, since work that has never been written down anywhere does not get staffed when the budget comes round.
The part of this we cannot fix for you
Now the limits, ours before yours, since a page of this sort is worth very little without them.
Maxdesk reads mail. That is the whole of the channel, and it is a real constraint rather than a modest one: there is no phone queue and no chat widget, and if your desk needs somebody sat on a phone line then we are not the tool for it, whatever else on this page fits. Most desks of the size we suit get through their week on mail without ever missing the phone. Some do not, and we would far rather have it on the page than have you find it out around week six.
Nor are we an ITSM suite, and we would rather say so than let a demo imply otherwise. The configuration database, the change workflow and the asset discovery that a grown practice runs on are all absent from Maxdesk, and we are not quietly building them either, so that side of the work wants a different tool and probably a different budget. IT asset management is a subject of its own and a desk is not one.
The free plan has its edges too, and they are stated rather than hidden: it carries advertising, outgoing mail wears a small Maxdesk line on it, history is kept for three months, and only a limited number of automations can be active at once. That combination suits a great many small desks perfectly well and it does not suit everybody, and knowing which of the two you are takes about ten minutes with the plans in front of you.
And the plainest limit of the lot, which no software anywhere gets around. A desk with nobody genuinely accountable for it drifts back to being an inbox, and it does so within about a quarter, no two ways about it. Whatever it runs on. The tooling puts the work somewhere it can be seen, and somebody still has to go and look at it, which is not a thing any plan on any wall has ever done on its own.
Where to start, if the door is not really one door yet
Do not buy anything this week. Count your doors instead.
For five working days keep a tally, on paper or wherever suits, of every place a request actually landed. The shared alias, a direct message, somebody’s personal mail, the phone. The corridor and the kitchen count for as much as any of them, mind you, and they are the two people always forget. One line per request, no detail needed, just where it came in and roughly what it was about.
Nearly everybody who keeps the tally lands somewhere between four and seven doors, and the split of it surprises them more than the number does, on account of the official door usually carrying less than half of it, which is a thing worth seeing your own self rather than taking our word on. Then take the two busiest and give them a single address, go and tell the twenty people who use them most, and see how the following fortnight goes. That is the useful half of the whole exercise and it costs nothing at all.
If the tally makes the case, the free plan takes unlimited people and you can point an alias at it in an afternoon, and an afternoon of your own mail landing in it will tell you a good deal more than the rest of this page has.