Use the support dashboard
Review open work, identify service-level risks and find the next action for your team.
On this page
Overview
The dashboard is the SPA home at #/. It summarizes ticket volume, waiting work, and SLA risk so an agent can jump to Inbox, a ticket, or Settings without opening every module.
When to use this
Use it at the start of a shift to see what is breached or unassigned before filtering Inbox. It is not a replacement for Reports, which cover date ranges and charts.
Where to find the controls
Sidebar Overview / home icon → #/. Documentation is the sidebar item above Free/Dev; Dashboard is the first item.
Who can make these changes
Anyone with elegant_support_view_ticket. Cards that deep-link to Settings still require manage_settings to edit. Additional capability requirements: elegant_support_view_reports.
Before you begin
No separate dashboard settings. Counts follow Inbox views, SLA engine state, and Feature Manager (hidden modules do not appear as broken cards).
Follow these steps
- Open HelSup.
- Read open / waiting / SLA chips.
- Click through to #/inbox or a ticket workspace.
- Use Command Palette if you already know the ticket number.
Settings reference
Summary cards, recent activity, and shortcuts. Exact tiles depend on role and enabled features (AI Copilot is marked beta and gated by ai_copilot).
Example workflow
Monday 09:00: dashboard shows three SLA at-risk tickets. The agent opens Inbox, sorts by SLA deadline, and works those first.
Good practices
If counts look stale, the queue may not have ticked. Production should use system cron; WP-Cron only runs when the site has traffic.
Important considerations
Do not treat dashboard charts as audited finance reports. WooCommerce order context is optional and only appears when that plugin is active and the agent has elegant_support_view_commerce.
If something does not work
Empty dashboard after login: bootstrap failed — retry, then check REST 401/403 and that you are not cached out of /wp-json/elegant-support/. Hard-refresh after a plugin update.