Incident management is the whole of what a shop does in the stretch of time between a thing going wrong and the thing being put right, and, just as much, it is what the shop says to the people that the wrong thing landed on while they sit there waiting on it. It is not the fixing its self. The fixing is engineering, or it is a phone call to a courier, or it is somebody restarting a server that had no business falling over on a Saturday in the first place. Incident management is the whole of the rest of it, the who-knows and the who-answers and the who-goes-and-tells-the-customer, and almost nobody sits down of a calm afternoon and designs that part on purpose. It gets made up on the hoof the first bad morning a shop ever has. And then the made-up thing, the panic and the guessing and the hoping, quietly becomes the way it is done from that day on. Nobody ever votes for it. It just settles in.
Cathal and Sinead found theirs by accident, weeks after the morning that made it. The two of them run a small software shop out of a room in Cork, a booking widget that salons and barbers drop onto their own websites so a customer can pick a slot without ringing anybody. Cathal does the code and Sinead does the mail, more or less, though on a bad day the line between the two of them goes blurry. And it was Sinead, one quiet Tuesday a good while later, who had the support inbox open for a reason that had nothing to do with any of this, she was hunting down an old thread about a refund, when she went and stumbled on the whole of what had happened the Saturday the widget fell over. Three messages from the one salon, a barber's up in Limerick run by a woman named Orla, sent across the one morning. The first was a question. The second, an hour on, was sharper. The third said only that the bookings were away again and she would sort something else out. It had been answered the once, vaguely, and never again, and the honest part of it is that Sinead only found the thing at all because she went looking for a refund. Nobody was ever going to go back and find it on purpose.
How a Small Shop's Incident Response Gets Invented in a Panic
The Saturday its self had started ordinary and gone wrong around ten. The widget stopped taking bookings, all of it, every salon at once, for the better part of three hours, on the one morning of the week those shops live or die on. And the mail came in the way it always comes in when a thing breaks for everybody at the same time, not as one alarm going off but as thirty separate people each writing in about what looks, from where they are sitting, like their own private problem. One says the button does nothing. One says a customer rang them cross. One just says is it only me, mind you. Thirty little messages, and every one of them the very same incident wearing thirty different coats, and not a soul in that inbox seeing it whole.
That is the miss that sits under all the other misses. Thirty reports of the one broken thing are still the one broken thing, and if you cannot see that they are the same, you go and answer them as thirty. Sinead read each as it came, the way you would read any normal morning's mail, and each got its own fresh reply written from cold, as though the woman in Limerick and the fella in Galway were having two unrelated bad days rather than the exact same bad three hours. There is no meeting where anybody decides to do it this way. It is only what happens when the mail arrives one message at a time and nothing anywhere is telling you that this one and that one and the other one all belong together.
Where It Comes Apart the Moment Two People Answer
It comes apart first in the place you would least expect, which is that there were two of them answering. Cathal saw the panic and put his head straight down into the code, which is exactly what you want the person who can fix it to be doing, mind you. But he was answering the odd message too, in the gaps, the ones that pinged his own phone. So now you had Cathal telling three salons one thing and Sinead telling the next lot something a little different. Neither of them had the least sight of what the other had already gone and promised. The same shop, two mouths, two stories. No two ways about it. And a customer on the far end who does not know nor care that there are two of them, who only knows she was told at half ten it would be twenty minutes and told at eleven it was being looked into, which are not the same message and cannot both be true.
Worse again was the promise that got made in the heat of it and could not be kept. Somebody, and it does not much matter which of the two, wrote back early on that it would be sorted within the hour, on account of it feeling true in the moment and on account of a person under pressure wanting to give a worried customer something solid to hold. But the hour went and the thing was not sorted. The bug was deeper than it looked from the outside, and now every salon that got the within-the-hour line was sitting there at half eleven watching an hour that had come and gone. A shop that had said nothing at all would have been in less trouble than the shop that went and promised a time it then sailed straight past. Being slow is a thing people forgive easily enough, they have all been slow their own selves. Being slow right after you swore blind you would be quick is the thing that actually gets under their skin, no two ways about it.
Then the fix landed, near enough to noon, and here is the quiet killer of the whole business. Nobody sent the note. Cathal got the widget breathing again, felt the flood of relief a person feels, and moved straight on to making sure it stayed up, which is a fair instinct and the wrong one. Because the thirty salons did not know. There is no bell that rings in Limerick when a server in Cork comes back. Orla found out it was working the way most of them found out, by going and trying it herself a while later on the off chance. And a fair few never went back to try at all. They had already made their Saturday arrangements around a thing they had decided they could not rely on, and that was the end of it. The incident was over inside the shop a full hour before it was over for the customer, and for some of them it was never told to be over at all.
And under that, the last miss, the one that guarantees the next time will go the same road. Nobody wrote down a word of what happened. What broke, when, who was told what, what finally fixed it. It all lived in the two of their heads, and heads empty out, so when the widget went and wobbled again months later there was nothing to reach for, no note that said last time it was this and we handled it that way. They started the second incident from the very same cold nothing they had started the first one from. A shop can have the one bad morning three separate times and learn not one thing from any of it, purely for want of somebody jotting down a few lines while it was fresh. That is the whole waste of it.
Why the Outage Was Never the Real Damage
Here is the part that most small shops get the wrong way round, and not through any thickness either. The instinct is to treat an incident as a technical event, a thing that is measured in how fast the broken bit got mended, and to feel that a three-hour outage patched in three hours is a job more or less done. But the three hours down did the smaller share of the harm, truth be told. The bigger share was thirty people each going through those hours alone. In the dark, getting a different story or no story, watching a promised time slide past, each one of them on their own. An outage that every customer knew about, understood the shape of, and got one honest running account of would have cost that shop almost nothing in goodwill, even at three hours. The same outage handled in silence and crossed wires cost it Orla, and cost it a clatter of others it never even knew it lost. The breaking, that is the engineering end of it, and engineering gets fixed one way or another. The being-left-alone-in-the-dark is the part that quietly empties your customer list on you while you are busy congratulating yourself on the fix. And that part is a communication problem from the first minute to the last. Not a technical one at all.
What Handling One Incident Well Actually Looks Like
So what does the good version actually look like, said plainly and without making it sound grander than it is. It looks like somebody spotting early that the thirty messages are the one incident, and the whole shape of the response bending around that single fact. One person owns it, so there are not two mouths anymore. Just the one. One holding note goes out to every soul who wrote in, the same honest line to all of them, we know, it is us not you, we are on it, we will tell you the minute it is back and we will not guess a time we cannot stand over. Then the fix happens in its own time. Then, and this is the bit that goes missing every time, one more note goes out the moment it is right again, to every one of the thirty, it is back, here is the sorry, here is the small thing we are doing so it does not happen again. And after all of it, when the heart rate is down, two or three lines written somewhere that will still be there in six months. That is the whole of it. It is not clever and it does not need a war room.
Go back to Orla in Limerick and read what she was actually after, because it was a good deal less than the silence made it seem. She did not need it fixed in twenty minutes, she runs a barber's, she knows things break. That much was grand. She needed to know a person had seen her, that the shop knew it was the shop's own doing and not hers, and that somebody would tell her when she could trust the thing again so she could stop refreshing it between customers. One honest note on the Saturday, and a second when it came back, would have kept her. Instead she got a vague half-answer and then a silence she filled in for her own self, and she filled it in with grand when it works, which is about the most damning line a customer ever leaves you, on account of it meaning the product is grand and the shop is not a thing you can lean on. And that split, whether the shop can be leaned on or only the software, is the whole of what decides if she stays. It is not built out of a bigger team or a cleverer tool. It is built out of the seeing and the telling and nothing more. This is the ground where a proper IT ticketing system earns its keep, not by mending the bug for you, which it never will, but by making sure the thirty coats never again hide the one incident, and that the note goes out to every last person who wore one.
Where Maxdesk Fits, Said Without the Sales Voice
I would as soon say plainly that this is the sort of shop we built Maxdesk for than let on the piece wandered onto the subject by chance. Maxdesk takes the support mail a shop already gets, on the very address the customers already write to, and turns it into tidy tickets, which is only a plain way of saying that every message becomes a thing with an owner and a state to it instead of a line in a shared squint. When thirty write in about the one outage, they land in the one place where a person can actually see the pile stacking up and cop, early, that this is not thirty problems but one. It shows you which of the two of you is on a thread, so Cathal cannot be promising one thing while Sinead promises another to the fella next door. It keeps every writer's message gathered together, so when the thing is mended the it-is-back note can go to the whole of them and not just the three that happened to shout loudest. Every last one, not the loud few. It ships a knowledge base for the questions that come round every time, the is it down and the where do I check, so the answers that never change can sit somewhere a customer finds on their own. And it lets you set the reply-time targets you actually mean to hold your own self to, and then it minds the clock on them, so a promise made in a panic has somewhere to live besides one tired founder's memory.
And it does the whole of that on a free plan that charges nothing per head, which matters more than it sounds for a two-person shop that might be five people come a busy season. Put a third pair of hands on the mail for the Saturday rushes and the bill does not climb a penny for the extra person, on account of Maxdesk not charging by the head the way a fair few of these tools quietly go and do. Fair is fair, there is a trade in the free plan and you should hear it from me now rather than trip over it later. The free workspace carries some supporting ads, puts a small Maxdesk name along the foot of the mail going out, and keeps three months of history rather than the whole of forever, so if your reporting wants a longer memory than the one quarter, that is the thing the paid plans are there for. It plugs onto the address you already use rather than asking you to move house, and the setting of it up runs about sixty seconds, near enough.
The Part This Does Not Fix Its Self
Fair is fair a second time, so here are the limits of the thing, said before anybody builds a hope on the wrong footing. Maxdesk is a lightweight shared inbox for email support, and that is deliberately the whole of what it is. It is not a full incident management platform, and I would be doing you no favour dressing it up as one. There is no alerting in it that pages an engineer at three in the morning, no on-call rota, no severity dashboard counting your outages, no public status page hoisting a red light for the world to see. If what your shop genuinely needs is cloud incident management with the whole of that machinery, the paging and the runbooks and the major incident bridge calls, then you want a dedicated incident management tool built for exactly that, and a shared inbox is not it. What Maxdesk handles is the customer-facing side of the same event, the intake and the coordinating and the closing of the loop, which for a small shop is very often the whole of the side that was actually going wrong.
There is a plainer limit sitting under that one. The tool does not run the incident its self, it only clears the way for a person to run it well. It gathers the thirty coats into the one place and shows you they are the one incident, but a person still has to be the one to look at it their own self, to cop the pattern, to write the honest holding note, to decide the fix is solid enough to send the all-clear. It does not mend the widget, and it does not know the right words for the sorry. A person does the whole of that their own self, every single time, and a person always will. The tool is the seeing and the sorting and the not-forgetting of it. The judgement stays where it has always been, with the tired human at the far end of the line who has to decide what to say and when.
Where to Start, If This Sounds Like Your Last Bad Morning
Before you go pricing a single tool, do the cheap thing first and go and read back over your own last bad morning. Pick the one incident, the outage or the botched batch or the day the phones melted, and follow every customer thread it threw off the whole way to its end. Not the first flustered reply. The end. The place where each person either got told it was sorted or quietly went and decided you could not be relied on. Count how many got a different story from how many, and count how many you never once went back to tell that the thing was fixed. Most owners doing this honestly for the first time find at least one Orla in there, one grand-when-it-works they never saw coming, and it stings, but it is the cheapest lesson you will get all year and it costs you nothing but an evening. That much you can do this very night your own self. And if what you find is that the breaking was never really the problem, that the leaving-people-in-the-dark was, then that is roughly the point where holding the whole of it inside two heads stops being sensible, and you can put Maxdesk on the mailbox you already have and watch it work against your own real threads inside a few minutes, which is a more honest test of whether any of this is for you than reading another page about it would ever be.