Conversations • Analytics • SLA Reporting
How to Track SLA Performance in Conversations
SLA Performance Reporting helps you understand how consistently your team responds within configured Conversation SLA targets. The dashboard combines SLA compliance, response-time trends, user performance, and channel performance in one reporting view. You can use these insights to identify response delays, compare team performance, and improve conversation coverage.
What You'll Learn

Learn where to find the SLA Performance Dashboard, how each SLA metric is calculated, how user and channel attribution works, which messages are included in reporting, and how to build additional SLA views using Dashboard and Custom Report widgets.

Important

Only Admins can access the SLA Performance Dashboard. Conversation SLAs must be configured for SLA reporting to produce meaningful results. Dashboard data is available starting May 23, 2026, and only completed SLA evaluations are included in the reported SLA metrics.

1

What is the SLA Performance Dashboard?

The SLA Performance Dashboard is a Conversations reporting view that shows how well your team is performing against configured response-time SLAs. Instead of reviewing individual conversations one at a time, Admins can use the dashboard to evaluate overall SLA adherence, response speed, user performance, and channel performance from one location.

The dashboard can help answer questions such as:

  • How consistently is the team meeting SLA response targets?
  • Which users may need additional coverage or coaching?
  • Which communication channels experience the most SLA breaches?
  • Are response times improving or declining over the selected period?
2

Key Benefits of the SLA Performance Dashboard

Centralized SLA reporting gives managers a clearer view of response performance than isolated inbox checks. Reviewing trends by user, channel, and time period can help identify operational problems before they become persistent service issues.

  • Centralized Visibility: Review key SLA metrics from one reporting area instead of manually checking individual conversations.
  • Faster Issue Detection: Identify when SLA breaches or response times begin trending in the wrong direction.
  • User Accountability: Compare SLA performance across assigned users to identify strong performance, coaching opportunities, or workload concerns.
  • Channel Insights: Compare communication channels to understand where response delays occur most frequently.
  • Better Operational Decisions: Use reporting data to adjust staffing, workflows, coverage, and response processes.
3

SLA Metrics Explained

Understanding how SLA metrics are calculated is essential when comparing performance across users, channels, or time periods. Active SLA timers are not treated as completed outcomes, so the reporting denominator contains only messages whose SLA evaluation has finished.

MetricWhat It Means
SLA Met %The percentage of completed SLA evaluations where a response was sent before the SLA deadline. Messages with an active SLA are excluded.
SLA Breached %The percentage of completed SLA evaluations where the response-time target was missed.
Average Response TimeThe average time taken to respond for messages where a reply was sent and the relevant SLA evaluation is complete.
SLA Met MessagesThe number of messages that received a response within the configured SLA time.
SLA Breached MessagesThe number of messages where the SLA deadline expired before the required response was sent.
SLA Tracked MessagesThe total number of messages with a completed SLA outcome. This includes SLA Met and SLA Breached messages but excludes active SLA evaluations.

Example: If 100 completed SLA evaluations are included and 60 messages were answered before their deadline, the SLA Met percentage is 60%. Messages whose SLA timers are still active are not included in that calculation.

4

User and Channel Performance

Breaking SLA results down by user and channel helps turn a high-level compliance percentage into actionable information. Managers can identify whether delays are concentrated around particular team members, communication channels, or operating conditions.

User Performance

User-level reporting shows SLA results by assigned user. This can help identify consistent performance, coaching opportunities, workload imbalances, and areas where additional coverage may be required.

Attribution rule: SLA performance is attributed to the user assigned at the time the SLA is evaluated. A later reply or reassignment does not retroactively change that completed SLA attribution.

Channel Performance

Channel-level reporting compares SLA performance across supported communication channels. This helps you identify whether certain channels consistently produce longer response times or higher breach rates and may require different staffing or SLA targets.

Channel-level SLA performance report
5

SLA Reporting Rules and Access

SLA reports intentionally exclude some conversations and incomplete evaluations. Knowing these rules helps explain why dashboard totals may differ from the total number of conversations or inbound messages seen elsewhere.

  • Completed Outcomes Only: Only SLA evaluations that have finished as Met or Breached are included in completed SLA reporting.
  • Active SLA Timers: Messages whose SLA evaluation is still active are excluded until the outcome is determined.
  • Read Without Reply: Conversations marked as read without a reply are excluded from SLA reporting.
  • User Attribution: Performance is attributed to the user assigned when the SLA evaluation occurs.
  • Admin Access: Only Admins can access the SLA Performance Dashboard.
  • Historical Availability: SLA Performance Dashboard data is available beginning May 23, 2026.
6

How To Use the SLA Performance Dashboard

Start with overall SLA health, then narrow the analysis to individual users, channels, and time periods. This approach makes it easier to distinguish a broad response-time problem from an issue affecting only part of the team.

Step 1
Confirm Conversation SLAs Are Configured

Before analyzing performance, confirm that Conversation SLAs are enabled and configured with the response-time targets your team is expected to follow.

Step 2
Open SLA Performance

Go to Conversations → Analytics → SLA Performance.

SLA Performance dashboard under Conversations Analytics
Step 3
Choose the Reporting Period

Select the date range that matches the period you want to evaluate. Use a consistent reporting window when comparing performance over time.

Date range controls for SLA Performance reporting
Step 4
Review Overall SLA Health

Start with SLA Met %, SLA Breached %, and Average Response Time. These metrics provide the clearest high-level view of whether your response process is meeting expectations.

SLA overview metrics and performance trend
Step 5
Review Trends

Use the trend controls to compare relevant SLA metrics over time. Trends can help distinguish isolated spikes from sustained changes in team response performance.

SLA trend metric selector
Step 6
Compare Users and Channels

Review the user and channel tables to identify where SLA performance is strongest or weakest. Use the available table sorting controls to focus on the metrics most relevant to your analysis.

User and channel SLA performance table sorting
7

Build Custom SLA Dashboards and Reports

The Conversations SLA Performance Dashboard is not the only place SLA data can be analyzed. SLA widgets can also be added to Dashboards and Custom Reports, making it possible to combine SLA health with other operational reporting or schedule reports for stakeholders.

Available SLA Widgets

Available Conversations SLA widgets include:

  • SLA Met Trend: Tracks the percentage of SLA targets met over time.
  • SLA Breached Trend: Tracks SLA breach percentages over time.
  • Average Response Time Trend: Shows how response speed changes across the selected reporting period.
  • SLA Performance: Compares SLA outcomes across users or message channels.

Add SLA Widgets to a Dashboard

  1. Open Dashboards and edit the dashboard where you want to display SLA data.
  2. Click Add Widget.
  3. Open the Conversations widget category.
  4. Choose the SLA widget you want to add.
  5. Configure its metric, grouping, filters, chart type, and other available display options.
  6. Save the dashboard changes.

Add SLA Widgets to a Custom Report

  1. Go to Reporting → Custom Reports.
  2. Create a report or open an existing one.
  3. Add a widget or report element.
  4. Choose the required SLA widget from the Conversations reporting options.
  5. Configure the metric, grouping, conditions, and display.
  6. Save the report and schedule delivery if needed.

Widget requirement: Conversation SLAs must be enabled before SLA widgets can populate with SLA data. SLA widgets support a maximum reporting date range of one year.

8

Frequently Asked Questions

Q: Who can access the SLA Performance Dashboard?
Only Admins can access the SLA Performance reporting view in Conversations.
Q: Why is my SLA Met percentage lower than expected?
Review the selected reporting period and the conversations that completed SLA evaluation during that period. Only completed Met and Breached outcomes are included in the SLA percentage calculation.
Q: Why are active conversations missing from SLA Tracked Messages?
An active SLA has not produced a final outcome yet. SLA Tracked Messages includes only messages whose SLA evaluation is complete as either Met or Breached.
Q: Are conversations marked as read without a reply included?
No. Conversations that are marked as read without a reply are excluded from SLA Performance reporting.
Q: What happens if a conversation is reassigned?
The completed SLA result remains attributed to the user assigned at the time the SLA was evaluated. A later reassignment does not change that completed attribution.
Q: Why do I not see SLA data from early 2026?
The SLA Performance Dashboard contains data beginning May 23, 2026. Earlier Conversation activity is not available in this dashboard's historical SLA reporting.
Q: Can I create my own SLA reporting dashboard?
Yes. Add SLA widgets to a Dashboard to create an always-on SLA monitoring view, or add them to a Custom Report when you need a shareable or scheduled reporting layout.
Q: Why is an SLA widget showing zero or no data?
Confirm that Conversation SLAs are enabled, the selected period contains SLA activity, the date range does not exceed the widget's supported range, and any user or channel filters are not excluding the expected data.
9

Need Help?

If SLA Performance reporting is unavailable or the results do not match what you expect, use the checks below to narrow down the cause.

  • SLA Performance is missing: Confirm you are an Admin and are looking under Conversations → Analytics → SLA Performance.
  • No SLA results appear: Confirm Conversation SLAs are enabled and that the selected reporting period contains completed SLA evaluations.
  • Totals are lower than expected: Active SLA timers and conversations marked as read without a reply are not included in completed SLA reporting.
  • A user's totals seem incorrect: Confirm who was assigned when the SLA evaluation completed. Reporting attribution is based on that user.
  • Historical data is missing: Do not expect SLA Performance Dashboard data from before May 23, 2026.
  • A channel appears to underperform: Compare its SLA Met %, SLA Breached %, and Average Response Time before adjusting targets or staffing.
  • An SLA widget shows no data: Verify SLA is enabled, review the dashboard date range, and check the widget's user and channel conditions.
  • A Custom Report differs from the Conversations dashboard: Compare the reporting date range, metric, grouping, and widget conditions before treating the difference as a data issue.
  • Issue continues: Collect the selected reporting period, affected user or channel, expected SLA result, actual dashboard values, example conversations, and screenshots of the affected report before contacting support.