When something breaks, the first question is who fixes it and how fast they can reach it. Many buyers use the words helpdesk, desktop support and on-site support as if they meant the same thing. They do not. They are different ways of delivering help, and each one has things it cannot do.
This article defines each term, shows the support tiers, lists what each level can and cannot fix, and explains how tickets move between them. It ends with a decision table and a look at the hybrid model most organizations end up using.
What is the difference between on-site IT support and a helpdesk?
The difference is where the work happens: a helpdesk works remotely through tickets, calls, chat and remote sessions, while on-site IT support puts a technician physically at your location.
That one difference drives everything else. A remote analyst can see a screen, change a setting and reset an account. A person on site can also reach the device, the cable, the printer and the room. ConnectWise describes a help desk as reactive and tactical, focused on resolving end-user issues quickly, with typical work such as password resets, software troubleshooting and hardware problems. The key point for this comparison is that a helpdesk can diagnose a hardware problem but cannot touch the hardware.
What does on-site IT support mean?
On-site IT support means a technician travels to your office, site or branch to resolve or install something that needs physical access, then leaves a record of what was done.
The term covers a range of work, from a single visit to fix a failed docking station to a technician who is based at your site every working day. Our glossary entry on dispatch explains how those visits are assigned and scheduled. What they share is hands-on access to equipment.
- Hardware repair and part swaps on laptops, desktops, monitors and docks.
- Printer and peripheral fixes, including paper paths, trays and network printer setup.
- Patch cords, wall ports and small cabling faults at the desk or rack.
- Moves, adds and changes: relocating a desk, setting up a new starter, rebuilding a workstation.
- Device deployment, imaging and asset tagging at the point of use.
- In-person help for users when remote tools cannot reach the device.
What are the IT support tiers: L1 helpdesk, remote, on-site and field?
IT support is usually organized in tiers, where each level handles harder or more physical problems and passes the rest up.
InvGate describes Tier 0 as self-service, Tier 1 as frontline work from documented procedures, Tier 2 as system-level technical investigation, Tier 3 as expert work on unresolved incidents, and Tier 4 as external vendors and hardware manufacturers. Terms for on-site work vary between providers, so ask how a provider labels its own levels. A common working model looks like this.
- L1 helpdesk: takes the call or ticket, logs it, handles common requests such as passwords and software, and routes the rest.
- L2 remote engineering: investigates deeper faults through remote sessions and admin tools, and works with devices, applications and infrastructure.
- On-site support: a technician at your location for physical work and for faults that remote tools cannot resolve.
- Field or specialist engineers: a technician with the right skills or parts for a site that has no technician of its own, often sent through dispatch.
- Vendor or manufacturer: warranty repair and proprietary fixes, which InvGate places at Tier 4.
What can each level fix, and what can it not?
Remote support fixes anything that lives in software, accounts or configuration and cannot fix anything that needs a physical hand.
Microsoft's Remote Help documentation shows the shape of remote work: support teams connect to a user's device for real-time assistance, and both sides sign in with organization accounts. Its web app gives the helper view-only access, so the helper can guide the user but not take control. If the device will not power on, has no network or has a failed part, no remote tool helps. That is where a person on site is needed.
| Problem | Helpdesk or remote | On-site |
|---|---|---|
| Forgotten password or locked account | Yes | Not needed |
| Software install, update or settings fault | Yes, if the device is online | Only if remote access fails |
| Remote diagnosis of a slow or failing device | Yes | Follows up if hardware is at fault |
| Broken screen, failed drive or dead dock | Diagnoses only | Yes |
| Printer jam, tray or toner issue | Can guide the user | Yes |
| Loose or faulty patch cord and wall port | Can suggest the cause | Yes |
| Moving a desk or setting up a new workstation | Prepares the account | Yes |
| Device that will not power on or reach the network | Cannot connect | Yes |
How do helpdesk and on-site support hand off to each other?
A good handoff keeps one ticket from first report to closure, so nobody asks the user to explain the problem twice.
InvGate describes escalation as functional, hierarchical, time-based or impact-based, and says each escalation should carry context and clear ownership. For on-site work, that means the helpdesk sends the on-site technician the findings, not just the complaint.
- The user reports the issue and the helpdesk logs a ticket with the device, location and contact.
- L1 or L2 tries remote fixes and records what was tested and what failed.
- If the cause is physical, the helpdesk raises a dispatch request on the same ticket, with access details, hours and parts needed.
- The on-site technician reads the history, does the repair and records what changed.
- The technician files a visit report, and the ticket stays open until the user confirms the fix.
- If the visit reveals a wider fault, the ticket goes back up to L2 or L3, or out to the vendor.
What response times should you expect from each?
Response expectations are set by a service level agreement, so ask for the response and resolution targets in writing before you buy.
NIST defines a service level agreement as an arrangement between a provider and a client that covers duties, type of service, expected performance, and requirements for reporting and resolution. Response time is how long until someone acknowledges and starts on the ticket. Resolution time is how long until the problem is fixed. They are different measures, and a fast response can still lead to a slow fix. Our glossary entries on SLA and MTTR explain both.
Remote and on-site work are measured differently. A helpdesk can usually respond faster because no travel is involved. On-site targets depend on distance, access, parts and the hours your contract covers. Ask whether on-site targets run from the ticket being logged or from the dispatch being accepted, and ask what counts as a missed target. We do not quote targets here because they should come from your own written scope.
When do you need a helpdesk, on-site support or both?
You need a helpdesk when most of your problems are software, accounts and configuration, and on-site support when you have equipment, rooms or sites that people cannot reach remotely.
Use the table below as a first pass. If your answers span both columns, you need a hybrid.
| Your situation | Best fit |
|---|---|
| Fully remote staff, cloud apps, few physical assets | Helpdesk, with occasional dispatch |
| One or two offices with printers, docks and meeting rooms | Helpdesk plus on-site visits |
| Many small sites with no IT staff | Helpdesk plus on-demand dispatch |
| Large site with constant moves, new starters and device refreshes | Helpdesk plus a dedicated on-site engineer |
| Recurring hardware faults at known locations | On-site support with a spares plan |
| Short project such as a refresh or office move | Scheduled on-site technicians for the project |
What is the hybrid model and how does Deploris fit?
The hybrid model pairs a remote helpdesk with on-site technicians under one ticket flow, so remote fixes happen first and physical work is dispatched only when needed.
This keeps simple problems quick to handle, and still gives you hands on site for the rest. Deploris provides remote helpdesk support, scheduled and on-demand on-site visits, and dedicated on-site engineers, and can connect them through one ticket and one set of reports. Scope and pricing are agreed against your sites, hours and device mix after a conversation, not from a rate sheet. If you are choosing a provider, our guide to questions for a field services provider covers what to ask.
Key takeaways
- A helpdesk works remotely through tickets, calls and remote sessions, and on-site support puts a technician at your location.
- Remote support cannot fix hardware, cabling, printers or physical moves, so those need a person on site.
- A clean handoff keeps one ticket from report to closure and passes the findings to the technician.
- Ask for response and resolution targets in writing, because they are different measures.
- Most organizations end up with a hybrid, where the helpdesk triages and dispatches on-site work when needed.
Sources and further reading
- InvGate, IT support levels explained: from Tier 0 to Tier 4 (opens in a new tab)
- ConnectWise, Service desk vs. help desk: what is the difference (opens in a new tab)
- NIST CSRC glossary, service level agreement (opens in a new tab)
- Microsoft Learn, Use Remote Help to assist users authenticated by your organization (opens in a new tab)