An internal help desk is IT support whose requesters are a company's own employees, not customers. It runs on company accounts and internal priorities, with no client billing. The recommended setup is one support address, a portal, and a ticket queue, answered by your technicians, an MSP, or both.
Below: how it differs from customer support and an MSP's helpdesk, five ways to staff one, and the six parts it needs. It comes from the team behind SherpaDesk, a helpdesk and professional services automation (PSA) tool a small IT team can run alone. The week-by-week rollout belongs in a separate plan; this guide covers what you're building.
Key takeaways
Definition
An internal helpdesk is IT support whose requesters are the company's own employees. Your own technicians, an MSP, or both can answer it. What makes it internal is who asks, not who answers.
The U.S. Bureau of Labor Statistics lists computer user support specialists, "also called help-desk technicians," as the people who give technical help to computer users outside IT. Their listed duties include documenting the problem as the user describes it, guiding the user through the fix, installing new hardware or software, and training users on it.
What makes the desk internal is who's on the other end. Every requester is a coworker with a company account, a manager, and a device you probably issued. The helpdesk can use your directory instead of asking strangers to register.
In a small company, the internal helpdesk may be one administrator with a shared mailbox, or two or three technicians splitting the work.
One r/sysadmin member works IT at a 125-person law firm. In their words, "the 4 of us act as ticket agents distributing the workload (plus one other agent for facilities issues)."
IT owns the desk there, and a neighbor team uses it too. If you're starting from scratch, start with IT alone and add facilities once the queue habit sticks.
An external helpdesk answers people outside the company: a software vendor's customer support team, or an MSP's own client-facing desk. The tickets look alike, but almost everything around them changes.
Perspective matters. If an MSP answers your employees, the desk is still internal from your company's view, because of who asks. To the MSP, the same desk is one of its client desks.
| Question | Internal helpdesk | Customer support helpdesk | An MSP's client-facing helpdesk |
|---|---|---|---|
| Who asks | Your own employees | Customers of your product | Your clients' employees |
| How you know them | Company directory, single sign-on | Customer account or email address | Contact list per client |
| What "done" means | The employee can work again | The customer's request is resolved | The client's issue is fixed within the contract |
| Money on the ticket | None; maybe a cost-center report | None per ticket; support is part of the product | Time billed to the client or drawn from a contract |
| Who sets priorities | Your managers and your own impact rules | Your support policy and customer plans | The service agreement with each client |
| Answers visible to | All staff, or one department | The public or logged-in customers | One client at a time |
The practical difference is where responsibility stops. An MSP works inside each client's contract: what it covers, when, and at what rate. An in-house team works to the scope its company sets, such as which systems and hours it covers.
One r/sysadmin member weighed a move from an MSP to an in-house job. From their own experience: "I implement in the MSP world but I never own it and it belongs to someone else."
Money follows the same line: an internal helpdesk has no client billing.
The service desk, a broader ITSM function, is a separate question.
Without a helpdesk, requests arrive by email, chat, a text at 7 p.m., and a coworker at your door. Each is a promise you have to remember; a queue turns them into a list someone can see.
The pain shows up first when a second person joins IT. A form and a spreadsheet can work for one admin.
One r/sysadmin member who ran a school's support that way wrote: "As a single IT person - it worked great and I loved it." Then came the catch: "Once you add more Admins to "manage" the tickets (I use the word loosely as you're looking at excel rows), it quickly becomes a nightmare."
A company can reach 80 to 100 people without a ticketing system. One r/sysadmin member took over as solo sysadmin at a company that size and found that "the previous admin did not implement a ticketing system for the users."
A helpdesk also gives you a record when something goes wrong. Attackers have posed as employees to get helpdesk staff to reset passwords. A ticket shows who asked and who approved the reset; our Helpdesk Best Practices guide covers the check itself.
It also shows patterns.
Telling team members and managers about major problems and users' recurring concerns is part of the job description. Ten tickets about the same VPN error make that case for you. Ten hallway conversations don't.
Ten tickets about the same VPN error make that case for you. Ten hallway conversations don't.
Small companies staff an internal helpdesk in one of five ways. The model decides who answers first and where the hard tickets go.
| Model | First answer | Hard tickets go to | Breaks when |
|---|---|---|---|
| Solo admin | The one IT person | The same person, or the software vendor's support | That person is on leave, and the queue is the only memory |
| Small IT team | Whichever of two to five technicians is free | The technician who owns that system | Everyone works the easy tickets first |
| Shared desk | IT, facilities, HR, or operations, each from its own queue | The team that owns the queue | Confidential HR cases sit where technicians can read them |
| Co-managed | Internal IT | An MSP, for network, security, or after-hours work | The two queues have no clear hand-off |
| Fully outsourced | An MSP's helpdesk, for companies with no IT staff | The MSP, under its contract | A request falls outside the contract |
Inside each model, tickets still move up by difficulty. A password reset stays with whoever answers first. A server outage goes to the person who runs the servers, or to the MSP.
The shared desk deserves a caution. Any department that takes incoming requests can use the same queue habit, but not every request belongs in an IT tool. Keep confidential cases, such as employee-relations complaints, where only HR can read them.
These six parts are the recommended setup for an internal helpdesk, scaled to your size. A solo admin can start with one shared mailbox and a page of rules, and add the portal and forms later. Roles and permissions touch every other part, so decide them early.
Pick one address, such as help@ or it@, and print it everywhere. In Microsoft 365, a shared mailbox is built for support addresses, but it supports a maximum of 25 users, and you can't stop members from deleting messages. In Google Workspace, a collaborative inbox lets members assign a conversation and mark it complete.
When you move to ticketing software, the address forwards to it. Microsoft 365 can block that external forward, so check that setting before you switch.
Common mistake: keeping a technician's personal address as a second route. Every request needs to land in the same queue.
A portal answers "where's my request" and "how do I fix this myself." Employees sign in with the accounts they already have, see their own tickets, and read your written fixes.
Start the knowledge base with the five fixes you repeat most, written from real tickets.
Common mistake: letting anyone with an email address register. Limit sign-up to your company's domain.
Forms collect the facts you'd otherwise chase by email: which device, which app, who approved the access. Keep it to five to eight request types an employee can tell apart, such as "Can't sign in," "Need access," "New hardware," and "Something's broken."
Common mistake: 20 categories on day one. Employees pick "Other," and your reports become useless.
Start with one IT queue. Add a second only when a different person works it, such as facilities, or the MSP for network tickets. Route by request type, so "New hardware" reaches whoever orders laptops without anyone forwarding it.
Common mistake: an unassigned pile everyone can see and nobody owns. Name who sorts new tickets each day.
Four roles cover a small internal helpdesk. Requesters are every employee, and technicians work tickets.
An administrator changes forms, queues, and permissions. Approvers are managers who sign off on access and purchases. Write the backup for each technician next to their name.
For who owns which systems on a small team, use the responsibility matrix in IT Department Structure.
Common mistake: making the only technician the only administrator. When they're out, nobody can fix a routing rule.
One page is enough: support hours, what counts as urgent, how fast you reply at each priority, and what to do after hours. Add the identity check for password and multi-factor resets. Keep the rest of your help desk management rules, from priorities to that check, on the same page.
Common mistake: promising response times you meet only on a quiet week. Start loose and tighten after a month of data.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Say you run IT at a 90-person engineering firm. It's you, one junior technician, and an MSP that handles the firewall and after-hours alerts.
Today, requests come by email to you, by chat to the junior, and in person to whoever is closer.
| Part | What this firm sets up |
|---|---|
| Address | help@ forwards to the ticketing tool; both personal addresses stop taking requests |
| Portal and sign-in | Employees sign in with their Microsoft 365 accounts; sign-up limited to the firm's domain; six fix articles published |
| Forms | Seven request types: can't sign in, need access, new hardware, software install, something's broken, facilities, and joiner or leaver. HR starts the joiner or leaver request and the employee's manager approves it; the checklist items come from the Employee Offboarding Checklist |
| Queues | IT (you and the junior), Facilities (the office manager), Network (the MSP's contact) |
| Roles | You: administrator and backup for the junior. The junior: your backup on tickets and backup administrator, with admin rights. Department heads approve access requests. The office manager works facilities tickets only |
| Rules | Support 8 a.m. to 6 p.m. "Urgent" means someone can't work: first reply within 1 business hour; everything else the same business day. Can't sign in: call the IT phone line or walk over, and the technician opens the ticket. Resets follow the identity check in Helpdesk Best Practices, linked above; a callback to the directory number is one step of it. After hours: firewall and alert issues go to the MSP; everything else waits for the next business day |
Whether you hire for the helpdesk or give it to your current admin, federal data shows what the role pays.
| Measure | Value |
|---|---|
| Median annual wage, computer user support specialists (helpdesk), May 2025 | $61,860 |
| Median annual wage, computer network support specialists, May 2025 | $76,220 |
| Jobs, computer support specialists, 2025 | 903,100 |
| Projected employment change, 2025–35 | −3% |
| Projected openings per year, average over the decade | 48,700 |
Source: BLS, wages as of May 2025.
Two things follow for a small company. First, the user support wage in that table is the market reference for a full-time helpdesk hire. In our view, if your queue doesn't justify that, give the helpdesk to someone who also runs other IT work.
Second, the BLS expects fewer user support jobs because organizations "continue to implement automated tools, such as chatbots, for troubleshooting." The openings in the table all come from replacing people who leave.
The software is the easy part. The hard part is the coworker who messages you directly because it's faster for them.
In a thread about users who skip the ticketing process, one r/sysadmin member put the rule plainly: "Issues that don't get put into the ticketing system don't get worked."
That doesn't mean the employee has to file every ticket. Every request becomes a ticket, including the ones a technician logs from a call or a hallway conversation. Reply with the ticket number, and the queue becomes the easy path.
Launching an internal helpdesk takes a dated plan, not a project team. This guide covers what the helpdesk is made of. The order and the dates belong in a plan.
Our Helpdesk Implementation Plan has one to copy: setup, the pilot, the switch-over day, a rollback, the announcement, and what to count after 30 days.
No request type for joiners and leavers. New-hire and offboarding requests come from HR or a manager, not the employee. Without their own form and approver, they arrive by email and get missed. The offboarding checklist linked in the example covers both halves.
Copying an MSP's setup. Client accounts, contracts, and billing fields serve an MSP's invoices. An internal helpdesk needs departments, locations, and approvers instead.
One address per department. If employees must choose between it@, facilities@, and hr@, they first have to know which team owns the problem. One address saves them that choice. Route behind it, and send confidential HR requests through their own access rules.
No route for people who are locked out. The employee who can't sign in can't use the portal or email. Name a phone line or a walk-up route for exactly that case.
Treating it as IT's tool only. Help desk operations depend on the rest of the company knowing the address, the hours, and what "urgent" means. Repeat them in onboarding for every new hire.
How this works in SherpaDesk
You can run SherpaDesk as an internal ticketing system for your own staff or as client-facing ticketing for businesses you support. Forward your support address to an email dropbox, and incoming emails become tickets. Each dropbox can route to a technician or a group.
Employees sync nightly from Google or Microsoft 365 and sign in with single sign-on. Active Directory/LDAP setup carries an implementation fee. You can limit portal sign-up to your company's email suffix.
Custom fields attach to a ticket class, so an access request asks only access questions, and technician-only fields stay hidden from employees.
A helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin.
A one-person IT team can start on Single Agent at $0, which includes ticket management and the knowledgebase. Base Camp is $45 per agent per month ($40 billed annually).
The first agent is free, forever, so a two-technician team pays $45 a month ($40 billed annually). Setup takes about 2 minutes; 14 days free, no card.
See Ticket Management → · See SherpaDesk Pricing →
Who this isn't for
Teams whose main job is HR case management, with confidential employee-relations files, are better served by a tool built for HR casework. If you're still comparing tools, start with Best IT Help Desk Software. And you can't install SherpaDesk on your own servers; it runs only in the cloud.
It's the support team, and usually the software, that answers a company's customers about its product or service. It differs from an internal helpdesk in who asks: customers instead of employees.
That changes how you identify people, what you publish, and who sets priorities. See the comparison table.
Typical internal requests are sign-in and password problems, access requests, new or broken hardware, software installs, printers, and network trouble. Track your own request types for a month; your top five tell you which fixes to publish first.
Not entirely, by the federal forecast. The BLS expects fewer user support jobs as organizations use chatbots for troubleshooting. It also says automation may free some user support specialists to handle more complex cases.
Openings continue, all from replacing people who leave; see the staffing table.
It depends on what you want from it. The staffing table has the federal pay and outlook figures: network support pays more at the median than user support, and total jobs are projected to shrink over the decade. On an internal helpdesk, problems from every system reach you first, so you see the whole stack.
It takes every request, records it as a ticket, and fixes what it can. The rest goes to the person or vendor who owns that system. Then it tells the requester what happened.
The BLS also lists informing team members and managers about major problems and recurring concerns. On an internal helpdesk, that report is how leadership sees where IT time goes.
A helpdesk technician is a computer user support specialist, in the BLS's terms: the person who helps non-IT users with computer problems. Beyond the duties in the definition section, the BLS lists diagnosing the cause and setting up or repairing equipment.
Facilities usually can: a broken door lock and a broken printer travel the same route, in separate queues. HR is different.
Keep confidential cases, such as complaints or medical leave, in a place only HR can read. Share the address and portal if you like, but not the case files.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.