WorkestraDocs
ModulesSupport

Support Analytics

Dashboard with date range controls, SLA compliance tracking, CSAT scores, and performance metrics.

Track support performance with visual dashboards, configurable date ranges, and key metrics including SLA compliance and customer satisfaction.

Dashboard Overview

The Support dashboard at /support provides a real-time overview of your team's performance. All metrics respond to the date range selector at the top.

Date Range Selector

Toggle between time periods using the pill buttons at the top of the dashboard:

RangeWhat It Shows
7 daysRecent snapshot for daily standups
30 daysMonthly performance review
90 daysQuarterly trend analysis

All stat cards, charts, and the recent tickets table update when you change the range.

KPI Cards

Five stat cards provide at-a-glance metrics:

CardDescription
Open TicketsTotal open + in-progress + waiting tickets, with breakdown
Avg ResolutionAverage time from ticket creation to resolution
CSAT ScoreAverage customer satisfaction rating (out of 5)
SLA CompliancePercentage of tracked tickets within SLA targets
ResolvedNumber of tickets resolved in the selected date range

SLA Compliance Card

The SLA Compliance card shows:

  • Compliance percentage — % of tickets with an applicable SLA policy that are within their resolution target
  • Breach count — If any tickets have breached their SLA, the count is shown (e.g., "3 breached")
  • "All within SLA" — Displayed when no breaches exist

SLA compliance is calculated using active SLA policies matched to tickets by priority.

Quick Action Cards

Below the charts, two action cards help you stay on top of operations:

Customer Portal Card

Shows your portal URL with a Copy Link button. Share this with customers so they can submit tickets directly.

-> Learn more about the Customer Portal

Unassigned Tickets Card

Quick link to the View Queue of unassigned tickets — tickets waiting to be picked up by an agent.

Dashboard Charts

Volume Trend

Full-width area chart showing ticket activity over the selected date range:

  • Created (blue line) — New tickets per day
  • Resolved (green line) — Tickets resolved per day
  • Gradient fills for visual clarity
  • Hover for exact daily counts

Use For:

  • Capacity planning
  • Identifying incident spikes
  • Measuring resolution rate vs. incoming volume

Status Distribution

Donut chart showing the current breakdown of ticket statuses:

StatusColor
OpenBlue
In ProgressYellow
WaitingOrange
ResolvedGreen
ClosedGray

Priority Breakdown

Horizontal bar chart of tickets by priority:

PriorityColor
UrgentRed
HighOrange
MediumYellow
LowGreen

Channel Distribution

Horizontal bar chart showing how tickets arrive:

ChannelDescription
PortalCustomer portal + widget submissions
EmailEmail-to-ticket via processors
PhoneCall logging
ChatLive chat
APISystem integration

Use For:

  • Measuring which channels customers prefer
  • Deciding where to invest in self-service (portal, widget, KB)

CSAT Score

How CSAT Is Collected

When a ticket is resolved, the customer automatically receives an email with a Rate Your Experience button. This links to a satisfaction survey where they rate their experience from 1 to 5 stars.

-> Learn more about CSAT collection

CSAT Metrics

MetricCalculation
Average CSATMean of all ratings in the date range
Per-Ticket CSATShown in ticket detail sidebar and metadata

CSAT Ratings

RatingScore
Excellent5
Good4
Average3
Poor2
Very Poor1

Recent Tickets Table

Below the charts, a table shows the 5 most recent tickets with:

  • Ticket ID, Title, Type, Priority, Channel, Created time, Assignee

Click View all to jump to the full tickets list.

Interpreting Metrics

Healthy Indicators

MetricTarget
Volume trendStable or decreasing
Open tickets< 10% of monthly volume
Urgent tickets< 5% of total
CSAT score> 4.0
SLA compliance> 90%

Warning Signs

MetricConcern
Volume spikeIncident or product issue
Growing backlogUnderstaffed or slow resolution
High urgent %Quality issues or over-escalation
Declining CSATCustomer frustration
SLA compliance < 80%Policies too aggressive or team capacity issue
High portal/email ratioConsider expanding self-service (KB, widget)

Next Steps