IT support levels · escalation
How a fault moves through Missan support: L1, L2, L3 and vendor escalation.
Every ticket follows the same path, whether it comes from a 10-user office or a multi-site group. This page sets out who picks it up, when it escalates, what happens when an engineer has to travel, and the response targets we write into contracts. 5,000+ clients served since 2004, 4.6★ from 200+ Google reviews.
Talk to our team today. Mon–Sat, Dubai time.
The four steps
Service desk, remote fix, on-site visit, review.
One ticket number from the first call to closure. The level changes; the person you deal with does not.
- Step 01 L1
Service desk
Your staff raise the ticket by email, phone, WhatsApp or the client portal. The service desk logs it on our service-management platform, agrees the priority with you and closes routine requests on the spot: password resets, access changes, Microsoft 365 questions, printer and device faults.
- Step 02 L2
Remote fix
Anything the desk cannot close goes to an escalation engineer who already knows your setup. Servers, network, firewall, backup jobs, identity and the Microsoft 365 tenant are worked remotely under the same ticket number. Most tickets end here.
- Step 03 L3
On-site visit
When a fix needs hands, an engineer travels from our Sharjah head office to your site anywhere in the seven emirates: hardware swaps, cabling, rack work, device rebuilds. Scheduled visits run where the contract includes them.
- Step 04 Review
Review and report
Repeat problems get a root cause and a permanent fix rather than a third ticket. Every month you receive a report: tickets, repeat problems, risks we found and what we plan to fix next.
Existing client with a fault now? Go to client support for the portal, email and phone channels. Switching from a provider who holds your passwords? Read switch to Missan.
Support levels explained
Who works your ticket at each level.
Levels describe depth of skill, not a queue. A P1 goes to the engineer who can fix it, not to the bottom of a list.
Level 1
Service desk
First contact. Logs and triages every request, sets the priority with the person reporting it, and resolves known fixes and user requests. Owns the ticket until it is closed, whoever is working on it.
Level 2
Escalation engineer
Deeper remote work on servers, networks, firewalls, VPN, backups, identity and Microsoft 365. Already holds your documentation, so nobody asks you to explain your environment twice.
Level 3
Senior and project engineers
Infrastructure faults that need design-level knowledge: firewall high availability, hyperconverged clusters, SAN and storage, migrations and multi-site networks. The same engineers who deliver the projects in our case studies.
Vendor escalation
Vendor and manufacturer cases
Where the fault sits in a product, we open the case with Microsoft, Sangfor, 3CX or your firewall, server and ERP vendor, own the thread and keep you updated. You never referee between suppliers.
Priorities and response targets
Four priorities. Targets in business hours, in writing.
The same definitions and targets go into every managed IT and AMC contract. Response means an engineer has picked the ticket up and is working on it, not that it is closed.
| Priority | What it means | Typical example | Response target |
|---|---|---|---|
| P1 Critical | Business stopped at a site or for a core system | Internet down at a site, ERP down, ransomware suspected | 2 business hours |
| P2 High | A team or key person cannot work; no workaround | Finance cannot reach the bank portal on payment day | 4 business hours |
| P3 Normal | One user affected, or a workaround exists | One laptop slow, a printer offline with another nearby | 1 business day |
| P4 Request | Planned change or question | New starter, access change, software install | 5 business days |
Business hours are Monday to Friday 08:30–17:00 and Saturday 08:30–14:00, Dubai time, excluding UAE public holidays. Resolution targets depend on the systems involved and are agreed per contract.
Outside those hours: 24/7 automated monitoring and alerting, with engineer response in business hours and agreed out-of-hours cover for the systems you name as critical. How to write all of this into a contract is in our IT SLA buyer's guide.
What you can expect at every level
The rules do not change when the ticket escalates.
- One ticket number from the first call to closure, whichever level is working on it.
- One named account lead on your side of the table, who sends the monthly report.
- Priorities agreed with you, not assigned to you, and written into the contract.
- Your admin accounts, domain and documentation stay in your company's name.
- Scope, hours of cover and response targets in writing before the first ticket.
- 24/7 automated monitoring and alerting, with engineer response in business hours and agreed out-of-hours cover.
Fully managed, co-managed or an AMC: the escalation path is the same. See managed IT services, co-managed IT and IT AMC contracts.
The levels in practice
Aluminium factory · Dubai
On-site, same dayAn old firewall swapped for a FortiGate 30G in a single visit, with internet restored the same day.
UAE hospital group · Abu Dhabi
L3 project engineersFortiSwitches, a FortiAP and a FortiGate configured over FortiLink at two remote clinic sites, to the group's own design.
Dicetek · Dubai and India
L2 remote, multi-siteNew firewall in the India office, managed VPN and restore-tested backups, run from the UAE under one contract.
Every published project at a glanceGet a support quote with these targets in writing
Tell us how many users and sites you have and what support you run today. The engineer who scopes it will have read this page.
Questions
IT support levels: what IT managers ask first.
What is the difference between L1, L2 and L3 IT support?
L1 is the service desk: first contact, logging, triage and known fixes. L2 is an escalation engineer working remotely on servers, networks, firewalls, backups and Microsoft 365. L3 is senior and project engineers for design-level infrastructure faults, and the on-site visit when a fix needs hands. If the fault is inside a vendor's product, Missan escalates to the vendor and owns the case.
Who decides the priority of a ticket?
The service desk agrees it with the person reporting the fault, using the P1 to P4 definitions written into your contract: P1 means business stopped at a site or for a core system, P4 is a planned change or question. You can ask for a priority to be raised at any time.
What are Missan's response targets?
P1 2 business hours, P2 4 business hours, P3 1 business day and P4 5 business days. Business hours are Monday to Friday 08:30 to 17:00 and Saturday 08:30 to 14:00, Dubai time, excluding UAE public holidays. Response means an engineer has picked the ticket up and is working on it.
Do you come on site, and where?
Yes. Engineers travel from our Sharjah head office to sites in all seven emirates when a fix needs hands, and on scheduled visits where the contract includes them. Sites outside the UAE are supported remotely, with your local contacts handling hands-on tasks.
Do you monitor systems outside business hours?
Yes: 24/7 automated monitoring and alerting, with engineer response in business hours and agreed out-of-hours cover for the systems you name as critical.
Can our in-house IT team keep L1 and hand you L2 and L3?
Yes. Under a co-managed arrangement your team keeps users and first-line work, and Missan takes monitoring, patching, security and escalations. Who does what goes into a written responsibility matrix.
What happens when the fault is with Microsoft or a hardware vendor?
Missan opens the case with the vendor under your licence or ours, works it with them and keeps you updated under the same ticket number. Vendor coordination is part of the managed service, so you do not have to referee between suppliers.
22+
years serving UAE organisations
5,000+
clients served since 2004
10,000+
projects delivered since 2004
3
countries with Missan teams: the UAE, India and Uzbekistan
4
industry awards in 2025
4.6★
from 200+ Google reviews
Many clients have been with us for more than a decade. Infrastructure, security, cloud, communications and software — delivered and supported by one team. See the full range and the technologies we run
Want these targets in your contract?
Send us your user and site count. We quote managed IT, co-managed IT and AMC against the same four priorities, with scope and hours of cover in writing.