Service Level Agreements

A Service Level Agreement (SLA) in the context of customer support, SLAs outline the maximum timeframes within which agents should respond to and resolve customer inquiries or issues.

---

Why is SLA useful?

1. Improved Customer Satisfaction: By setting clear expectations for response and resolution times, SLAs help ensure customers receive timely support, which boosts satisfaction and trust.

2. Enhanced Accountability: SLAs provide a structured framework for monitoring agent performance. This makes it easier to identify gaps in service delivery and take corrective actions.

3. Better Resource Management: By setting priorities and deadlines, SLAs help teams manage workloads effectively, ensuring critical issues are addressed promptly.

4. Data-Driven Insights: SLAs provide valuable metrics that can be analyzed to understand performance trends, helping organizations make informed decisions to improve processes.

Incorporating SLAs into your CRM platform helps maintain high standards of service, driving both operational efficiency and customer loyalty.

---

Feature Description

Creating metric-based SLAs:

Understanding the metrics:

1. First Response Time (FRT): Calculated from the ticket's "opened_at" time, irrespective of agent assignment.

2. Next Response Time (NRT): Calculated from the first user message until the agent replies back.

3. Resolution Time (RT): Calculated from the ticket's "opened_at" time until it is resolved, regardless of agent handoffs.

Defining Escalations and Reminders

• Multi-Level Escalations: Users can set up multi-level escalations if any of these policies are breached.

  • Escalations consist of in-app notification and mails

• Reminders: Users can set up reminders when the SLA is nearing breach time to prompt timely actions.

  • Reminders also consist of in-app notification and mails

  

Example of Reminders and Escalations

• Reminder Example: When FRT approaches in 30 minutes, send a reminder to the assigned agent.

• Escalation Example: When FRT is not met, escalate immediately to the assigned agent and send a level 2 escalation to the admin if the ticket is still not resolved after 30 minutes.

Defining SLA Conditions

Users can define SLA policies based on:

• Inbox

• Team

• Tags

SLA Policy Ordering

Users can define the order in which SLA policies are applied to avoid multiple SLAs being applied to a single ticket. Ordering is essential to ensure that only one SLA policy is applied per ticket, preventing ambiguity.

The first matching SLA will override any other SLA that may be applied later when a ticket is reopened or assigned to another agent.

Out-of-Office Settings

Users have the option to include or exclude out-of-office hours in SLA calculations, defined for each metric.

Filters in the “Tickets” Section

1. Breached SLA: Filter to differentiate between tickets where any SLA was breached.

2. Nearing SLA Breach: Filter for tickets nearing SLA breach within a defined time frame.

Metrics and Reporting

1. Ticket Level Metrics

   • Overall SLA Violation %: Percentage of tickets where any SLA was breached.

   
2. Agent Level Metrics

   • Violation % for Agents: Calculated for closed tickets, showing the percentage of violations for FRT, NRT, and RT.

   

Notifications and Highlights

• In app notifications : Notifications for escalations and reminders and breaches

• Activity Messages in Tickets: Indications of SLA status within ticket conversations

• Email notification: An email will be sent to inform about the breached cases

To know more about SLA feature, check this video:

---

FAQ'S

What are the key SLA metrics?

• First Response Time (FRT): Time taken from when a ticket is opened to when an agent first responds.

• Next Response Time (NRT): Time from a customer's message until an agent's next reply.

• Resolution Time (RT): Time from ticket creation to resolution, regardless of agent transfers.

How do reminders and escalations work?

• Reminders: Sent before an SLA is breached to prompt agent action.

  • Example: A reminder is sent 30 minutes before FRT is breached.

• Escalations: Triggered if an SLA is breached, notifying higher-level agents or admins.

  • Example: If an FRT breach occurs, escalate to the assigned agent, and after 30 minutes, escalate to the admin.

Can I customize SLA conditions?

Yes, SLA policies can be defined based on:

• Inbox (specific support channels)

• Team (assigned agent groups)

• Tags (specific ticket types or priorities)

What is SLA policy ordering?

SLA policies follow a set order to prevent multiple SLAs from applying to a single ticket. The first matching SLA overrides others, ensuring clear and consistent application.

Can SLAs exclude out-of-office hours?

Yes, out-of-office settings can be configured to include or exclude non-working hours when calculating SLAs.