Outsourced IT support: how a helpdesk for SMBs works
Outsourced business IT support in Morocco: channels, priority levels, remote vs on-site, ticket portal and the monthly report you should expect.
An outsourced helpdesk is the single entry point for every IT request from your staff. Instead of calling “the person who knows computers” or a repair technician whose number someone kept, every user contacts the same support team through the same channels. Each request becomes a ticket, gets a priority based on its business impact, is handled remotely when possible and on site when necessary, and then appears in a monthly report.
For an SMB in Morocco, the point is not having a technician available: it is making sure nothing gets lost, that urgent issues come before convenient ones, and that the same problems stop coming back. Here is how outsourced business IT support actually works, and what to check before you sign.
What a helpdesk handles
The helpdesk handles user requests. It relies on system monitoring and administration, which belong to the managed IT services contract, but its job is the relationship with your teams. There are two kinds of requests:
- Incidents: something that used to work no longer does. Email unavailable, a PC that will not boot, a printer offline, a VPN refusing to connect.
- Service requests: something new is needed. Creating an account for a new hire, installing software, granting access to a shared folder, preparing a laptop, handling a departure.
The distinction matters because they are not handled the same way: an incident gets resolved, a request gets scheduled. Mixing them leads to installing software before restarting a stopped server, simply because the request arrived first.
Channels: few, but all tracked
Good support does not multiply channels; it controls them. In practice, three are enough:
| Channel | Recommended use | Watch out for |
|---|---|---|
| Phone | Emergencies, a user or service completely blocked | The call must be turned into a ticket, or it disappears |
| Support email | Everyday requests, with screenshots | One shared address, never a technician’s personal mailbox |
| Ticket portal | Service requests, follow-up, history | Easy to reach, no training needed, works in a browser |
Direct messages to a technician’s personal phone are the first enemy of reliable support: the request is not recorded, has no priority, and is lost the first time that person is on leave. Whatever the channel, the rule is the same: no ticket, no request.
Priority levels: impact decides, not the caller
A ticket’s priority depends on two things: how many people are affected and how blocked the business is. It depends neither on the tone of the call nor on the seniority of the caller. A simple grid, written into the contract, avoids arguments:
| Priority | Typical situation | Handling |
|---|---|---|
| Critical | Server, email, internet or phones down for a whole site; security incident | Handled in under 15 minutes, 24/7 monitoring |
| High | An important service degraded, or a key user fully blocked | Handled first, within the time defined in the contract |
| Normal | A user is inconvenienced but can still work | Handled in order of arrival |
| Scheduled | New hire, installation, change | Booked for an agreed date |
The exact times for each level, the hours covered and what happens outside those hours are negotiated and written into the SLA. We cover the definitions to check in our article on managed IT contracts and SLA clauses. One key point: response time (an engineer is working on the problem) is not resolution time (the problem is fixed). An honest contract separates the two.
Remote or on site: the right reflex for each request
Remote assistance is not a lesser service: it is the fastest way to help a user. With a secure remote-control tool, the engineer sees the screen, fixes the issue and shows what was done, within minutes, without waiting for someone to cross Casablanca.
Site visits remain essential for hardware (a failed PC, disk or screen), cabling, equipment installation and some incidents. In a well-run helpdesk, diagnosis happens remotely first, so the technician who travels already knows what to bring. The conditions for site visits (cities covered, timing, what is included) are part of the contract; we also cover them in our complete guide to managed IT services in Morocco.
The life of a ticket, step by step
- Intake: the request arrives by phone, email or portal and becomes a numbered ticket. The user receives a confirmation.
- Triage: incident or service request, priority, device and user concerned. The technician checks the history and the environment documentation.
- Response: an engineer is assigned. For a critical priority, work starts in under 15 minutes.
- Resolution: remotely first; escalation to a specialist engineer (network, Microsoft 365, security) if needed; a site visit if hardware requires it.
- Communication: the user is kept informed at each significant step, especially when resolution takes time.
- Closure: the ticket is closed with its cause and solution, after the user confirms.
- Improvement: if the same request keeps coming back, it appears in the monthly report with a proposed root-cause fix.
The ticket portal and the user experience
A helpdesk is judged first by what your employees say about it. A few principles make the difference:
- A single entry point everyone knows, posted in the office and repeated to every new hire.
- A simple portal: describe the problem, attach a screenshot, follow progress, with no jargon.
- People who know your environment: they know which business application you use and how your network is organised.
- Answers in French and English, understandable by someone who is not in IT.
- New hires ready on day one: account, mailbox, laptop and access prepared from a scheduled request.
For everyday Microsoft 365 requests (shared mailboxes, licences, Teams access), a support team that masters the vendor’s admin console, such as our Microsoft partner team, resolves most cases without touching the user’s device.
The monthly report: proof that support is working
Each month, the report should let a manager answer three questions in five minutes: how many requests, handled within what times, and what keeps recurring. It includes ticket volume by priority and category, response-time compliance, recurring requests with the actions proposed to eliminate them, and tickets still open. The indicators to require are detailed in our article on IT monitoring and the monthly report.
Common mistakes
- Accepting “direct” requests on a technician’s mobile: nothing is tracked, nothing can be measured.
- Letting the user set the priority: everything becomes urgent, so nothing is.
- Confusing response and resolution in the contract.
- Never reading the monthly report: recurring requests are the best indicator of where to invest.
- Forgetting departures: an account still active after someone leaves is a security risk, not an administrative detail.
- Outsourcing without documentation: support that rediscovers your environment on every call wastes time at your expense.
Checklist before choosing an outsourced helpdesk
- Channels are defined and every request becomes a numbered ticket.
- The priority grid is written into the contract, with response times.
- Covered hours and out-of-hours handling are specified.
- On-site visit conditions are clear (cities, timing, included or not).
- Users have a portal to follow their requests.
- Arrivals and departures follow a written procedure.
- A monthly report is provided, with recurring requests and proposed actions.
- Your environment documentation belongs to you and is handed over at the end of the contract.
To compare several providers, our 12-question checklist for choosing an MSP complements this list.
How we do it
At ALLSAFE SOLUTIONS, the helpdesk is part of our managed IT services contract. We start with a free initial audit: device inventory, accounts, business applications and how your teams work. We then agree with you on the channels, the priority grid and the arrival and departure procedures. Every request becomes a ticket; we reply within 24 business hours, and a critical incident is handled in under 15 minutes, with 24/7 monitoring that often detects the failure before the user calls. Each month you receive a readable report and a list of actions to reduce recurring requests. Our case studies show how this works in practice.
Want to see what structured support would look like in your company? Request your free initial audit.
Frequently asked questions
What is the difference between an outsourced helpdesk and an IT repair technician?
A repair technician comes when called, with no history and no commitment. An outsourced helpdesk records every request in a ticket, applies priority levels defined in the contract, knows your environment through documentation and reports each month on what was done.
How do my employees contact support?
Through a small number of channels set at the start: usually a phone number for urgent issues, an email address and a ticket portal for everything else. What matters is that every request, whatever the channel, becomes a tracked ticket.
Is support delivered remotely or on site?
Most requests (passwords, email, software, network printers) are handled remotely, which is faster for the user. Site visits are reserved for hardware, cabling, installations and incidents that require them; the conditions are written into the contract.
How can I tell whether the helpdesk is doing a good job?
From the monthly report: number of requests, split by priority, response times, recurring requests and the actions proposed to eliminate them. Good support aims to reduce repetitive requests, not just to handle them.
About the editorial team
ALLSAFE SOLUTIONS
Network, security and cloud engineers
Written by the engineering team at ALLSAFE SOLUTIONS, a managed IT provider founded in Casablanca by network, security and cloud engineers. Our articles draw on the projects we deliver for clients in Morocco and abroad.
LinkedIn
