SLA figures cover contract calls only, measured against a flat 8-hour response target from logged to responded. 2 records in this selection sit outside that — quotes, projects and planned installs, plus 1 call billed time and materials. They stay visible for volume context.
Service performance
3 eligible records in this yearAverage first response
17.4 hr
Target 8 hours from logged to responded
Average resolution
1.7 days
Open records excluded from the average
SLA achievement
50.0%
1 call(s) over the 8-hour target
First-time fix
50.0%
Where the source records the field
Volume
Contract calls
3
5 calls logged in the period
Off contract
1
£325.5 chargeable
Open / closed
2 / 3
Across the selected period
Data-quality gaps
1
Contract calls with no response time recorded
Support volume trend
Event measure summed per month
Records are counted in the bucket containing their logged date.
Category breakdown
Eligible records only
3
records
- Line of business app1
- Network1
- Telephony1
Support performance by year
Contract calls against the 8-hour response target
| Year | Calls | Avg response | SLA met | Misses | Excluded |
|---|---|---|---|---|---|
| 2026 | 3 | 17.43 hr | 50.0% | 1 | 2 |
Response performance by call logger
Grouped by the person who raised the call, not the engineer
| Call logger | Calls | Avg response | SLA met | Misses |
|---|---|---|---|---|
| Julie Herbert | 1 | 32.09 hr | 0% | 1 |
| Anne-Marie Cable | 1 | 2.76 hr | 100% | 0 |
| Aiden Higgins | 1 | — | — | 0 |
1 contract calls missed the 8-hour target
Worst first — the calls a service review will be asked about
Longest 24.1 hr over
| Job number | Call logger | Machine or system | Logged | Response | Over target | Engineer | Issue |
|---|---|---|---|---|---|---|---|
| 303865 | Julie Herbert | HP ProBook 450 G6 | 2026-01-23 13:35 | 32.09 hr | +24.1 | BK | Application crash on launch |
Recurring issues by call logger
Repeat patterns worth fixing at source
No repeat pattern in this period.
Recurring issues by machine
Equipment generating repeat calls
No device is generating repeat calls.
SLA achievement trend
Percentage of eligible records responded to within target
Records
5 records match the current filters · showing the 150 most recent
Read-only from source
| Reference | Logged | Type | Summary | Priority | Status | Response | Resolution | SLA |
|---|---|---|---|---|---|---|---|---|
| HAZ559-100028 | 21 Aug 2026 | Incident | Voicemail not delivering Telephony · SE · Head Office | P3 | In Progress | — | — | n/a |
| HAZ559-100027 | 07 Aug 2026 | Change · excluded | Wi-Fi dropouts in warehouse Network · SE · Remote | P3 | Resolved | — | — | n/a |
| HAZ559-100026 | 31 Jul 2026 | Quote · excluded | Endpoint alert investigation Security · KB · Branch | P3 | In Progress | — | — | n/a |
| HAZ559-100025 | 02 Jun 2026 | Incident | Slow VPN Network · SE · Remote | P4 | Resolved | 2.76 hr | 1.1 days | Met |
| HAZ559-100024 | 23 Jan 2026 | Change | Application crash on launch Line of business app · BK · Head Office | P3 | Resolved | 32.09 hr | 2.4 days | Missed |
iHow these figures are calculatedShow
Eligibility uses the structured record type from the source system, never free-text title matching. Excluded types: Quote, Project, Planned Install (rule version sla-rules v2.0). Records with no captured response time are left out of averages and reported as a data-quality count. Worked example: if nine eligible records respond within one hour and one quote stays open for fourteen days, the quote contributes nothing to the response-time denominator and does not move the average.