What is the difference between a shared mailbox and a service desk?
A shared mailbox holds the message. A service desk holds the commitment.
Three people watching one inbox works right up until the day it doesn't. Someone replies and nobody knows. Someone doesn't and everyone assumes someone did. There is no reference to quote, no owner to ask, and no record of what you promised or when.
A service desk gives every request a reference, an owner and a clock. It knows which service is affected, which contract covers it, and how long you have left. When a customer asks for an update, the record answers rather than a person guessing.
This page is the companion to our eight-week Helpdesk run. Over those weeks we work through what a desk needs, one piece at a time, and the checklist below is the short version you can keep.
What the desk does today
Deployed and in use, not on a roadmap.
Tickets and SLA
INC- for something broken, SR- for something asked for. Priority from an impact and urgency matrix, with an override when you know better.
- First response and resolution timers
- Business hours or 24 by 7
- Timers pause on the statuses you choose
- Breach monitoring that runs on its own
Assets and the CMDB
Every asset with a reference, an owner company and relationships to the things it depends on.
- Warranty and end of life dates
- Backup policy and audit log
- Devices promoted from your integrations
- A daily SSL check that raises its own ticket
Security operations
Alerts from your security tooling become tickets with the normal SLA and assignment, not log lines in a console nobody opens.
- MITRE kill chain and affected asset
- AI triage assessment on convert
- Isolate, quarantine and scan from the ticket
- Every action written to the timeline
And the parts people forget until they need them
Email in, ticket out
A watched mailbox turns email into tickets, matches the requester to the company record, and threads every reply onto the same conversation.
Customer portal and CSAT
A login per company. Their tickets, their assets, their knowledge base. A tokenised satisfaction link on close, scored back onto the ticket.
Runbooks and a credential vault
The steps for the jobs you repeat, recorded per execution. Credentials encrypted at field level, with every reveal logged against a user and an IP.
Major incidents
Promote a ticket to a P1 and it gets its own lifecycle, its own timeline and a public status page your customers can read instead of ringing you.
Changes, CAB and problems
Approval chains from your own policy, deployment windows with a rollback plan, post implementation review, and a known error database behind it all.
AI assist
Ticket summary, reply draft in a tone you pick, resolution suggestions from tickets you have already closed, and a flag when the answer was never written down.
The shared mailbox, honestly compared
Most desks start in an inbox. Here is what changes when they stop.
| Chorum Helpdesk | A shared mailbox | |
|---|---|---|
| A reference to quote | ||
| One named owner per request | ||
| First response and resolution timers | ||
| Counts working hours, not wall clock | ||
| Priority from impact and urgency | By whoever shouts | |
| Customers can see their own tickets | ||
| Asset register beside the ticket | ||
| Audit trail of who did what | Sent items, if nobody deleted it |
What we cover over the eight weeks
One theme a week, three posts a week, on LinkedIn and X.
- The difference between a shared inbox and a service desk
- An SLA that counts your working day rather than the calendar
- Email in, ticket out, and nothing filed by hand
- The customer portal, and finding out how you are doing from your customers
- The CMDB, and the certificate that expires on a Sunday
- Runbooks, and getting the password out of the spreadsheet
- Major incidents, changes and CAB
- AI assist and the security operations panel
Follow along, or take the checklist and skip to the end.
Questions people ask before they switch
Start a 14-day trial of Chorum Helpdesk
No card required. UK data residency. Cancel whenever you like.