Read support reports
Review ticket volume, service levels and team performance over a defined reporting period.
On this page
Overview
Reports at #/reports charts ticket volume, statuses, channels, agents, SLA outcomes, and organization bars for a chosen date range. Settings → Other → Reports only stores default range and cache bounds, then links back to #/reports. This is not a billing invoice module.
When to use this
Managers need trends the Inbox cannot show. Cache bounds keep heavy queries off every page load; the queue/cron refresh matters on large sites.
Where to find the controls
Sidebar Reports → #/reports. Defaults: Settings → Other → Reports. Export of workspace settings (not a full ticket dump) is Settings → Other → Import / Export.
Who can make these changes
elegant_support_view_reports. Viewers have this cap. Changing defaults needs manage_settings.
Before you begin
Set the default date range and cache lifetime on the Other → Reports section. Do not expect real-time-to-the-second charts if cache is on.
Follow these steps
- Open #/reports.
- Pick a range.
- Read volume, SLA, and channel tiles.
- Check the organizations chart for B2B load.
- Change range and compare.
- If numbers look frozen, wait for cache/cron or widen the range.
Settings reference
Date from/to, volume series, status breakdown, channel mix, agent workload, SLA hit/breach, organization ticket totals.
Example workflow
Last 30 days shows email 60%, live chat 25%, form 15%, and Acme as the tallest organization bar. The manager staffs mornings for chat hours.
Good practices
Dashboard is for today; Reports is for the month. Export settings from Import/Export before you change Feature Manager.
Important considerations
Reports are operational, not audited finance. WooCommerce revenue is not a core Reports tile. Empty org chart means no tickets with organization_id in range.
If something does not work
Empty charts: range has no tickets, cache stale, or missing view_reports (forbidden screen). Contact support if SQL-sized sites time out after you already raised cache bounds.