SLA Management
Service Level Management turns the commitments in your service catalogue into live, enforceable targets. Inside ServiceCore, every service-level agreement is a Service Level Policy object that defines which records it applies to and what response and resolution times those records must meet. The moment an incident or service request is logged, the matching policy attaches automatically, calculates the target dates against a business-hours calendar, and writes them to the record's Due Date field. From that point the clock runs in real time, visible on the record and on every queue and dashboard built from it.
Built for the way sla management should work
Service Level Management turns the commitments in your service catalogue into live, enforceable targets. Inside ServiceCore, every service-level agreement is a Service Level Policy object that defines which records it applies to and what response and resolution times those records must meet. The moment an incident or service request is logged, the matching policy attaches automatically, calculates the target dates against a business-hours calendar, and writes them to the record's Due Date field. From that point the clock runs in real time, visible on the record and on every queue and dashboard built from it.
Because policies are rule-based, prioritization stops being a judgement call. Targets are selected from the impact, urgency, customer, and service attributes already on the record, so the same logic that classifies an incident also decides how fast it must move. Multi-level targets let a single record track response, intermediate checkpoints, and resolution in parallel, each with its own clock. When a target approaches its limit, escalation fires before the breach, not after, notifying the right owner or reassigning the work while there is still time to recover.
The module measures the full delivery chain, not just the customer-facing promise. Operational Level Agreements between internal teams and underpinning contracts with suppliers roll up against the same record, so a customer SLA that depends on a vendor's resolution time is tracked end to end. Business-hours calendars, holidays, and shift coverage are applied to every calculation, and SLA clocks pause during agreed wait states such as pending-customer, so the timers reflect the time you actually owned rather than wall-clock elapsed time.
Service Level Management does not run in isolation; it reads from and writes to the shared data model that connects all 29 modules. It attaches to Incident and Request records, draws relationship and ownership context from the CMDB, feeds remaining-time signals to the work-prioritization engine, and surfaces breach and compliance metrics in Reporting and Continual Improvement. The numbers you report on attainment, breaches, and escalations come from the same records your teams worked, so what you measured is what you delivered.
- Response & resolution targets
- Real-time SLA tracking
- Proactive escalation
- OLA & underpinning contracts
- Business-hours calendars
- Breach reporting
What you can do with it
Service Level Policy objects
Define response and resolution targets as reusable, rule-scoped policies that attach automatically to the records they match.
Automatic Due Date calculation
Target response and resolution dates are computed at log time and written to the record's Due Date field, removing manual calendar math.
Multi-level targets
Track response, intermediate checkpoints, and resolution on one record in parallel, each with its own independent clock.
Business-hours calendars
Apply working hours, holidays, and shift coverage to every timer, and pause SLA clocks during agreed wait states such as pending-customer.
Proactive escalation
Trigger notifications and reassignments before a target is breached, based on percentage-to-limit thresholds rather than after-the-fact alerts.
OLA and underpinning contracts
Track internal Operational Level Agreements and supplier underpinning contracts against the same record so the full delivery chain is measured.
Why teams adopt it
Fewer breaches
Proactive escalation surfaces at-risk records while there is still time to act, shifting teams from explaining breaches to preventing them.
Objective prioritization
Rule-based targets decide what moves first from data already on the record, ending subjective queue debates between technicians.
Defensible reporting
Attainment, breach, and escalation figures are drawn from the same worked records, so the numbers hold up in customer and audit reviews.
End-to-end accountability
Customer SLAs, internal OLAs, and supplier contracts roll up together, exposing exactly where in the chain a commitment is at risk.
Where it fits
Tiered customer SLAs
Apply faster response and resolution targets to premium customers automatically by scoping policies to the customer and service on the record.
Weekend and holiday coverage
A request logged late Friday is calculated from Monday's working start, with holidays excluded, so the target reflects real coverage.
Supplier-dependent resolution
When resolution depends on a vendor, track the underpinning contract alongside the customer SLA to see which party is consuming the clock.
At-risk queue triage
Dashboards rank open records by remaining time so dispatchers focus on the items closest to breach across all active SLAs.
Common questions
Every target is computed against a business-hours calendar that includes working hours, holidays, and shift coverage. Time outside those windows is not counted, and SLA clocks pause during agreed wait states such as pending-customer, so timers reflect the time your team actually owned rather than raw elapsed time.
Related modules
See SLA Management in action.
Book a demo and we'll show sla management working alongside the rest of the platform — on one shared data model.