No. Charts run on what your WordPress database holds. If your stack writes synced conversation rows, Beacon leads, or webhook payloads into WP tables or postmeta, those rows feed the charts. Help Scout's own reports continue to handle mailbox-level metrics like response time and customer satisfaction, which belong on their side of the boundary.

A Number card for a top-level KPI like total synced conversations, a Pie or Donut for status distribution, a horizontal Bar for ranked assignee workload, and an Area or Line for lead and webhook volume over time. Radar and Radial cards work well for multi-dimensional comparisons like response-time bucket versus priority, but most teams start with the four basics.

If your Beacon bridge writes the source URL into a column on the capture table, yes. A horizontal Bar grouped by source page gives a ranked view of which pages drive contact, the same data marketing usually pulls into a spreadsheet. Saved dashboards keep that view one click away instead of one query away.

Yes when the source is configured as a join across the synced conversation table and WooCommerce orders. A Bar of conversation volume per customer LTV bucket, or a Number card of total open conversations from customers with active subscriptions, both work as long as the data lives in the same database.

Cards aggregate live against the source tables each time the dashboard loads, then cache briefly for the same viewer so subsequent page loads stay responsive. If your sync layer writes a new conversation row, the next dashboard refresh reflects it; there is no manual rebuild step or pre-computed cube to invalidate.

Yes. Saved dashboards are capability-scoped, so a support lead dashboard with workload and triage cards is invisible to a contributor, and a marketing dashboard with Beacon lead trends is invisible to a support agent. Inline edits and exports honour the same checks, which keeps role separation clean across the same source data.

Yes. Each card exports its underlying rows as CSV for hand-off to a spreadsheet, and the rendered chart exports as PNG for inclusion in a board deck or weekly report. Useful when the same dashboard feeds the internal Monday review and the external client summary without duplicating the work in another tool.

SleekView Charts reads the database directly, so whatever columns your sync layer or Beacon bridge writes are what shows up in the agent UI when you compose a card. Re-picking columns when a schema changes is a UI action, not a code migration, which matters when the integration layer in your stack evolves faster than the helpdesk itself.