One Desk, Two Weekends, and a Holiday You Cannot Diarise
A support promise written as "one working day" is the only promise in your contract that has to be translated. Across six countries that share a language, a currency peg and a customs union, it translates differently in each of them.
It is four o'clock on a Thursday afternoon and a ticket arrives from a customer in Riyadh. Your desk is in Dubai. The contract says next working day. Your agent goes home on Thursday evening expecting to answer it on Sunday morning, because that is what next working day means where they sit — and by then the customer has been waiting through a weekend that, from their side of the border, ended on Saturday night.
Nobody has done anything wrong. Two people applied the same clause honestly and got answers two days apart. This is the one clause in a support contract that cannot be read literally, and the Gulf is the place where it bites hardest, because six countries that share a great deal do not share a working week.
The region does not have a weekend. It has weekends.
Until January 2022 this was simple: the Gulf worked Sunday to Thursday and rested on Friday and Saturday, and every service agreement in the region quietly assumed it. Then the UAE federal government moved to Monday–Thursday with a half day on Friday and a Saturday–Sunday weekend, Sharjah's government went further to a four-day week, and the assumption stopped being safe. The other five states did not move.
| Where the customer is | When their week ends | What "next working day" means on a Thursday ticket |
|---|---|---|
| Dubai or Abu Dhabi, private sector | Friday, often early; weekend Saturday–Sunday | Friday, and possibly Friday morning only. |
| Sharjah, government-facing | Thursday; a four-day week | Monday. Three days later. |
| Riyadh, Jeddah, Dammam | Thursday; weekend Friday–Saturday | Sunday. |
| Doha, Kuwait City, Manama, Muscat | Thursday; weekend Friday–Saturday | Sunday. |
| A head office in Europe or Asia | Friday; weekend Saturday–Sunday | Monday. |
The practical consequence is not that anyone breaches. It is that your breach report stops meaning anything, because the same performance reads as compliant or late depending on whose calendar you apply, and the report applies one calendar to everybody.
Two people read the same clause honestly and arrived two days apart. That is not a discipline problem. It is a units problem, and units problems are fixed in configuration, not in a team meeting.
The clock can be told about this. By default it is not.
What the SLA clock here actually reads
Each ticket category chooses its clock: elapsed wall-clock minutes, or working hours only. Elapsed is the default. On the working-hours setting the clock counts against your configured business hours on the days your organization actually works, and the working week is whatever you set it to — Friday and Saturday off, Saturday and Sunday off, a single rest day, or none. It is not a hardcoded Monday-to-Friday, which is the assumption that makes most support tooling awkward in this region. The mechanics of both clocks, the pause, and how to set targets are covered in full in SLAs that mean something; this page is about what you have to tell it.
So the fix for the Thursday ticket is available and it is a configuration decision, not a development one. The decision worth making deliberately is which categories get which clock, and the Gulf makes that choice sharper than most places, because a four-day gap is long enough to matter commercially.
-
Outage and incident categories stay on the elapsed clock
A promise of restoration within four hours means four real hours. It means them at two in the morning on Eid, and a customer whose line is down does not care what your calendar says. If the commitment is about availability, the clock should ignore the working week entirely — that is what the elapsed setting is for, and it is the right default for exactly these categories.
-
Anything worded as a working day goes on the business clock
Requests, changes, questions, billing queries. The moment a contract uses the phrase "working day", an elapsed clock will silently breach across every weekend and every Eid, and your team will correctly conclude the metric is unfair.
-
Decide whose working week you are promising
Yours or the customer's. There is one setting, so you are choosing one of them for everybody. Choosing yours is defensible and it is what almost everyone does; the mistake is not choosing, and then discovering during a dispute which one the software picked.
-
Say it in the contract in hours, not days
Where you have the drafting pen, "sixteen working hours" travels across a border and "two working days" does not. It also matches what the clock actually counts, which removes the translation step altogether.
Ramadan is a month when your business hours are wrong
Working hours are shortened by statute across the Gulf during Ramadan. The size of the reduction and who it applies to differ by country, and that is a question for your own legal advice rather than for a software page. What is a software question is this: your business hours are a single start time and a single end time, and there is no seasonal variant of them.
Which means that for one month a year, a working-hours clock is either counting hours nobody was at their desk for, or somebody has edited the setting for the month and will need to remember to edit it back. Both are fine; only one of them is a plan. Put it in the annual rhythm below, because the alternative is discovering it in the breach report in week three, when the tickets that arrived in week one are already late.
Half your holiday calendar recurs and half of it cannot
Public holidays are entered per organization and can be marked as recurring, which is the right feature and covers rather less of the Gulf year than it looks.
| Holiday | How the date is fixed | Can it be entered once as recurring? |
|---|---|---|
| National days — UAE 2 December, Saudi 23 September, Qatar 18 December, Oman 18 November | A fixed Gregorian date. | Yes. Enter once, correct every year. |
| Saudi Founding Day, 22 February | A fixed Gregorian date. | Yes. |
| Eid al-Fitr | Lunar. Moves roughly eleven days earlier each Gregorian year, and the exact day is confirmed shortly beforehand. | No. A recurring entry repeats the same calendar date, which will be the wrong day in every subsequent year. |
| Eid al-Adha and the Islamic New Year | Lunar, same drift. | No. |
| The length of an Eid break | Announced by decree, and often differs between public and private sector. | No — it is not only the date that changes, it is how many days. |
The practical shape of this is an annual task with an owner. It takes about twenty minutes and it protects two months of SLA reporting, and it is the single most valuable thing on this page precisely because it is so unglamorous that nobody assigns it.
What we do and do not do
What AWRA OpsHub does today
- A configurable working week. The days your organization does not work are a setting, so a Friday–Saturday weekend, a Saturday–Sunday weekend or a one-day weekend all work. Nothing assumes Monday to Friday.
- A per-category choice of clock — elapsed wall-clock time, or working hours only, chosen per ticket category rather than globally.
- Your own public holiday list, honoured by the working-hours clock, with a recurring flag for holidays that fall on a fixed Gregorian date.
- A clock that rolls forward rather than burning hours. A ticket raised at ten in the evening starts counting at the next opening, so it gets the same working hours as one raised at nine in the morning.
- One shared calendar across the product. The same working week drives HR leave arithmetic and workflow due dates, so those three answers cannot drift apart from each other.
What it does not do
- One working week per organization, not one per country. A desk covering both the UAE and Saudi Arabia has a single weekend setting and two realities. You choose which one the clock believes; the software will not hold both.
- Business hours are a single pair of times. No per-day variation, so a UAE-style short Friday cannot be expressed, and no seasonal variation, so Ramadan hours are a manual edit for the month and a manual edit back.
- Recurring holidays recur on a Gregorian date. Lunar holidays must be entered individually each year. Nothing will remind you that they are missing.
- No per-customer or per-contract calendar. The clock runs on your calendar, not on the calendar of whoever raised the ticket.
- No warning when the calendar is empty. If no working day is configured at all, the working-hours clock quietly falls back to elapsed time rather than failing — which is the safe engineering choice and means a misconfiguration looks like a working system.
The first two are the ones to weigh before you buy anything, and they are not unique to this product — very few systems hold more than one working calendar, and the ones that do charge for it. If your desk genuinely spans both weekend conventions and the difference is contractual, the honest options are to run separate organizations, to promise in hours rather than days, or to accept that one country's tickets are measured on the other country's calendar and say so in the report.
What is not built for the UAE today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in the UAE. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If FTA e-invoicing, a WPS salary file, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
FTA e-invoicing and VAT output
Document structuring and submission through an accredited service provider under the Ministry of Finance programme, with the parts vendors gloss over — rejection handling, resubmission, and a daily report of sales carrying no registration identifier. Corporate tax computation stays with your adviser by design; what we would build is the record it is computed from.
Banks, acquirers and customs paperwork
Bank statement feeds, card acquirer settlements and instant-payment files pulled into the Payments Register, plus a data link to your clearing agent or port community system so a customs event updates the consignment instead of arriving as an email.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
WPS salary files in the layout MoHRE or your free zone authority expects, with end-of-service gratuity accrued on live employee records rather than estimated in a spreadsheet each year.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedThree questions worth asking any support tool in this region
The Gulf-specific questions, which are not the usual ones
Can the weekend be Friday and Saturday, and where is that set?
What you are listening for
A named setting, and ideally a demonstration.
How to read the answer
A vendor who has to check has not sold into this region, which tells you what their support hours are likely to be too. A tool with a hardcoded Saturday–Sunday weekend will misreport every week of the year, in the same direction, invisibly.
How do I enter Eid, given the date is confirmed a few days beforehand?
What you are listening for
An acknowledgement that it is a manual annual entry.
How to read the answer
Anyone who says the recurring holiday feature handles it has not thought about it. The correct answer is a small annual task, and hearing it stated plainly is a good sign about the rest of the product.
If our desk covers several Gulf countries, how many working calendars can we hold?
What you are listening for
Usually one. Occasionally one per team, at a price.
How to read the answer
One is the common and workable answer. What matters is that you find out before the first cross-border dispute rather than during it — and that your SLA report says which calendar it used.
The rhythm that keeps this correct
One annual task, one monthly glance
- Once a year, someone named enters the coming year's fixed national holidays as recurring, and diarises a reminder to add each Eid when its dates are announced.
- Once a year, confirm that the weekend setting still matches how your team actually works. It changed for a lot of organizations in 2022 and the setting did not always follow.
- Before Ramadan, decide whether business hours will be edited for the month — and put the reminder to change them back in the same place as the reminder to change them.
- Every ticket category has been looked at once and assigned a clock deliberately. Elapsed for availability commitments, working hours for anything worded in days.
- Contracts written from here on express support targets in working hours, not working days.
- Your SLA report states which calendar it was measured on. A number without that is not comparable across a border.
The short version
A Gulf support desk has a units problem before it has a performance problem. The working week is not a constant across the region, it stopped being a constant within the region in 2022, and the two biggest holidays of the year cannot be diarised in advance. All three land on two settings — the working week and the holiday list — so the fix is configuration plus one annual task with an owner's name on it. Put availability commitments on the elapsed clock, put anything worded in working days on the business clock, and write future contracts in hours. If your desk spans both weekends, pick the calendar you will be measured on deliberately, and say which one it is on the report.
Frequently asked questions
Can the system use a Friday–Saturday weekend?
Yes. The working week is a setting listing the days your organization does not work, and it drives the working-hours SLA clock, HR leave arithmetic and workflow due dates from one place. Any shape works — Friday and Saturday, Saturday and Sunday, a single rest day, or a seven-day operation with none. The one limit worth knowing is that there is a single working week for the whole organization, so a desk serving both the UAE and Saudi Arabia has to choose which one it is measured on.
How should we handle Eid, when the dates are only confirmed days beforehand?
Enter them as individual dated holidays each year, once announced. The recurring flag repeats a holiday on the same month and day every year, which is correct for a national day and cannot follow a lunar calendar — Eid moves roughly eleven days earlier each Gregorian year, and the length of the break is announced by decree and can differ between public and private sector. Give the task an owner and a calendar reminder; it takes twenty minutes a year and nothing will tell you it has been missed.
What happens to our SLA clock during Ramadan?
Business hours are a single start and end time with no seasonal variant, so if your statutory hours shorten for the month you either edit the setting for that month or accept that the clock counts hours nobody was at their desk for. Neither is wrong; the failure is doing it by accident. Decide before Ramadan begins, and set the reminder to change the hours back at the same moment you set the reminder to change them.
Should support targets be written in days or hours?
Hours, wherever you hold the pen. "Two working days" has to be translated at every border and by every reader, and in the Gulf it currently translates into answers up to three days apart depending on which side of which weekend the ticket lands. "Sixteen working hours" needs no translation and matches what the clock actually counts, which removes an entire class of dispute.
Does this only matter for external customers?
No, and the internal case is often worse. An internal desk covering group entities in several Gulf countries has the same single calendar and none of the contractual pressure that would otherwise surface the mismatch, so the misreporting simply persists. If your group runs a shared service centre in one country for operations in others, check which weekend its clock believes in before you set targets for it.
