Complaint SLA examples for Saudi businesses: setting response times

A complaint SLA is a written promise about how fast your business answers an unhappy customer, and how fast it closes the case. It is an internal commitment measured in hours and days, not a line on a marketing page. The Ministry of Commerce handled 443,000 consumer protection reports in the first nine months of 2026, so for most Saudi businesses the question is no longer whether complaints arrive. It is how long they sit before someone owns them.

This guide gives you concrete complaint response time targets you can copy, a table of examples by business type, and the rules that keep a target honest once real work starts hitting it.

What a complaint SLA actually promises

Most teams say they reply quickly and leave it there. An SLA replaces that with numbers tied to a specific event. The event is the moment a complaint is received on any channel, and the promise is a maximum elapsed time to the next step.

A usable complaint SLA has four parts. First, the channels it covers: phone, email, the website form, the counter and the social inbox. Second, the clock, whether you count business hours or calendar hours. Third, the targets, one per stage. Fourth, the owner, a named person rather than a department.

Everything else is detail. If you cannot state those four things in a short paragraph, your team does not have an SLA, it has an intention.

The three clocks every complaint SLA needs

Teams that track only resolution time end up with angry customers who waited three days for any sign of life. Split the promise into three clocks and most of that frustration disappears.

Acknowledgement. Proof that the complaint was received, with a reference number the customer can quote back. This part can be automatic. Measure it in minutes, not hours.

First response. A named person explains what they understand, what they will check and when they will come back. This cannot be automatic. It is the clock that decides whether a customer waits for you or escalates to a public review or an official report.

Resolution. The outcome, whether that is a refund, a replacement, a correction or a clear explanation, plus confirmation that the customer accepts it. This clock is the only one that should ever pause, and the pause rules matter more than the target itself.

Complaint SLA examples by business type

The right numbers depend on how much a complaint costs you and how easily your customer can switch. A retailer with a queue at the counter cannot use the same targets as a maintenance contractor waiting two weeks for a part. The table below gives starting points that a Saudi SME in each sector can defend in front of a customer.

Three notes on using the table. Publish only the targets you can hit in nine cases out of ten, because a target you miss every week teaches your team to ignore it. State the business hours next to every number, for example Sunday to Thursday, 9:00 to 18:00. And keep one faster track for any complaint that mentions a safety issue or a wrong charge, where the first response target drops to 1 hour whatever your sector.

How to pick response times you can actually meet

Do not start from a number you read online. Start from the last 30 complaints you handled, because that is the only data that reflects your real staffing, your real suppliers and your real working week.

1. List the last 30 complaints with the date and time each one arrived, the time of the first human reply, and the date it closed.
2. Sort the first response times from fastest to slowest and read the value at position 24. That is your current 80th percentile, which is what you already deliver on a normal week.
3. Publish a target slightly above that number, then tighten it by about 25% once the team has held it for a full month.
4. Check the arrival times. If a third of complaints land after 17:00 or on Friday, your clock has to start at the next working hour, and you have to say so in writing.
5. Put the three targets, the business hours, the pause rules and the escalation ladder on one page. Anything longer will not be read.

This bottom up method also shows you where the delay really is. In most small teams the resolution clock is slow because the case is waiting for an approval, not because the fix is difficult. That is a management problem with a one week solution, and you will never see it if you only look at averages.

Escalation and the rules that keep a target honest

An SLA without escalation is a wish. Decide in advance what happens when a clock runs out, and make it a rule rather than a judgement call made by whoever happens to be on shift.

A simple ladder works for most SMEs. At 100% of the first response target the complaint moves to the team lead. At 150% it moves to the department manager. At 200%, or immediately when the complaint names a regulator, a safety risk or an incorrect charge, it goes to the owner or the general manager.

Pause rules have to be written down or the resolution clock becomes meaningless. The clock should pause only while you are genuinely waiting on the customer for information, a document or an appointment, and it should restart the moment they reply. It should never pause because the case is waiting on an internal approval, because that delay is yours and not theirs. Cap the pauses at two per complaint and require a short note for each one.

Finally, agree what a breach costs internally. Not a penalty for the agent, but a review: every breached complaint gets a one line cause in the weekly meeting. After six weeks the same three causes will keep appearing, and those are the process fixes worth your time.

Measuring the SLA without a spreadsheet

A target you cannot check on a Sunday morning is not a target. You need every complaint in one record with its arrival time, owner, category, priority, status and closing time. A shared mailbox cannot give you that, because nothing in a mailbox has an owner or a stage.

This is what a complaint management system for Saudi businesses is for. Daftarix logs every complaint as a ticket in a shared inbox, assigns it to a named person, and tracks category, priority and status from open through to resolved, with replies in Arabic or English. Because the complaint sits next to the customer's invoices, quotations and deals, whoever answers can read the full history before writing the first line.

For the SLA itself, the reporting side is what matters. The reports show complaint volume and resolution time, and reading them by category is how you find the recurring issue behind a cluster of complaints. If your first response times look healthy but one category is always slow to close, the cause is usually a supplier or an approval step rather than the support team. Our guide to help desk KPIs that matter in Saudi Arabia covers the weekly numbers to watch alongside these clocks.

A 30 day plan to put the SLA live

Rolling out a complaint SLA is a four week job for a small team, and most of the work is agreement rather than software.

• Week 1. Pull the last 30 complaints, work out your current 80th percentile for each clock, and list every channel a complaint can arrive on.
• Week 2. Write the one page SLA: three targets, the business hours, the pause rules and the escalation ladder. Have the owner approve it.
• Week 3. Move every channel into one system, train the team on who owns what, and run a full week without telling customers the targets yet.
• Week 4. Review the breaches, adjust the numbers once, then put the acknowledgement and first response promise into your reply templates.

Publish the acknowledgement and first response targets to customers. Keep the resolution target internal at first, because it depends on suppliers and approvals you do not fully control yet.

If you want to see how complaint ownership, priority and resolution time reporting fit together in one place, book a demo and we will walk through it with your own complaint categories.

Frequently asked questions

What is a reasonable complaint response time for a Saudi SME?

Acknowledge within 15 minutes to 1 business hour, give a first human response within 2 to 4 business hours in consumer facing businesses, and aim to resolve within 2 to 5 business days. Then adjust those numbers from your own last 30 complaints instead of keeping a figure you copied.

Should the clock run on Fridays and Saturdays?

Use business hours for the first response and resolution clocks and state them clearly, for example Sunday to Thursday, 9:00 to 18:00. Keep acknowledgement automatic and running around the clock, so a complaint filed late on Friday still gets a reference number straight away.

What should happen when we miss a target?

Escalate automatically at 100% of the target and again at 150%, record a one line cause for every breach, and review the causes once a week. The point is to find the repeated process delay, not to blame the person who was holding the ticket.

Do complaints from official channels need different targets?

Yes. Treat any complaint that arrives through an official channel, or that names a regulator, as top priority with a 1 hour first response, because these carry an external deadline and a public record. The Ministry of Commerce lists receiving a commercial complaint among its e-services, and the window for that channel is set by the platform rather than by you.

Is a complaint SLA the same as a help desk SLA?

They use the same three clocks, but a complaint carries reputational and sometimes regulatory risk that a routine support request does not. Many Saudi businesses run both in one system and keep a tighter track for anything logged as a complaint.