Joanna’s first Monday at the surveyors begins at ten to nine at the front desk, where there is no pass with her name on it. It carries on upstairs at a desk with a laptop still in its box, which would be no use to her anyway, since nobody has gone and made her an account. By the Thursday she has asked three different people why she is missing from payroll. That week is what an internal help desk is for. It is the one place staff write to when they need HR, IT or facilities, where each request lands with a named owner and stays on the record until it is done, whichever of the three teams it ends up with.
Most companies of a hundred-odd people have the three teams already, mind you, each with its own address and its own habits, and each one decent enough at answering its own mail. The requests that go missing are the ones needing two of them. A new person starting is the commonest of those by some distance, and Joanna’s start had gone wrong three weeks before she ever reached reception.
Why does a new starter’s first Monday go wrong
Go back to the Tuesday she accepted the offer. Bridget in HR sent the contract out that afternoon and put the start date into the new-starters spreadsheet, which lives on SharePoint and is kept properly, as it goes, every column filled in. Nobody in IT opens it. Facilities do not know it exists. On the Thursday before the Monday, Bridget went and forwarded the whole offer thread to Callum. Callum is the IT department at the surveyors, all of him, and the line on top asked could he have a laptop ready for the start.
Callum was off that Friday. He read the mail at half nine on the Monday, by which point Joanna had been in the meeting room for forty minutes with a coffee and nothing to log into. A laptop of the spec they buy takes about 10 working days to come from their supplier. So what sat in the box was the spare, and a spare wants a good afternoon of updates before it is any use to anybody. Her Microsoft 365 account went live at eleven.
Facilities never got a mail at all, funnily enough. Phil, who looks after the building and the post room and the door passes, heard there was somebody new from the receptionist at ten to nine, with Joanna standing there in her coat. He went and had a pass printed by quarter past ten, which was quick going. Payroll was a separate road again. The starter form reached the payroll clerk two days after the cut-off for that month’s run, on account of it sitting in Bridget’s drafts while she waited on a sort code. Her first pay came a month late.
Look at the whole of it from above and nobody behaved badly. Each of the four had a system that worked for their own bit. What failed was the handover, a forwarded mail that landed on somebody’s day off and a word in reception standing in for a request. It failed because the handover its self was nobody’s job in particular, so it got done whenever somebody happened to remember.
What does a month of staff email look like once somebody counts it
Here are four weeks of staff mail at the surveyors, 140 people across two offices, invented for this page but counted the way you would go and count your own, one address at a time.
IT had the most, 212 mails. The bulk of it was what you would guess, passwords and the VPN and a printer on the second floor that jams when anybody looks at it sideways. There was a run of SSO lockouts as well, on the Tuesday after a policy change nobody had warned staff about. Facilities had 88. Heating, a leak over the kitchen in the smaller office, desk moves, and a steady trickle of parcels somebody wanted bringing up. HR got 131. The greater part of those came in the three days after payday, when people open their payslip and find a question in it, along with holiday balances and a handful of letters confirming somebody’s salary for a mortgage.
That makes 431. Now count only the ones that needed a second team before they could be called finished. At the surveyors there were 37 of them. Six new starters and four leavers to begin with, then a team of nine moving floors, and a monitor arm that IT thought was furniture while Phil was sure it was IT, and the rest of it smaller things of the same sort. That comes to about 9% of the month, which does not sound like a great deal.
Over the same four weeks the managing partner had 14 complaints about things not getting done, and that is the number anybody in a company actually notices, far more than any count of mails. Eleven of the 14 traced back to one of the 37. So nearly four in every five complaints came out of less than a tenth of the mail, and every one of those eleven had started in one team’s inbox and needed finishing in another’s.
The leavers worry us more than the starters, truth be told, even though they make less noise. A starter left waiting complains, loudly, on the first morning. A leaver’s door pass that goes on opening the side entrance for weeks after their last day bothers nobody at all. Nobody is about to notice, since the person it belonged to has gone. At the surveyors, two of the four leavers that month still had working passes when Phil went down the list at the end of it.
Which requests go to which team, and which stay out of the desk
| Request | Address staff write to | Team that owns it | Second team needed | Keep it in the desk |
|---|---|---|---|---|
| Password reset or locked account | it@ | IT | None | Yes |
| New laptop, phone or software | it@ | IT | Finance, if it needs signing off | Yes |
| VPN, Wi-Fi or printer fault | it@ | IT | None | Yes |
| Heating, lighting or a leak | facilities@ | Facilities | None | Yes |
| Desk or office move | facilities@ | Facilities | IT, for the dock, phone and network point | Yes |
| Meeting room screen or video kit | it@ | Agree one owner before go-live; IT is usual | Often facilities | Yes |
| Payslip or pay query | hr@ | HR (payroll) | None | Yes |
| Holiday balance or policy question | hr@ | HR | None | Yes |
| Letter confirming employment or salary | hr@ | HR | None | Yes |
| New starter | Sent by HR to it@, facilities@ and hr@, subject “New starter” | HR keeps it; IT and facilities own their parts | IT and facilities, 15 working days ahead | Yes, the request; not the documents |
| Leaver | Sent by HR to it@, facilities@ and hr@, subject “Leaver” | HR keeps it; IT and facilities own their parts | IT and facilities, on the day notice is given | Yes |
| Right-to-work documents and passport scans | None | HR’s own records | None | No |
| Grievance, disciplinary or medical matter | A private HR address off the desk | HR manager | None | No |
Meeting room screens get argued over at the surveyors and nearly everywhere else, on account of being a bit IT and a bit furniture. Settle who owns them before the desk goes live, mind you, rather than on the morning one goes blank ten minutes before a client walks in.
Anything needing a second team still wants one owner the whole way through, and at the surveyors that is whoever the mail reached first. Bridget keeps a starter on her own name until the Monday has gone off properly, laptop and pass included, even though she does none of the setting up her own self. The reason is plain enough. Hand a request over outright and both teams can go on believing the other one has it for a good long while, and the person waiting on it has no idea which of them to chase.
Should HR, IT and facilities share one desk or have one each
There is a fair case for giving each team a desk of its own, three desks, and the person making it is usually in HR. Their mail is more private than anybody else’s. Their busy days fall in a different week of the month too, payday and the days after it, and the thought of IT being able to scroll through payslip queries is enough to end the conversation before it has properly started. All of that is reasonable. Most of it is answered by how one desk gets set up, though, rather than by building three.
What three separate desks cannot do is carry a request across from one team to another. Joanna’s start would go back to being a forwarded email between HR’s desk and IT’s, which is the thing that went wrong in the first place, only now with a ticket number on either end. One desk with three groups inside it can pass a request from HR to IT with its history still attached and an owner still named.
Price has a habit of deciding this before anybody argues it out, mind you. An internal desk at a company that size has a long tail of people who answer now and then. The payroll clerk busy three days a month is one of them. So is the office manager at the second site, and the receptionist who logs the parcels, and there is the IT contractor too, who only comes in on Wednesdays. At the surveyors that came to nine people, and only three of them answer mail every day. A desk priced per person makes you pick which of the nine are worth a login, and the ones left off carry on answering from their own Outlook or Gmail, so the payslip answer the clerk sent from home on a Sunday sits in nobody’s record but hers. We went through what each way of charging ends up rationing when we wrote about help desk pricing models.
Who gets to see HR’s mail
Bridget’s forward to Callum had the whole offer thread underneath it, the salary in there and the notice period at Joanna’s last job and a line from her about why she was keen to leave it, all of it sitting under the one line Bridget had typed on top about a laptop for the Monday. Callum needed her name, her start date and which team she was joining. He got the rest as well, sitting in his own inbox, where it will stay until he goes and deletes it, which nobody ever quite gets round to. He never asked for any of it.
On a shared desk that forward never needs sending. Each team works inside its own group, and each person can be held to the tickets of one group, so Callum sees IT’s requests and Phil the building’s, and that gets set person by person rather than team by team. Neither of them sees a thing that came in to hr@, which is how Bridget wanted it. The starter request IT gets is a ticket of its own, written for IT, carrying the name and the date and the kit and nothing about money.
The admin role is the part HR should ask about before anything goes live. Whoever holds it sees the whole desk, HR included, and at a company of 140 the admin is very often the IT person, on account of being the one who set the thing up. At the surveyors they gave the admin role to Bridget and the office manager and kept Callum on an IT-only role. That suited him fine, to be honest with you, since the last thing he wanted was to be reading the payroll mail his own self.
Some HR mail should never go near the desk at all. Grievances and disciplinary matters belong in HR’s own records, and anything medical is special category data under Article 9 of the GDPR, which wants a narrower home than a queue. Right-to-work documents carry rules of their own. In the UK the Home Office expects copies kept for as long as somebody works for you and 2 years after they leave. In the US the Form I-9 is kept for 3 years after the hire date or 1 year after the job ends, whichever comes later. A help desk ticket is the wrong sort of home for every one of those, no two ways about it, and a longer retention period would not change that. The surveyors gave staff a second HR address for confidential matters that only Bridget reads, in her own mailbox, and kept hr@ on the desk for the everyday questions about pay and holidays and letters.
How does a new starter get through three teams without falling between them
Count back from the first Monday. The laptop needs 10 working days if it has to be ordered. A pass cannot be printed without a photo, so somebody has to go and ask the new person for one, and payroll wants the form in by the 15th to make that month’s run. Put those together and all three teams want to know about a start roughly three weeks before it, and in the counted month IT heard that early for only 2 of the 6 starters.
So the request has to leave HR the day the offer is accepted, in a shape nobody can misread. At the surveyors Bridget now sends three short mails off a saved template, to it@ and facilities@ and to hr@ its self, each with a subject reading New starter, then the person’s name, then the start date. Callum’s lists the team, the kit and the systems they need into, Microsoft 365 and the drawing software and the shared drive, and leaves pay and contract out of it. Phil gets a shorter one asking for a pass and a desk and a locker, with the photo following once she has it, and the copy to hr@ stays on Bridget’s name with the payroll form attached, so HR’s part sits on the desk beside the other two. Leavers go the very same way, with Leaver at the front, sent the day notice is handed in rather than in the last week. That gives Callum time to switch the accounts off in Active Directory on the last afternoon, and Phil to cancel the pass the same hour.
We would normally tell you not to trust a subject line for routing, since people reply to old mail with brand new questions in it, and our page on ticket routing rules goes into that at length. This is the exception we make. HR writes these subjects, always in the same words, so a rule looking for New starter at the front of a subject is matching words HR put there on purpose. That rule puts a starter tag on the request and bumps its priority up, which keeps it from sitting under a pile of printer faults in the IT queue on a Monday morning.
Searching the person’s name then brings up all three requests side by side, HR’s own included for whoever is allowed to see it. Bridget checks on the Wednesday before a start and again on the Friday. The next person to start after Joanna had a pass waiting in reception and an account behind the laptop, with pay arriving on the right date at the end of her first month. None of it rested on Callum being in that Friday, or on Phil happening to walk past reception at the right minute.
Where does Maxdesk come into it
Over here at Maxdesk, the made-up surveyors took most of a Tuesday afternoon to set it all up, the better part of it spent arguing about the meeting room screens. They made one workspace and pointed hr@, it@ and facilities@ at it, and made a group for each team. Then they wrote one rule per address, sending each mail to the group it was addressed to, and the starter and leaver rules went on after. On Microsoft 365 the admin had to allow forwarding to an outside address first, since that has been switched off by default for a few years now, and finding the setting cost them half an hour of the Tuesday on its own. Staff went in as requesters rather than customers, the same desk with your own colleagues doing the writing in, and the lot of it was answering mail by the Wednesday morning.
Each of the nine got a login. Callum and the Wednesday contractor were held to the IT group’s tickets, and Phil and the receptionist to the building’s. Bridget and the payroll clerk got HR’s. The managing partner went in on a read-only login, so she could look without replying to anybody. When nobody’s role fitted the office manager at the second site, the permission matrix let them build one that can answer mail but cannot delete a ticket or invite anybody in. Priorities each carry an SLA target, so a heating failure in January gets treated like the emergency it is and a holiday-balance question waits its turn, which the person asking rarely minds. Callum leaves internal notes on a ticket for Phil about which floor box a moved desk needs, and the person who asked for the move never sees them, which saves a fair bit of explaining. Every change lands in the audit trail with a name and a time on it, which on an internal desk earns its keep the first time a leaver’s pass is still working and somebody asks who was told and when.
The payslip questions were the quickest win of the lot, funnily enough. Bridget wrote one reply as a template, covering which day payslips appear and where to find them and who to ask about a tax code. The three days after payday went from most of her week down to a couple of hours of it. The longer answers, the VPN on a home router and how the holiday year runs, went into the knowledge base, so a reply can point to them instead of typing them out again.
Our bill goes to the workspace, whatever number of people sit in it, so nine logins cost what two would have, read-only one included. If you came here from the IT side, our page on the IT ticketing system covers that half in far more depth than this one does. Anybody weighing the whole of it against a full service desk will find that difference gone through in our piece on the service desk.
The parts of an internal desk we leave to somebody else
A good share of what staff ask IT never arrives as email at all. It comes as a message on Teams or Slack, or a head round the door, and we take email and nothing else, so none of that reaches the desk unless somebody sends it there. Callum got into the habit of answering the Teams ones with a short line asking for it to come to it@, which annoyed people for about a fortnight and then stopped annoying them. There is no portal either, nowhere for staff to sign in and fill out a form, and a company that wants every request arriving as a form should look elsewhere.
A new laptop that needs a yes from the finance director gets that yes as a reply or an internal note, typed by hand, since the desk has no approval step, and nothing in it stops somebody in IT who goes and orders before the yes has come. Who has which laptop is a question for wherever you kept the answer before, a spreadsheet on Google Drive or SharePoint more often than not, because we keep no asset register and the desk its self has no idea. Nor is any of this an HR system. Maxdesk holds no employee records and no case files, which is part of why the grievances and the passport scans stay out.
The free workspace keeps 3 months of history, rolling from each ticket’s last activity, and a paid plan stretches it, to 12 months on Pro or 24 on Elite. For the everyday mail that is usually plenty. It falls short all the same for the question of what was agreed with a leaver last spring, so a company expecting to answer that sort of thing from the desk is better off paying from the first month than discovering the gap the week it matters. The free workspace also shows ads to the people working in it, never to the staff writing in, and it limits the number of rules running at once, so count the surveyors’ five against that limit before you build them.
A first count you can do with last month’s mail
Before building anything, open last month in the three inboxes, it@ and hr@ and facilities@ or whatever yours go by the name of. Export it to a CSV if your mail will let you, whether it runs on Microsoft 365 or Google Workspace, and go and work down the lot with a pen. Put a mark beside every mail that needed a second team before it was finished. Then put a second mark beside every complaint you heard about that month and see which of them line up with the first. It takes a morning, near enough. Most of the morning goes on the arguments over whose a thing was.
If your count comes out anything like the surveyors’ 37, those are the requests to set up for first, starters and leavers above all, and the address rules can wait until the week after. A free workspace takes a minute or so to make, with every person who answers mail in it from day one. Point one of your three addresses at it for a fortnight, facilities@ say, since it is usually the quietest, and watch the whole of it run on your own mail.
Common questions about internal help desks
What is an internal help desk?
An internal help desk is a single place where employees send requests to internal teams such as IT, HR and facilities, so each request gets a named owner, a priority and a record until it is resolved. It works like a customer help desk, except the people writing in are your own staff.
What is the difference between an internal help desk and a service desk?
The terms overlap. A service desk usually means an IT-led function built around ITIL practices such as incident, change and service request management, often run on an ITSM tool with an asset register alongside it. An internal help desk is the broader and simpler idea: one queue that several internal teams answer, IT among them.
Can HR use the same help desk as IT?
Yes, if the desk can limit who sees what. Put HR in its own group, hold IT and facilities staff to their own groups’ tickets, and check who holds the admin role, since admins can usually see everything. Keep grievances, disciplinary and medical matters out of the desk entirely.
Should HR, IT and facilities use one help desk or three?
One desk with a group per team usually works better, because the requests that cause the most trouble, such as new starters, leavers and office moves, need two or three teams. Separate desks turn each of those handovers back into a forwarded email.
What should not go into an internal help desk?
Grievances, disciplinary cases, medical information and right-to-work documents. Health data is special category data under Article 9 of the GDPR, and right-to-work copies have their own retention rules: in the UK, the length of employment plus 2 years; for the US Form I-9, 3 years after hire or 1 year after employment ends, whichever is later.
Do staff need a portal to raise internal requests?
Not necessarily. Every employee already has a work email address and uses it to ask for things, so an email-based desk with addresses such as it@, hr@ and facilities@ catches most requests. A portal earns its place when requests need structured forms or approvals.
Product details reviewed on 13 October 2026 against the live Maxdesk site. The surveyors and their month of mail are made up for the example. Retention periods are from UK Home Office right-to-work guidance and USCIS Form I-9 guidance; special category data is defined in Article 9 of the GDPR.