An IT help desk is the single place your staff go for technology problems and requests, by phone, email, portal or chat, with every request tracked as a ticket. Boston IT Services Group runs an outsourced help desk for Boston and Massachusetts organizations that have no internal IT staff or whose internal team needs help with the ticket queue.
Our IT help desk Boston organizations use gives your staff one place to go when technology gets in the way: a phone number, an email address, a portal and chat, all feeding a single ticket queue. Every request is logged, prioritized, worked and closed with a record of what was done. If your office manager is fielding password resets between other jobs, or your one IT person cannot get past the queue, an outsourced help desk takes that load.
What an outsourced help desk does
A help desk is the front door for IT. It takes requests from users, solves the simple ones right away, routes harder ones to the right engineer and keeps track of everything until it is finished. An outsourced IT help desk Boston firms hire is the same function, staffed by an outside provider instead of your own employees.
The work splits into two kinds of tickets. Incidents are things that broke: Outlook will not open, the VPN drops, the scanner stopped emailing. Service requests are things someone needs: a new hire's account, access to a shared folder, a second monitor. Both go through the same queue, but service requests can often be handled with a standard form and checklist.
A Boston helpdesk service also has to cover the physical office. Some tickets end with a technician on site. Our IT support page covers onsite work and the L1 to L3 escalation model, so this page sticks to how the help desk itself runs.
Help desk channels: phone, email, portal and chat
People report problems in different ways, and a good help desk accepts all of them without losing track of any.
| Channel | Best for | Tradeoff |
|---|---|---|
| Phone | Urgent problems, users who are locked out, anything where talking it through is faster | Harder to attach screenshots; the technician has to write good notes |
| Non-urgent requests, problems with error messages to attach | Easy to send vague requests; needs a quick follow-up to clarify | |
| Portal | Service requests with forms (new hire, access request), checking ticket status | Users need to remember to use it |
| Chat | Quick questions, users who would rather not call | Not suited to long troubleshooting sessions |
Whatever the channel, the request ends up as a ticket. A phone call does not live only in the technician's memory, and an email does not sit in someone's inbox.
How a help desk ticket moves, step by step
Behind the help desk sits a PSA (professional services automation) platform. It is the ticketing system, the contract record and the reporting engine in one place. Each ticket gets an ID, a requester, a priority, a category and a history of every note and action. A typical ticket takes this path.
- A user reports a problem or request through any channel.
- The PSA creates a ticket and sends the user a confirmation with the ticket number.
- A technician assigns a priority based on how many people are affected and how badly they are blocked.
- The technician checks the knowledge base for your environment, contacts the user and starts work.
- Simple problems are fixed on first contact. Others escalate with full notes to a senior engineer or the vendor.
- The user confirms the fix, and the ticket closes with a resolution note.
- A short satisfaction survey goes to the user.
- Patterns in closed tickets are reviewed, so recurring problems get a permanent fix.
SLAs: what they are and what to look for
An SLA (service level agreement) is the part of the contract that turns "we'll get back to you" into measurable targets. A help desk SLA usually defines:
- response targets by priority, meaning how soon a person starts working the ticket
- resolution targets by priority, meaning how soon the problem should be fixed or have a workaround
- covered hours, and what happens outside them
- how performance is measured and reported to you
Read the definitions carefully. An automated "we got your email" message is not a response. Resolution targets usually carve out time spent waiting on the user or a vendor, which is fair, but the carve-outs should be written down. We publish our targets in the agreement and report against them, rather than quoting numbers on a web page. Whatever IT help desk Boston providers propose to you, ask for these definitions in writing before you sign.
Password resets, onboarding and access requests
These three request types make up a large share of help desk work, and each needs a defined process.
Password resets look simple, but they are also how attackers try to talk their way into accounts. Before resetting a password or MFA (multifactor authentication) method, the help desk should verify the caller's identity using a method agreed in advance. Better still, take the help desk out of routine resets. Microsoft Entra self-service password reset lets users reset their own password or clear a lockout after proving who they are with methods they registered earlier, with no help desk involvement. For MFA prompts, CISA recommends phishing-resistant MFA where possible and number matching as a fallback to block push-bombing attacks. Our Microsoft 365 security checklist covers the related tenant settings.
Onboarding requests work best as a form: start date, role, manager, equipment, software and which shared folders and Teams the person needs. The help desk turns that into a checklist so the laptop is ready and the Microsoft 365 accounts work on the first morning. Offboarding is the reverse, and timing matters more. Access should end when employment ends.
Access requests (a new SharePoint site, a finance folder, a shared mailbox) should be approved by the data owner or a manager you name, and the approval should be recorded in the ticket.
The knowledge base
A help desk is only as good as what it knows about your environment. We keep two kinds of documentation. The internal knowledge base is for technicians: how your network is laid out, which apps each team uses, vendor contacts, known quirks and the fix that worked last time. The user-facing articles are short how-tos for common requests, such as connecting to the VPN or adding a shared calendar.
Good documentation is what makes first-contact resolution possible. It also means your environment is not trapped in one person's head, which matters if that person leaves.
After-hours help desk options
Not every office needs coverage at 2 a.m. Common options are emergency-only coverage for critical problems outside business hours, extended hours that match early or late shifts, and full coverage for organizations that operate around the clock. Pick the one that matches when your people work and what an outage at night would cost you. Whatever you choose, the agreement should say exactly which requests are handled after hours and how to reach someone.
What an IT help desk Boston offices hire should report
An IT help desk should show you how it is doing every month. We think these six numbers are worth reading each month.
| Metric | Definition | What it tells you |
|---|---|---|
| First-contact resolution (FCR) | Share of tickets solved during the first interaction, with no callback or transfer | How well trained and documented the first line is |
| Time to first response | How long from ticket creation until a person starts working it | Whether urgent problems get picked up quickly |
| Time to resolve | Average time from ticket creation until the problem is fixed | How long users stay blocked |
| Reopen rate | Share of closed tickets reopened because the problem came back | Whether tickets are closed too early |
| CSAT (customer satisfaction) | Average rating users give in post-ticket surveys | How the service feels to the people using it |
| Volume by category | Ticket counts grouped by type (email, printers, access) | Where recurring problems need a permanent fix |
Read the metrics together. A help desk can push FCR up by closing tickets quickly, so read it next to the reopen rate. Volume by category is the most useful for planning, because twenty printer tickets a month is a printer problem, not a help desk problem.
Help desk vs service desk
People use the two terms interchangeably, and in a small office the difference rarely matters. Formally, ITIL 4 describes the purpose of the service desk practice as being "to capture demand for incident resolution and service requests," with the service desk acting as the single point of contact between the provider and all of its users (ITSM.tools summary of ITIL 4). A help desk, in the traditional sense, focuses more narrowly on fixing technical problems. The Boston IT helpdesk we run does both: it fixes incidents and handles service requests through the same queue.
When to outsource the IT helpdesk Boston teams depend on
Outsourcing the help desk makes sense when one or more of these is true:
- an office manager, partner or practice manager spends hours each week on IT problems
- requests live in email threads and text messages, and some get lost
- nobody has documented how your systems are set up
- your internal IT person spends all day on the queue and never gets to projects
- staff wait until a problem is serious before reporting it, because asking for help is awkward
If you have internal IT staff, a co-managed setup lets them hand us the queue while they keep projects and line-of-business systems. Our IT outsourcing and co-managed IT page explains how that split works. For offices with no IT staff, the help desk usually comes as part of a managed IT services agreement with monitoring, patching and security.
A helpdesk service Boston offices can trust should be easy to reach, should keep a record of everything and should report its numbers without being asked. If your current IT help desk in Boston does not, send us a description of how your staff get help today and we will show you how the queue would run with us.
Frequently asked questions
What does an outsourced help desk do?
An outsourced help desk is an outside team that takes your staff's IT requests by phone, email, portal or chat, logs each one as a ticket, fixes what it can on first contact and escalates the rest to senior engineers or vendors. It handles password resets, access requests, new hire setup, software problems and printer issues, and it reports on volume, resolution times and user satisfaction so you can see how it is performing.
What is the difference between a help desk and a service desk?
In everyday use the terms overlap. Traditionally, a help desk focuses on fixing technical problems for users. A service desk, as ITIL describes it, is the single point of contact between an IT provider and all of its users, capturing both incidents (something is broken) and service requests (someone needs something new, such as access or equipment). Most small business help desks today do both.
What is first-contact resolution?
First-contact resolution (FCR) is the share of tickets solved during the user's first interaction, with no callback, transfer or follow-up needed. A high FCR usually means the first-line technicians are well trained and have good documentation. It should be read alongside the reopen rate, because a help desk can inflate FCR by closing tickets too early, and reopened tickets show when that is happening.
What is an SLA for a help desk?
An SLA (service level agreement) is the part of the contract that sets measurable targets for the help desk: how quickly it responds to a ticket at each priority level, how quickly it aims to resolve it, which hours are covered and how performance is reported. A good SLA defines what counts as a response, since an automated email reply and a technician starting work are very different things.
Can users reset their own passwords?
Often, yes. Microsoft Entra self-service password reset lets users reset their own Microsoft 365 password, or clear a lockout, after proving their identity with methods they registered in advance, without contacting the help desk. It has to be enabled and configured by an administrator, and users have to register their methods first. When self-service is not possible, the help desk should verify identity before resetting anything.
Is after-hours help desk support available?
After-hours coverage is something you choose in the agreement. Common options are emergency-only coverage for critical issues, extended hours that match early or late shifts, and full coverage for offices that run around the clock. The right choice depends on when your people work and what an outage at 9 p.m. would cost you. The agreement should spell out exactly what each option covers.
When should a business outsource its IT helpdesk?
Common signs are an office manager or partner spending hours each week on IT problems, tickets that live in email threads and get lost, no documentation of how systems are set up, and an internal IT person who cannot get to projects because the queue never empties. Outsourcing the help desk fixes the queue and leaves internal staff, if you have them, free for higher-value work.