Using SLA Dashboard to Measure Agent Response Times
Updated
How SLA Reporting Dashboard helps you analyze key agent metrics and widgets, and gives you a single view of SLA Dashboards.
A service-level agreement (SLA) is a part of a service contract where a service is formally defined. In practice, the term SLA is used to refer to the contracted delivery time (of the service or performance). SLA metrics are used for measuring agent response times against pre-set objectives (in consideration of business hours, if applicable) to determine brand and employee performance.
Inbound messages arrive in real-time. As a user, replies to the inbound message, the outbound message is time-stamped. The SLA is calculated by taking the difference in time according to the pre-set configuration guidelines. SLA counts only when there is a response. If 100 messages come in but a user responds to 5, the SLA will calculate the average for the 5 responses.
Use Cases of SLA Dashboard
Improve Team Performance and Morale: SLA Dashboard helps you locate teams and individuals who are your true champions and areas of potential training and coaching opportunities. Monitoring your team's progress enables you to adjust targets appropriately and serve employees better.
Unified View: It allows you to have a single view of the SLA dashboards to analyze key agent metrics and performance holistically.
Efficient Resource Allocation: The useful agent metrics and widgets within the platform such as total messages, messages replied, SLA Compliance, etc. enable you to make changes in SLA targets or allocate appropriate resources to meet SLA demands.
To Navigate to SLA Dashboard
Click the New Tab icon
. Under the Sprinklr Social tab, click Reporting within Analyze.
In the top left corner of the Reporting window, click the Dashboard Menu icon
which houses all of the reporting dashboards.On the Reporting Home window, select SLA to open the SLA Dashboard. For more information, see SLA Specific Widgets.
Note: SLA is at the Message level only. |
Below are the scenarios on how SLA is calculated
Case 1
Fan message 1 comes into Sprinklr and Agent/Community Manager responds to it with Brand Message 1.
Fan Message 1 — Fan message created time Monday 08:10 am.
↪Brand message 1 — Brand message replied Time Monday 10:30 am.
Response SLA will be calculated as 2 hours 20 minutes (Without Preset).
Case 2
Fan message 1 comes into Sprinklr and Agent/Community Manager responds to it with Brand Message 1.
Fan Message 1 — Fan message created time Monday 08:10 am.
↪Brand message 1 — Brand message replied Monday Time 10:30 am.
Let's suppose - SLA Preset (Defined business hours) is selected as - Monday - Friday (10 am - 7 pm) then Response SLA will be calculated as 30 minutes (With preset).
Case 3
Fan message 1 comes into Sprinklr and Agent/Community Manager responds to it with Brand Message 1 & with Brand Message 2.
Fan Message 1 — Fan message created time Monday 08:10 am.
↪Brand Message 1 — Brand message replied Time Monday 10:30 am.
↪Brand Message 2 — Brand message replied Time Monday 11:30 am.
Without Preset — Response SLA will be calculated as 2 hours 20 minutes.
With Preset — Response SLA will be calculated as 30 minutes.
The second reply will not be considered for SLA calculation. Sprinklr only calculates SLA on the first response to any fan message and a reply needs to be done from Sprinklr.
Case 4
Fan message 1 comes into Sprinklr and Agent/Community Manager responds to it with Brand Message 1.
Fan Message 1 — Fan message created time Monday 08:10 am.
↪Brand Message 1 — Brand message replied Time Tuesday 10:30 am.
Without Preset — Response SLA will be calculated as 26 hours 20 minutes.
With Preset — Response SLA will be calculated as below:
Let's suppose - SLA Preset (Defined business hours) is selected as - Monday - Friday (10 am - 7 pm)
Business hours are 10 am - 7 pm (on Monday) i.e. 9 hours
Business hours are 10 am - 7 pm (on Tuesday) and the response was made on Tuesday at 10:30 am so the calculation for SLA is 20 minutes.
So, the overall response time as per SLA preset is 9 hours 30 minutes.
Case 5 — Specific to Private Messages
Fan messages M1 to brand, Brand replies natively B1. Fan messages M2, M3, and brand reply natively B2, B3. Fan messages M4 and brand reply from Sprinklr B4.
Fan Message M1
↪Brand Message B1 — Replied Natively
Fan Message M2
Fan Message M3
↪Brand Message B2 — Replied Natively
↪Brand Message B3 — Replied Natively
Fan message M4
↪Brand Message B4 — Replied from Sprinklr
Response SLA will be captured as there is a Fan message prior to a brand message replied from Sprinklr as per threaded conversation.
Note: Only SLA for B4 will be calculated. |
Case 6 — Specific to Private Messages
Fan messages M1 to brand, Brand reply natively B1. Fan messages M2, M3, and brand reply natively B2, B3. Brand reply from Sprinklr B4. Fan messages M1 to brand, Brand reply natively B1.
Fan messages M2, M3, and brand reply natively B2, B3. Brand reply from Sprinklr B4.
Fan Message M1
↪Brand Message B1 — Replied Natively
Fan Message M2
Fan Message M3
↪Brand Message B2 — Replied Natively
↪Brand Message B3 — Replied Natively
↪Brand Message B4 — Replied from Sprinklr
No response SLA will be captured as there is already a brand message prior to a brand message replied from Sprinklr. For private messages, the whole conversation thread is considered as a one-on-one conversation and doesn't have a reply concept as comments.
Note Only SLA for B4 will be calculated. |
SLA Specific Widgets
Specific widgets that you will find in the SLA reporting dashboard are:
Average Response Time trend over time
SLA Compliance
Messages that Met SLA vs. Missed SLA
Distribution of intervals in which messages were responded
SLA Response Scorecard
SLA by the client
SLA by account
Each of these widgets can be drilled down for more in-depth reporting. For more information, see SLA Mapping of Metric Used in Widget.
Note The lowest SLA measurement is possible in seconds. |
SLA Dashboard Toolbar
At the top of the dashboard, there are various stats indicating current percentages, changes, and the amount during the previous period.
Average Response Time trend over time
Time taken by the brand to respond to the message over time.
SLA Compliance
Provided insights on how the brand is performing against the compliance target.
Messages that Met SLA vs. Missed SLA
Count of messages which were answered within SLA threshold VS count of messages that were answered outside the SLA threshold.
Distribution of intervals in which messages were responded
Count of messages in different response time buckets.
SLA Response Scorecard
Shows Fan message, Agent who responded, and reply made by the agent.
SLA By Client
Response time for a different workspace of the customer.
SLA By Account
Shows Account wise Response time.
SLA Mapping of Metric Used in Widget
Widget Name | Metric Used |
Total Messages | Inbound Count |
Messages Replied | The volume of fan messages replied |
Replies Within SLA | The volume of fan messages replied based on SLA Objective |
Replies Outside SLA | The volume of fan messages replied based on SLA Objective |
% Replies Within SLA | % Volume of fan messages replied based on SLA Objective |
% Replies Outside SLA | % Volume of fan messages replied based on SLA Objective |
Average Response Time Trend Over Time | Date, Response SLA |
SLA Compliance | Date, Response SLA |
Messages that met SLA vs Missed SLA | Date, Volume of fan messages replied |
Distribution of intervals in which messages were responded | SLA Frequency, Volume of fan messages replied |
SLA Response Scorecard | Inbound Message, Replied Post, User, Response SLA |
SLA By Client | Client, Response SLA |
SLA By Account | Account, Response SLA |
To Manage SLA Dashboard
Repeat Steps 1 to 3 by referring to section Navigate to SLA Dashboard
On the SLA Dashboard, hover over the dashboard's Options icon
in the top right corner in the Dashboard bar and select the desired option from the drop-down menu.

The following Dashboard options are available:
Create
Custom Interval
Get External Link
Clone
For more information, see Export Options in Reporting
Generate Presentation
Export Dashboard Mapping
Settings