No. Charts run on what your WordPress database holds. If your stack writes synced ticket rows, Web Widget leads, or webhook payloads into WP tables or postmeta, those rows feed the cards. Zendesk's own Explore continues to handle cloud-side metrics like response time and CSAT, which belong on their side of the boundary.

Yes. New, open, pending, on-hold, and solved each become a slice of a donut grouped by status, or a bar in a horizontal Bar card. If your sync layer writes a custom status mapping, the chart reflects the values actually written, so the legend matches what your team sees in the Zendesk app.

If your synced rows include priority and timestamps, both are chartable. A Donut on priority shows the urgency mix across the queue, an Average on hours-since-last-response per priority gives a quick SLA read, and a Bar grouped by SLA bucket (under 1h, 1-4h, 4-24h, over 24h) is a useful escalation visual.

Yes. If the synced row has a requester email, SleekView Charts can join against wp_users and WooCommerce orders. A Number card on open tickets from customers with active subscriptions, or a Bar grouped by customer LTV bucket, both work as long as both data sets live in the same database.

Cards aggregate live against the source tables each time the dashboard loads, then cache briefly for the same viewer to keep navigation responsive. When the sync layer writes new ticket rows or webhook events, the next dashboard refresh reflects them with no manual rebuild step.

Yes. Saved dashboards are capability-scoped, so a support lead dashboard is invisible to a contributor and a marketing dashboard is invisible to a support agent. Exports honour the same checks, which keeps role separation clean across the same source tables.

Yes. Each card exports its underlying rows as CSV for spreadsheet hand-off, and the rendered chart exports as PNG for board decks and weekly reports. Useful when the Monday dashboard feeds the internal review and the customer summary without rebuilding the same numbers in a separate tool.

The integration has had several iterations over the years; SleekView Charts doesn't depend on a specific plugin version. It reads the WP database directly, so whatever options, custom tables, or postmeta the active integration writes is what the charts surface. If the schema changes, you re-pick the source columns in the agent UI, no code migration required.