A ticket arrives two hours before Thursday closing time, with a four-working-hour resolution target. Is it due on Thursday evening or Sunday morning? In the Odoo application, the working calendar and matching policy determine the answer. Odoo 19 documentation 1 explains Helpdesk deadlines and reporting; the public abstract of ISO 10002:2018 2 gives a wider context for handling complaints. If you are choosing an application scope for a Saudi business, start with our Odoo application services, then test the deadline before committing it to customers.
How to define a service-level policy
- SLA Policies are enabled by default on newly created Helpdesk teams.
- One policy applies to one team. Criteria are priority, tags, customers and services. The Services criterion requires Timesheets enabled on the team and the relevant sales order line indicated on the ticket.
- If priority is left empty, the policy applies only to tickets with zero stars. A policy applies only after the ticket’s priority is updated to match the criteria.
- A target is a stage to reach within a time allowance. Stages listed as excluded do not count toward the deadline.
- The deadline is calculated from the ticket creation date and working hours. If several policies match, the earliest deadline shows first. If the deadline passes before the stage is reached, the tag turns red and stays red after the ticket is moved.
The calendar is the source of the deadline
The badge is only the result; the working calendar is the root. The policy takes working hours from the company setting by default, and working-hour measures in reports rely on the default working calendar. Before writing any policy, agree on working days, hours and holidays. A deadline that contradicts what your team understands loses value in front of the customer.
A worked example (hypothetical)
Hypothetical example: The Riyadh calendar is Sunday–Thursday 09:00–17:00, with Friday and Saturday closed. The base case has no holidays, lunch break or excluded stages. A ticket is created on Thursday 19 November 2026 at 15:00 with a target of 4 working hours to reach Solved.
| Item | Value |
|---|---|
| Working hours available Thursday 15:00–17:00 | 2 |
| Working hours available Sunday 09:00–11:00 | 2 |
| Deadline | Sunday 22 November 11:00 |
| Elapsed calendar hours to the deadline | 68 |
| Automatic acknowledgment Thursday 15:00 | Not counted as first human reply |
| First human reply Thursday 16:00 | 1 working hour |
| Solved Sunday 10:30 | 3.5 working hours (within target) |
| Optional case: waiting stage Sunday 09:30–10:30 excluded | Deadline Sunday 12:00 |
The gap between 68 calendar hours and 4 working hours is what your team and customer must understand. The Hours Open measure is not limited to working hours, while measures such as Working Hours to Close are. Solving the example ticket at Sunday 10:30 takes 67.5 calendar hours, compared with 3.5 working hours. The optional case assumes you actually configured the waiting-stage exclusion. We do not claim the default setup pauses the clock automatically while waiting for the customer.
Keep four things separate
Do not confuse the first reply, reaching the SLA stage, the actual solution and customer confirmation. A ticket can reach Solved while the problem persists for the customer. A green tag proves a stage and a time, not a happy customer. The Customer Ratings report is separate from SLA, so use it if you want to measure satisfaction.
Practical scope
Start with one team and two policies: one for starting work (an In Progress stage) and one for resolution. Then answer three questions for every ticket: who is responsible, what is the next action, and when is it due and why. Decide in advance which waiting stages are excluded and why.
You can use the project scoping calculator to estimate the size of the work. It is a scoping tool, not evidence of savings. If tickets connect to sales orders and stock, review the Sales application and retail solutions. The demo is a general sales and inventory interface, not a demonstration of this advanced feature.
Reading the reports
SLA Status Analysis shows failed, in-progress and successful SLAs grouped by team, and can be grouped by SLA deadline by month, week or day. The Hours to First Response measure excludes emails sent automatically when a ticket reaches a stage.
Hypothetical example: A cohort of 100 tickets with one common policy in this example: 80 met the target, 10 failed and 10 are still in progress.
- Success among decided tickets: 80 ÷ 90 = 88.9%.
- Success among all tickets in the cohort: 80 ÷ 100 = 80%.
The denominators differ, so never present one as an improvement over the other. Unfinished tickets are neither failed nor completed. Keep report criteria unchanged when comparing two periods. With multiple policies per ticket, separate policy outcomes from unique ticket counts: a measure counting tickets that failed at least one SLA is not the sum of every policy failure.
Acceptance checks
Test these in a licensed instance before relying on them:
- Create a ticket on Thursday at 15:00 and confirm the base-case deadline is Sunday 11:00.
- Confirm the automatic reply is not counted as the first human reply, and that the 16:00 human reply equals one working hour.
- Change priority after creation and confirm when the policy applies.
- Enable two overlapping policies and confirm the earliest deadline shows first.
- Fail a ticket, then move it to the target stage, and confirm the red tag stays.
- Try an excluded waiting stage and verify the new 12:00 deadline.
- Rerun the report with identical criteria and confirm the figures hold.
Frequently asked questions
Is a green tag enough to prove customer satisfaction?
No. It shows a stage reached within a calculated deadline. Satisfaction needs ratings or separate follow-up.
Why do two reports show different durations?
Some measures use working hours and some do not, such as Hours Open. Read the measure name before comparing.
Should we start with many policies?
No. Start with two clear policies, then expand after testing edge cases.
Conclusion
A deadline you can explain rests on an agreed calendar, a small set of policies, reports with stable criteria and written acceptance checks. Go back to the home page, review your scope in the calculator, then contact us to discuss your case. Contractual service levels should match the actual support scope.
Source notes
[1] Odoo 19 Helpdesk documentation: the Service Level Agreements page (criteria, target, excluded stages, deadline, tags, SLA Status Analysis report) and the Reporting page (Tickets Analysis, SLA Status Analysis and Customer Ratings measures, plus two use cases). The numeric examples and recommendations in this article are our own.
[2] ISO 10002:2018, public abstract on the standard’s page: a complaints-handling process covering planning, design, operation, maintenance and improvement for organizations of all sizes, with analysis, evaluation, review and training. We did not review the full standard, and mentioning it implies no certification or Saudi legal obligation.
