Managed IT across EMEA: response times that mean something when Dubai is at lunch and London is asleep

"We'll respond in four hours" is the most common sentence in an MSP contract and the least useful during an outage. Response is not resolution. Four hours needs a timezone, a severity, and a named owner. Future Cloud Tech operates from Dubai with UK and African coverage; the clock has to survive Friday in the UAE and a Sunday change window in Europe.

Severity first, then the clock

Critical means the business is stopped: email down for everyone, a ransomware event, or a payment system offline. High means a department cannot work but a workaround exists. Medium and low are everything else, with examples in the runbook so the service desk does not argue about labels at 11pm. Acknowledge critical issues with an owner and a channel; do not hide inside a ticket number.

• Critical: first human acknowledgement quickly, then timed updates even when nothing has changed.
• High: triage and a next-step ETA in the first reply.
• Medium and low: queue position or a self-service article when that is faster than a callback.

Follow the sun without losing the plot

Hand-offs fail when the last update is a private note. The next engineer should see: impact, what was tried, and when the customer expects to hear again. WhatsApp is fine for executives if the ticket still holds the record. Phone numbers in Dubai (+971) and the UK (+44) should be on the same signature so nobody guesses which desk is open.

Close with a cause, not a reopen

After a critical incident, write a short note: trigger, fix, and the one change that prevents a repeat. The metric that matters is repeat incidents from the same gap, not how fast the ticket turned green. That is how managed IT earns the retainer after month three.