A helpdesk is the thing that happens when questions start arriving faster than one person can hold them in their head. That is the whole of it, really, underneath the software and the dashboards and the words people put on a pricing page. It is not so much a product you go and buy as a job that quietly comes into being, and most teams are running one for a good long while before anybody sits down and gives it the name.
Nadia was running one for the better part of a year before she called it anything at all. She looks after support for a company that sells scheduling software to dental practices, a small outfit, and it started the way these things always start, with one inbox and her own two hands. The support address went to her. She answered it. When she was out nobody did, and the questions sat over the weekend waiting on her, which was fine, mind you, back when there were six of them in a day.
Then the company grew, the way companies do, and the six became sixty, and Nadia did the sensible thing and shared the inbox out. She gave the login to two other people. And that, funnily enough, is the very moment the helpdesk was born, though nobody in the room would have said so at the time. The thing about a shared inbox is that it works right up until it does not, and the day it stops working is not marked on any calendar for you.
How a shared inbox quietly turns into a helpdesk
The trouble with three people and one inbox is not the people. They are all good at their jobs and they all mean well. The trouble is that an inbox was built for one person to read their own mail, and the minute two of them open it at once, it starts telling small lies.
Somebody replies to a customer. Somebody else, not knowing, replies to the very same customer, and now the poor woman running the dental practice has two answers that do not quite agree, sent forty minutes apart by two people who never once spoke to each other about her. A message gets read, which marks it read, which means the next person scrolling past takes it as handled when it is nothing of the sort. Another gets archived by mistake, on a Tuesday, and is simply gone after that. Not answered and not refused, just gone. The customer waits, and eventually goes quiet, and you never learn why.
None of that is anybody being careless. It is the inbox doing exactly what an inbox was built to do, which is serve one reader, being asked to serve three instead. It was never the tool for the job. It only looked like the tool because it was already sitting there, and it was free, and everybody knew how to use it already.
Where the tickets quietly go missing
You would think the ones that go missing would be the hard ones, the angry ones, the complicated refunds. Sometimes they are. More often the hard ones get answered, on account of them being loud, and the ones that slip through the gap are the quiet, ordinary questions that did not seem urgent to anybody and so waited, and kept on waiting.
The message that came in while two people were both looking at the inbox and each quietly assumed the other one had it. A follow-up to a thread from last week that the whole team had mentally filed away as closed. Then there was the customer who wrote thanks, one more thing underneath an answer, so the one more thing arrived stapled to the bottom of a conversation marked done, and nobody opened it a second time. One came in over the weekend and was eleven emails deep by Monday morning, buried under newer mail, read by nobody at all.
And then the things that are not really about a single message. Whether anybody actually knows how many questions came in this week, or how long people waited, or which question keeps turning up again and again and might be fixed once at the source instead of answered fresh every single time. A shared inbox cannot tell you any of that. It was not built to count, it was built to hold, and so the whole picture of how your support is really doing lives nowhere at all, except maybe as a bad feeling in the pit of Nadia's stomach on a Friday afternoon.
Why the loudest customer is never the one to worry about
Here is the part that catches people out. The customer you hear about is the one who wrote in twice, or wrote in cross, or went and found somebody's direct address and came round the side. That customer, at the least, is still talking to you. You know they exist, you know they are unhappy, and you can go and fix the thing for them.
The one to worry about is the one whose question fell down the gap and who did not write again. They did not escalate. They did not complain. They just quietly decided your company was the sort that does not answer, and they carried that opinion off with them, and the first you hear of it, if you hear of it at all, is a number on a churn report three months later with no name attached and no way back to the Tuesday it started on. A shared inbox is very good at surfacing the loud ones and completely blind to the silent ones, which is precisely backwards, on account of it being the silent ones that quietly take their custom off somewhere else.
What a helpdesk actually keeps track of
So what is the thing a helpdesk does that the inbox cannot. Strip the branding off it and it comes down to a small handful of plain jobs.
It gives every question a single home, one conversation that belongs to one person at a time, so that two people cannot both answer it and nobody can quietly assume somebody else already has. It remembers who the customer is, so the one more thing underneath last week's answer lands as a fresh thing to be handled and not as noise at the bottom of a closed thread. It keeps a count, the dull and necessary count, of how many came in and how long they waited and which question turns up over and over. That is the number Nadia never had and felt the lack of every Friday. And it holds the ordinary answers somewhere the whole team can reach, so the ninth person to ask how to reschedule a booking gets the same clear reply as the first, written the once and reused, instead of three people writing three slightly different versions from memory.
That is a helpdesk. Not the dashboards, not the automations, not the words on the pricing page, all of which come after. Underneath the whole of it, a helpdesk is just the shared inbox finally being handed a tool that was built for more than one reader, which is the thing a shared inbox never was and was never going to become on its own, no matter how many rules you wrote up for using it properly.
Over here at Maxdesk that is the job we went and built for, plainly said. Email comes in, becomes a ticket that belongs to one person, and the count keeps its self without anybody having to tend it. The part that tends to surprise people is the pricing, on account of most helpdesks charging you by the agent, so every new person you put on support adds another monthly line, and you find yourself rationing who gets a seat, which really means rationing who is allowed to see the tickets. Which is a strange thing to be doing to your own support team, when you sit and think about it. Maxdesk charges by the workspace instead. The whole of your team can be in there, the weekend cover and the summer temp and the developer who only ever answers the technical ones, without the bill going and climbing every time you add a name.
The part where the software does not fix everything
Fair is fair, so here is the place a helpdesk stops.
It will not answer the questions for you. It puts each one in front of a person, cleanly, with the history attached, and the person still has to know the answer and still has to write it kindly, and no software anywhere does that bit for you. What it buys you is that the question actually reaches somebody, which the inbox could not promise. But the reply is yours to write either way.
And it will not, on its own, tell you why a customer is really upset. It gives you the count and the wait times, and those point you at the sore spots well enough, but the reading of them is a human job, on account of a number going up telling you where to look and not what you will find when you get there. Somebody still has to sit with it and work out whether Tuesdays run slow because the volume spikes or because your best person happens to have Tuesdays off.
There are plainer limits worth saying out loud too, since I would rather you heard them here than found them your own self a month in. Maxdesk is email, only email, at least for now, so if what you actually want is a live chat bubble on the website or a phone line ringing, this is not that, and no amount of me being pleasant about it changes the fact of it. The free plan carries a bit of Maxdesk branding on the outgoing mail and keeps your ticket history for three months rather than forever, and if that matters to you then it matters, and that is what the paid plans are there for. None of it is hidden and none of it is a catch, but you ought to know it going in.
Where to start, if this sounds familiar
You do not need to buy a thing to find out whether you have this problem. Go and look at your support inbox, the shared one, and put a couple of plain questions to it your own self.
Ask whether you could say, right this minute, how many questions came in last week and how long people waited on average, and if the honest answer is that you could not, that is worth sitting with a while. Ask whether two people have ever answered the same customer, or whether a message has ever been marked read by one person and taken as handled by another, and watch the faces when you ask it, because you will get your answer from the faces a good beat before anybody says a word. Ask whether the ninth person to ask the same question got the same answer as the first, or three slightly different ones from memory.
Most people who go and actually look find something inside the hour, and it is usually quieter and more ordinary than they feared, which is the whole trouble with it, on account of quiet and ordinary being exactly the sort of thing that hides in a shared inbox for a year before anybody names it. If what you find bothers you, that is roughly the point at which a shared inbox stops being enough and a helpdesk starts being worth the small bother of setting one up. You can try Maxdesk against your own support mail and see for your own self whether any of this holds, which is a more honest test of it than another page telling you that it does.