.svg)
What an employee help desk is
An employee help desk is the single place staff go for anything they need from the teams that support them: HR, IT, facilities and the rest. They find answers, send requests and follow them to done, without needing to know which department owns the question.
Five days in the shoes of one of your employees
Kestrel Diagnostics runs clinical testing labs, with about 1,100 people spread across a Denver head office and three labs in Colorado and Utah. Priya is a lab coordinator at the Salt Lake City lab. She has plenty to track, and which team owns what isn't part of it.
Monday, 7:50 am: her place, her building
Priya signs in with her usual company login. Her home page shows the benefits enrollment window that opened today, a note that the Salt Lake City parking lot is being repaved on Thursday, and her three open requests in one list, whether they sit with HR, IT or facilities.
10:30 am: an answer she can trust
An auditor is visiting next week. Priya asks the portal how to get a visitor badge for the lab floor. The reply comes from facilities' own visitor page for her building, linked underneath: badges need two days' notice. She books it before lunch.
Tuesday, 3:15 pm: sorted in five minutes
Her payslip isn't where she expected it. She types "where is my payslip" and the top result is payroll's step-by-step guide, with pictures of the exact screens. She finds it, downloads it and sends it to her landlord.
Wednesday, 9:05 am: one message, two teams, zero retelling
Priya moved to the microbiology team last week, and her badge still won't open the micro lab. She has no idea whether that's security, facilities or HR, and she doesn't need one. She writes it in Microsoft Teams. It lands with facilities, who see that badge access follows her team in the HR record, which still shows her old one. Facilities passes it to HR with a note explaining exactly that. HR fixes the record, facilities reissues the access, and Priya gets one reply in Teams. She was asked nothing twice.
Thursday, 1:20 pm: a desk move in a single form
Priya is moving to a desk inside the micro lab. One form asks for her new spot, equipment and date. The desk and chair go to facilities, the phone and network port go to IT, and her portal shows both halves progressing under one request.
Friday: the people behind it look at the week
Kestrel's shared services lead reviews searches that found nothing. Parking during the repaving tops the list. Facilities writes one page that afternoon.
What your employees can do
Open a home page that fits them
The home page is personalized to where someone works, their team, role and employment type. Lab staff see lab safety and badge pages. Office staff see desk booking. A notice about one building shows up only for the people in it.
Get answers without knowing who owns them
People ask as they would ask a colleague. The reply comes from whichever team's approved pages cover it, HR, IT, facilities or finance, with the page linked. One search covers the whole company.
Take care of the everyday things
Guides walk people through what they can do alone, like finding a payslip, booking a room or setting up a new phone.
Ask once, wherever they are
From Slack, Microsoft Teams, email or the portal, a request goes to the team that owns it. If it belongs somewhere else, it moves with everything the employee said and tried.
Follow every request in one list
Every open request shows its status and who has it, whichever team is working on it, and requests with several parts show each one.
What your support teams get
HR, IT, facilities and finance each get their own queues in one shared inbox, so each team works its own way while the whole company has a single front door. Anyone can pass a request to another team with an internal note the employee doesn't see. Approvals, like a manager's yes on a desk move, sit inside the request. Automations send each form's parts to the right queue. Reports show where requests wait and what employees couldn't find.
What changes when every team shares one front door
Nobody sends a request to the wrong department again. Employees describe the problem, and routing, not guesswork, decides which team picks it up.
Hand-offs between teams stop costing a day. A request moves between HR, IT and facilities with its history and notes, so the next team starts where the last one stopped.
Employees get answers after hours, in the app they already use. Every team's approved pages answer them in Slack, Teams, email or the portal, day or night.
Each team writes its answers once. A page HR, IT or facilities publishes is what search, the assistant and every colleague use from then on.
You see the whole picture of employee support. One set of reports covers every team instead of three tools that never compare notes.
People and AI, sharing the work
The assistant replies from the pages each team has approved and names its source. A question that needs a person is routed to the right team's queue with the whole conversation. What it's permitted to do, like opening a request for someone, is your call, and a log records each step. Every team stays in charge of its own answers.
How to build your employee help desk
- Bring in each team's pages. Connect what HR, IT and facilities already keep in SharePoint, Confluence, Google Drive or Notion, or create pages from scratch. Tag each by team, location and role.
- Connect your people. Employees sign in with the company login they already have, and their accounts come across with location, team and manager, so each portal fits the person.
- Set up a queue for each team. Create queues for HR, IT, facilities and finance, and decide who works each one.
- Build forms that split the work. Make forms for common requests, with approvals where needed, and route every part to whoever handles it.
- Open your channels. Add Slack, Microsoft Teams and a single support email address, all feeding the same inbox.
- Add the assistant and launch. Point it at approved pages, set what it may do, then start with one location before rolling out.
Fits the tools every team already runs
Slack and Microsoft Teams for day-to-day questions, email for people who aren't in either, SharePoint, Confluence, Google Drive, OneDrive and Notion for each team's existing pages, and single sign-on with user provisioning. For the systems HR, IT and facilities each run, there are webhooks, an open API and an MCP server.
Related
- IT help desk portal when you're starting with IT alone
- AI HR assistant for leave, benefits and policy questions
- IT self-service portal for software, hardware and access requests
- Running customer, partner and employee help on one platform
- A help desk implementation guide
- Employee enablement and support
| Employee help desk on MatrixFlows | A separate tool for each team | |
|---|---|---|
| Where employees go | One portal, plus Slack, Microsoft Teams and email | An IT portal, an HR inbox and a facilities email address |
| Choosing the team | Employees describe the problem and routing does the rest | Employees guess, and a wrong guess sits unnoticed |
| When a request crosses teams | It moves with its history and internal notes | The employee explains it again to the next team |
| Finding answers | One search across every team's approved pages, with sources | Each team's articles live in its own tool |
| Requests with several parts | One form, split to each team, tracked as one request | Separate tickets in separate systems |
| Knowing what's happening | Every open request and owner in one list | Follow-up emails to whoever might know |
| Seeing the whole picture | Reports across every team, including unanswered searches | Each team reports on its own slice |
A shared front door for HR, IT and facilities is employee operations run on MatrixFlows. Customer service and partner programs can sit on that platform with it.