Support and Maintenance en Riyadh
How we work in Riyadh
A maintenance window asks for two things at once
You need low usage and you need people awake in case it goes wrong. With calendars that do not line up, the quietest moment and the one with the most hands free can fall on different days. We pick the one that meets both conditions and write it down, instead of deciding each time.
Our shift runs Monday to Friday and we say so before signing
We have no Sunday cover and we are not going to invent one to close a deal. If you need cover that day it has to come from someone on your side or a second supplier, and that split is agreed at the start. We would rather lose a contract than break it in month three.
Every alert needs a recipient who is working
An alert landing in an empty inbox is not monitoring, it is a log entry. For each day of the week there has to be a name and a channel, and the escalation has to fire on its own when the first person is away. We check it by sending fake alerts, including on the odd days.
Expiry warnings go out far enough ahead
Certificates, domains and licences expire on the date they expire, and some fall inside a run of days off chained across the two calendars. A three-day warning can end up with nobody to read it. We set them at thirty days, with a second reminder behind.
Answering your questions
What people ask us about Support and Maintenance in Riyadh.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs