How-To · May 3, 2026
Setting Up an IT Helpdesk for Under $0
Most small IT teams run on Slack DMs and a shared inbox. It works until it doesn\'t. This guide walks through a 5-phase setup that gives you tickets, SLAs, routing, and asset tracking using a free helpdesk — no ServiceNow contract required.
A working internal IT helpdesk takes one week to set up: a single intake email, 5 categories, 3 priority tiers with realistic SLAs, routing rules mapped to your team, and a one-paragraph rollout to the company. For a small team (under 50 employees), all of this fits inside a free plan — no enterprise tool, no implementation services, no four-figure monthly bill.
Why most internal IT setups fail
If your IT team is drowning in requests but has no idea how many or what type, you\'re not alone. Four patterns cause it.
Requests scattered across Slack, email, and DMs
Without one intake point, half your tickets never become tickets. You can't measure what you can't see.
No priority system, so everything is "urgent"
When all tickets feel critical, real P1s wait behind cosmetic asks. A simple 3-tier priority list fixes this in an afternoon.
Hero culture instead of process
One person knows where everything is and how to fix it. That works until they're on vacation. Document the top 10 fixes as KB articles before the next incident.
Tools priced for enterprise
ServiceNow, Jira Service Management, and BMC Helix all start in the four-figure-monthly range. For a 50-person company, that's overkill — and the setup cost rivals the license cost.
The 5-phase setup (one phase per day)
This is the playbook small IT teams use to go from chaos to a working helpdesk in five focused days. Each phase is one day; each step is a concrete action you can finish in under two hours.
Phase 1 — Inbox
Day 1- Pick a single intake address (e.g. it-help@yourcompany.com)
- Forward existing IT requests from Slack channels and 1:1 DMs to that address
- Connect the inbox to your helpdesk so every email becomes a ticket
- Disable the "we got it" auto-reply for the first week — it adds noise while you debug routing
Phase 2 — Categories
Day 2- Define 5 categories: Access, Hardware, Software, Network, Other
- Add a tag for each category in your helpdesk
- Tag the last 50 tickets manually so you can see the real distribution
- Set up auto-tagging for obvious keywords ("VPN" → Network, "laptop" → Hardware)
Phase 3 — SLAs
Day 3- Define 3 priority levels: P1 (production down), P2 (impacts work today), P3 (request, not blocker)
- Set realistic targets: P1 first response ≤30 min · P2 ≤4 hours · P3 ≤24 hours
- Wire up breach alerts to a Slack channel or your phone
- Document the priority definitions so requesters can self-classify in the form
Phase 4 — Routing
Day 4- Map categories to people: Network → infra lead, Software → IT generalist, etc.
- Set up a default assignee for unrouted tickets so nothing sits in limbo
- If your team rotates on-call, configure round-robin assignment for P1s
- Add an escalation rule: any P1 unanswered for 15 min auto-pages the on-call
Phase 5 — Rollout
Day 5- Send a one-paragraph announcement to the company with the email address and SLA expectations
- Replace the IT Slack channel topic with the new email address and a "use the form for tracking" note
- Publish 3 starter knowledge-base articles for the top requests (password reset, VPN, MFA)
- Schedule a 30-day review to look at category distribution and SLA hit rates
How FyneDesk handles this
Every step here uses features on the free plan: email-to-ticket, custom categories and tags, SLA configuration with breach alerts, round-robin routing, knowledge base, and asset management. Setup is documented; no professional services call required.
Realistic SLA table for a small IT team
Use this as a starting point. Adjust based on your business hours, on-call coverage, and how badly each category hurts when it\'s broken.
| Example request | Priority | First response | Resolution |
|---|---|---|---|
| Production system down (email, payroll, customer-facing app) | P1 | ≤ 30 min | ≤ 4 hours |
| Cannot log in (account, MFA, VPN) | P2 | ≤ 4 hours | ≤ 1 business day |
| Hardware issue (laptop won't boot, monitor flickering) | P2 | ≤ 4 hours | ≤ 2 business days |
| New software request, access provisioning | P3 | ≤ 1 business day | ≤ 5 business days |
| Equipment for new hire (lead time) | P3 | ≤ 1 business day | ≤ 1 week before start date |
| General question or "how do I do X" | P3 | ≤ 1 business day | Same business day if possible |
Rule of thumb: set SLAs you can hit 95% of the time, then tighten quarterly. Missed SLAs hurt trust more than loose ones.
Tying tickets to assets
If you manage more than 30 company laptops, monitors, or licensed software seats, asset tracking pays for itself the first time someone asks "which version of Office does Marketing have?" Tie each asset to its owner and link tickets to the asset — troubleshooting time drops, replacement decisions get faster, and budget conversations get a lot easier.
You don\'t need a separate IT asset management tool for this. A helpdesk with built-in asset records (laptop model, serial, owner, purchase date, warranty) covers what most small teams need. Spreadsheets work too, but they fall out of sync the day someone forgets to update them.
How FyneDesk handles this
Asset records are part of the free plan. Each asset has an owner, type, serial, and ticket history. When a ticket comes in, you can link it to the asset in one click — and the asset\'s history shows every issue it\'s ever had.
The bottom line
A working internal IT helpdesk is not a tool problem; it\'s a process problem with a tool prerequisite. Pick the simplest tool that handles tickets, SLAs, routing, and assets, set it up in five focused days, and roll it out with clear expectations. Skip the enterprise comparison shopping until you outgrow the free option — most small teams never do.
Frequently asked questions
If you're fielding more than 5 IT requests per week and they're scattered across Slack, email, and DMs — yes. A helpdesk gives every request an owner, a status, and a history. Without that, requests get missed, repeated, and forgotten. For under-5-people IT teams, even a free helpdesk pays back the setup cost in the first month.
Audience and tone. An internal IT desk serves employees: tickets are about access, hardware, software, network. SLAs are negotiated against business impact. Tone is direct and technical. A customer helpdesk serves external users: tickets are about products, orders, accounts. SLAs are competitive (faster equals better). Tone is friendlier, more brand-aware. Many tools cover both — but the workflows are different and need separate categories, SLAs, and (often) separate teams.
Most small IT teams can have a working helpdesk live in a week — one phase per day if you stay focused. The longest part is usually the rollout: getting employees to actually use the new email address instead of DMing the IT lead. Plan for 2 weeks of "we've been doing it this way for years" pushback and respond by visibly closing tickets faster than the old method.
Five is the sweet spot: Access, Hardware, Software, Network, and Other. Fewer than five and you can't route effectively. More than five and tagging becomes a chore that gets skipped. Refine after 30 days of real data — if "Other" is over 20% of your tickets, you need to add a category; if any single category is under 5%, merge it.
Start with three priorities: P1 (production down), P2 (impacts work today), P3 (request, not blocker). Set first-response targets you can actually hit — 30 min for P1, 4 hours for P2, 1 business day for P3 is realistic for a small team. Tighten only after you've hit the looser targets for a month. Missed SLAs hurt trust more than slow ones.
If you manage company laptops, monitors, or licensed software for more than 30 people, yes. Tying tickets to assets ("Sarah's MacBook Pro 2024 #M-217") makes troubleshooting and replacement faster, and gives you the data you need for budgeting. Smaller teams can usually get by with a spreadsheet for the first year.
For 1- or 2-person IT teams, you usually are the on-call. The play is making P1 escalation loud (Slack DM, push notification, SMS) and P2/P3 quiet (no alert, batch in normal hours). For 3+ person teams, a weekly rotation works well — same person owns P1 escalations Monday through Sunday, then hands off. Document the rotation in the helpdesk so the system knows who to page.
For a small team, FyneDesk's free plan covers ticketing, SLA tracking, routing, asset management, knowledge base, webhooks, and analytics for up to 3 agents at $0/mo. That's enough for most internal IT teams under 50 employees. Scaling past 3 agents moves you to Pro at $6/agent/mo. Compare to ServiceNow or Jira Service Management, where setup alone can cost more than a year of FyneDesk Pro.
Run your IT desk on the free plan
FyneDesk includes ticketing, SLAs, routing, asset management, and knowledge base on its free plan. Up to 3 agents at $0/mo.
About this guide: Written by the FyneDesk team based on common setup patterns used by small internal IT teams. SLA targets are conservative starting points — adjust to your business impact tolerance. Updated May 3, 2026. Spot an error? Email support@fynedesk.io.