A Service Level Agreement (SLA) sets explicit, measurable expectations for how quickly support requests will be acknowledged and resolved. SLAs are typically tiered by priority (e.g., Critical, High, Normal) and channel, with stricter targets for issues causing business-critical outages.
Common SLA components:
- First Response Time target (e.g., Critical issues acknowledged within 1 hour)
- Resolution Time target (e.g., Normal issues resolved within 3 business days)
- Operating hours (24/7 vs. business hours)
- Escalation paths if targets are breached
Why it matters: SLAs create accountability, help customers set expectations, and give support teams a clear performance baseline. Breached SLAs are tracked as a key operational metric and may trigger penalties in external, contractual agreements (common in B2B and enterprise software).
Internal SLAs (between support and other departments, such as engineering) are equally important for managing escalation workflows efficiently.