ZenHR runs payroll, leave and HR administration for companies across MENA. Its software is used on the ordinary days when someone books a holiday, and on the specific days each month when a whole company expects to be paid correctly.
Payroll support is not evenly distributed
An HR platform gets quiet weeks and then a spike, because payroll runs on a calendar. The days around a pay date concentrate a month of urgency into a few hours, and none of it can be deferred.
The questions also come from two directions. An HR administrator asks how to configure an end-of-service calculation or close a payroll cycle; an employee asks why their payslip looks the way it does. Same platform, entirely different conversations.
And the region is not one rulebook. Labour law, end-of-service entitlement and payroll practice vary by country, so a confident general answer is often a wrong local one.
What Open does
The agent takes the how-do-I layer of an HR platform — leave balances and requests, profile and document questions, approvals, the configuration steps an administrator repeats every cycle — in Arabic or English.
That layer is most of the volume and almost none of the risk, which is what makes it worth automating first: it is the queue that stands between a payroll specialist and the work only they can do.
Anything about a specific person’s pay goes to a specialist. A disputed deduction, an end-of-service settlement or a payslip that looks wrong is somebody’s livelihood and a legal question at the same time, and neither is a candidate for automation.
The Impact
The payroll spike stops being the week nothing else gets answered, and the specialists spend it on the cases that genuinely need them.
ZenHR is not publishing resolution or response-time figures yet. This story will carry them when they exist and ZenHR is ready to share them.