This module extends the Helpdesk application by introducing Service Level Agreement (SLA) functionality.
- Define and manage multiple SLAs per ticket.
- Track deadlines and compliance for each SLA independently.
- Gain better visibility into support performance and ensure service commitments are met.
With this module, helpdesk teams can enforce response and resolution targets, improving accountability and customer satisfaction.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Define service level agreements (SLAs) for helpdesk teams and track whether each ticket meets its response/resolution deadline. Tickets automatically get the applicable SLAs, a deadline, and a colour-coded status.
This module adds Service Level Agreements to the Helpdesk app. Managers create SLA policies under Helpdesk configuration, choosing which teams, categories and tags they apply to, an optional filter, the target stage that counts as done, stages where the clock is paused, and a target expressed in days and hours.
On each helpdesk team you can switch on "Use SLA" and pick the working-hours calendar used to count time. When a ticket is created (or when you press "Set SLA" on the ticket form), Odoo finds the matching SLAs and creates one SLA line per ticket, each with its own deadline, consumed time and status (Accomplished, In Progress, Expired or On Hold).
On the ticket you see the applicable SLAs as coloured tags, the nearest deadline with a remaining-days indicator, and a flag when the SLA is expired. Moving the ticket to another stage updates the SLA status automatically: reaching the target stage marks it accomplished, pausing stages put it on hold, and passing the deadline marks it expired. The kanban view also shows the deadline.
A pivot report "SLA Report" (under Helpdesk reporting) counts tickets by month and by SLA state (Ongoing, Expired, Accomplished), filterable by team and customer. Ticket search adds "SLA Expired" and "SLA Not Expired" filters. SLA policies are restricted per company.
Depends on
Required by other modules
Menus it adds
Models and fields (5)
- helpdesk.sla · new modeldays, name, note, hours, active, domain (Filter), tag_ids (Tags), stage_id, team_ids (Teams), company_id (Company), category_ids (Categories), ignore_stage_ids (Ignore Stages)
- helpdesk.ticket · extends an existing modelsla_ids (Applicable SLAs), sla_fits, team_sla (Team SLA), sla_expired (SLA expired), sla_deadline (SLA deadline), ticket_sla_ids
- helpdesk.sla.report · new modeldate, name, state, active, team_id, ticket_id, partner_id
- helpdesk.ticket.sla · new modelname, color, hours, state, sla_id, expired, deadline, ticket_id, consumed_time (Consumed time), last_state_date, expected_stage_id
- helpdesk.ticket.team · extends an existing modeluse_sla (Use SLA), resource_calendar_id
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 7 confirmed, 2 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/helpdesk.
terminal Installation and usage
OCA documentation · Odoo 19.0Configuration
Source · Odoo 19.0To configure this module, you need to:
- Allow SLA for a Helpdesk's Team
- Set a resource calendar
Configure SLA
- Go to Helpdesk \> Configuration \> SLA.
- Edit or create a new SLA.
- Select a days or hours for that SLA.
Usage
Source · Odoo 19.0- Go to Helpdesk or Helpdesk \> Dashboard to see the tickets dashboard.
- In the Kanban view, you can see datetime in two colors: Green and Red. If is green, SLA is ok, if is red, SLA is wrong.
- In the form, you will see all affected SLAs that were computed on creation.
- If the SLA should change due a change on the ticket, you can recompute it.
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.