How to Set Up Inbox SLA

Article author
Learning Center Mekari
  • Updated

An SLA (service level agreement) policy determines the time standards your team must meet when responding to and resolving customer chats. With this policy, you can monitor whether each chat has been handled according to the established time targets.

In Qontak Chat, the SLA feature helps Agents monitor the time remaining to respond to and resolve chats through a countdown display on the Inbox page. If a chat is not handled before the specified time limit, its status will be marked as Breached. In addition, you can monitor overall SLA target achievements and breaches through the SLA Overview dashboard.

Important
Before setting up an SLA policy, make sure you meet the following three requirements:
1. The SLA feature is available in your plan. If the SLA Management menu is not available on the Settings page, contact your Account Manager to request that the feature be added.
2. SLA policies are only available to users with Ultimate and Enterprise plans in the Qontak service suite.
3. Have the appropriate role. Owners, Admins, and Supervisors can create and manage SLA policies. However, Supervisors can only select divisions they are members of.
4. Set office hours (optional). If you want to apply SLA policies based on working hours, both for chats received during and outside working hours, set office hours first through Settings > Inbox > Office Hours.

Therefore, in the explanation below, you will learn how to create, edit, delete, duplicate, and view the activity Log for SLA policies. The steps are as follows.

A. How to Create an SLA Policy

  1. Sign in to your Qontak account, then select the Settings menu.
  2. Then select the “SLA Management” tab, and select “Inbox SLA”.
  3. Next, click “Create Policy”.
  4. Then specify the Policy name and Description of the SLA policy.

    - Policy name (required): Enter the SLA policy name, with a maximum of 60 characters. Make sure each policy has a unique and different name, such as "Premium support".
    - Description (optional): Add a brief description of the SLA policy, with a maximum of 200 characters, to provide additional information about the policy.

  5. Add a Condition and Target to determine how the policy will be applied.
  6. Then click “Add condition” to add the conditions to be applied.

    Next, select Channel or Tagging, then specify the channel or tag you want to include. Note that you can only select channels available in the selected division. The SLA policy will apply to chats that meet at least one of the added conditions. 

  7. Set the SLA time targets by filling in the First response time field to determine the time limit for the Agent to provide the first response after the chat is assigned, Response time to determine the time limit for providing subsequent responses during the conversation, and Resolution time to determine the time limit for resolving the chat. Enter the time value in each field according to the service standards your team wants to apply. All time targets use minutes as the unit. 

     

    Important
    - First response time (required): Set the first response time target to a minimum of 1 minute.
    - Response time (optional): This setting is optional. Confirm the definition and function of this time target with the Product team before using it.
    - Resolution time: Set the chat resolution time target to a minimum of 1 minute. In some accounts, this field is required.

    Example:
    The Customer Service team sets the SLA targets as follows:
    a. First response time: 15 minutes.
    b. Response time: 5 minutes.
    c. Resolution time: 30 minutes.
    If a customer chat is assigned to an Agent at 10:00, the Agent must provide the first response no later than 10:15. During the conversation, the Agent is expected to provide subsequent responses within a maximum of 5 minutes. Meanwhile, the chat must be resolved no later than 30 minutes after the SLA calculation begins.

  8. Then specify the Operational hours. You can choose between 24/7 Availability or Custom , where you can adjust the operating days and time range.
  9. Make sure all the information is correct, then click “Save”.
  10. The following information box will appear, stating that the policy that has been created applies to newly created tickets that meet all the relevant conditions. Click “Save changes” to continue.

  11. The following notification pop-up will appear, stating that the SLA policy was created successfully.

B. How SLA Works

The SLA time calculation begins when a chat is successfully assigned to an Agent, not when the customer sends the first message. Therefore, chats that are still in the unassigned queue do not have an SLA time calculation.

Each SLA policy has two main targets calculated in minutes: First response time and Resolution time. The following explains when the calculation starts and ends for each target:

SLA TargetCalculation startsCalculation stops
First response timeWhen the chat is assigned to the Agent.When the Agent sends the first response in the chat.
Resolution timeWhen the chat is assigned to the Agent.When the chat is successfully changed to the Resolved status.

Example: 
If the First response time target is set to 15 minutes and the chat is assigned to Rina at 10:00, Rina must provide the first response no later than 10:15. If Rina replies at 10:20, the SLA target has been missed and the chat will be marked with the Breached status. 

C. SLA Application Conditions and Mechanisms 

1. Conditions for Messages Counted as Responses

Only messages sent by an Agent to a customer are counted as responses in the SLA calculation. Chatbot replies, automated messages, and internal notes are not considered responses and therefore do not stop the SLA time calculation.

2. SLA Calculation When a Chat Is Transferred to Another Agent

When a chat is transferred (handed over) to another Agent, the SLA calculation for the new Agent starts again from the time the transfer is made. Each Agent has an individual SLA calculation based on the portion of the conversation they handle.

3. SLA Calculation Is Not Affected by Office Hours

The SLA time calculation continues 24 hours a day, including at night, on weekends, and on national holidays. The Operational Hours setting only determines the time range in which an SLA policy applies; it does not stop or pause the SLA time calculation.

4. Determining the SLA Policy Applied to a Chat

Each chat can follow only one SLA policy at a time. If more than one active policy meets a chat's conditions, Qontak Chat determines the applicable policy based on the following order:

  • The policy with the greatest number of conditions that match the chat.
  • If several policies have the same number of conditions, the policy that was modified most recently will be prioritized.

SLA policies are applied live. This means that any changes made to a policy, such as creating, editing, disabling, or deleting the policy, will immediately affect open chats. In addition, adding or removing tags from a chat can cause the chat to move to another SLA policy that matches the latest conditions.

5. Handling Chats That Miss SLA Targets

If a chat exceeds the specified time target, its status will be marked as Breached. This information can be monitored through the Inbox page and the SLA Overview dashboard.

Note that Qontak Chat does not send notifications or automatically transfer chats when an SLA target is missed. Therefore, Supervisors are advised to check the SLA Overview dashboard regularly to monitor target achievement and identify chats with SLA breaches.

D. Managing SLA Policies

All created SLA policies can be viewed through Settings > SLA Management > Inbox SLA. On this page, you can view information for each policy, including its name, description, operational hours, and status. To change a policy's settings, click the “Actions” button on the row of the policy you want to update. 

No.ActionDescription
1Edit (Change policy)Changes to the settings will be applied immediately, including to open chats.
2Copy (Copy policy)A new policy will be created with the same settings as the source policy.
3Delete (Delete policy)The policy will be permanently deleted and cannot be restored. However, historical data on the dashboard will remain stored.
4Enable and disable policyDisable: Chats will no longer be calculated using the policy. If another active policy matches, that policy will be applied. Enable again: Chats that meet the policy's conditions will once again be calculated using the policy.

E. SLA Display on the Agent Inbox Page

Agents can monitor SLA information in two sections of the Inbox page: the badge in the chat list and the SLA Target panel on the chat details page. 

1. Badge in the Chat List

Each chat assigned to an Agent displays a time-countdown badge next to the customer's name, such as 12m (12 minutes) or 1h (1 hour). This badge shows the time remaining before the next SLA target is reached, starting with First response time, followed by Resolution time.

If the Resolution time target is missed, the badge will turn red and display the Breached status.

Note that the SLA badge is not displayed for unassigned chats, group chats, or Instagram comment chats.

2. SLA Target Panel

To view detailed SLA achievement information, open the chat you want to check, then locate the SLA Target panel in the chat details section on the right.

This panel displays two main targets: the First response time target and the Resolution time target. Each target has its own status, allowing Agents to monitor SLA achievement for each stage of chat handling.

Displayed StatusDescription
Timer with time remainingThe SLA target is still within the specified time limit (on track).
Yellow badge with time remainingThe time to meet the SLA target is almost up. The remaining time is less than half of the First response time target or less than one-third of the Resolution time target.
Red badge with timeThe SLA target has been missed, but the time calculation is still running. The displayed time shows the delay duration up to a maximum of 30 minutes.
BreachedThe SLA target has been missed by more than 30 minutes, or the Agent has not responded before the chat is changed to the Resolved status.
Completed in + timeThe SLA target was successfully met. The displayed time shows the time remaining when the target was achieved.
Breached for + timeThe Agent responded to or resolved the chat after the SLA time limit had been missed. The displayed time shows the delay duration.
"Target countdown starts once agent is assigned."The chat has not been assigned to an Agent, so the SLA time calculation has not started.

Agents can only view the SLA time calculation for the portion of the conversation they handled. Meanwhile, Owners, Admins, and Supervisors can view the SLA time calculation for the first Agent assigned to the chat. 

F. How to Monitor and Export SLA Data 

  1. Go to the Reports menu.
  2. Then select the “Agent performance” tab and click “SLA”.
  3. This dashboard displays two reports: First response time per Room ID and Resolution time per Room ID. Each row represents one chat and includes information about the Agent, channel, assignment time, target time limit, actual time, and SLA time indicator. Missed targets are marked in red. 
  4. The dashboard can also display summary cards showing the average first response time (Average First Response Time) and average chat resolution time (Average Resolution Time) to help you monitor overall team performance. 
  5. To export SLA data, click the Export button on one of the tables, then select one of the following export methods:

    - If you select Export via email, the exported file will be sent to your email address.
    - If you select Direct report, the exported file will be prepared and can be downloaded directly through the application. To monitor the export process, open Reports > Export.
     

G. Frequently Asked Questions

1. Why does the SLA timer not appear on a chat?
The SLA timer is only displayed for chats that have been assigned to an Agent and meet the conditions of an active SLA policy. The timer will not appear on unassigned chats, group chats, or Instagram comment chats. If the timer does not appear on a chat that should meet these conditions, make sure your plan includes the SLA feature.

2. Does the SLA time calculation stop at night, on weekends, or on holidays?
No. The SLA time calculation continues 24 hours a day, including at night, on weekends, and on national holidays. The Operational Hours setting only determines which SLA policy applies to a chat; it does not stop the time calculation.

3. Are chatbot replies or internal notes counted as First response time?
No. Only messages sent by an Agent to a customer are counted as the first response. Chatbot replies, automated messages, and internal notes are not included in the calculation.

4. How is SLA time calculated if a chat is transferred to another Agent?
When a chat is transferred to another Agent, the SLA time calculation for the receiving Agent starts again from the time the transfer is made. Each Agent has an individual SLA time calculation based on the portion of the conversation they handle.

5. Can one chat follow two SLA policies at the same time?
No. A chat can follow only one SLA policy at a time. If several active policies meet the chat's conditions, the policy with the greatest number of matching conditions will be prioritized. If the number of conditions is the same, the policy updated most recently will apply.

6. Do SLA policy changes affect open chats?
Yes. Every SLA policy change will be applied immediately to open chats. These changes include creating, editing, disabling, or deleting a policy. However, these changes do not affect historical data already recorded on the dashboard.

7. Will Agents receive a notification when a chat misses an SLA target?
No. Qontak Chat does not automatically send notifications when an SLA target is missed. Chats that miss the target will be marked with the Breached status on the Inbox page and the SLA Overview dashboard.

8. Can two SLA policies use the same name?
No. Each SLA policy must have a unique and different name. The system also treats names that differ only in capitalization as the same name. Therefore, names such as "Premium Support" and "premium support" cannot be used for two different policies.
 

That is how to manage Inbox SLA policies.