Practice SLA management vocabulary: P1 response time requirements, SLA breaches, clock pausing, monthly SLA compliance reporting, and SLA metrics interpretation.
0 / 5 completed
1 / 5
'The SLA requires 4-hour first response for P1.' What does 'first response' mean in SLA terms?
'First response' in an SLA means the time from ticket creation to the first substantive response from a support agent — not just an auto-acknowledgement. For P1 tickets, a 4-hour first response means a real engineer must have read the ticket, assessed the issue, and communicated back to the customer with initial findings or next steps within 4 hours.
2 / 5
'We breached SLA on this ticket.' What does an SLA breach mean and what typically happens next?
An SLA breach means the vendor failed to meet a committed response or resolution time. Depending on the contract, this may trigger: automatic service credits to the customer, an internal root cause analysis, a formal apology from account management, and reporting in the monthly SLA compliance report. Repeated breaches damage customer trust and can trigger contract review clauses.
3 / 5
'The SLA clock is paused while waiting for customer info.' What is this practice called and why is it used?
'Pending customer' (often shown as PCR — Pending Customer Response — or 'On Hold — Awaiting Customer') pauses the SLA timer when the ticket requires information from the customer to proceed. This is standard practice: if the vendor asks for log files and the customer takes 3 days to send them, those 3 days don't count against the vendor's SLA. The clock resumes when the customer responds.
4 / 5
'The SLA metrics report is sent monthly.' What should an SLA metrics report contain?
A monthly SLA metrics report gives customers visibility into support performance. It typically includes: ticket volume by priority, SLA compliance rate by priority (e.g., 98% of P1 tickets met SLA), number and details of any SLA breaches, average response and resolution times, and a trend line showing whether performance is improving or degrading.
5 / 5
'We're at 97% SLA compliance this quarter.' Is 97% SLA compliance generally considered acceptable?
97% SLA compliance is generally strong performance — it means the vendor met its committed response or resolution times 97% of the time. Many enterprise SLAs set targets of 95-99%. However, context matters: 97% overall with 100% P1 compliance is excellent, while 97% with P1 breaches is a serious concern. SLA compliance is typically broken down by ticket priority level.