No. SleekView Charts reads what your WordPress database already holds: captured leads, channel mapping rows, synced rows where a sync layer writes them, and webhook records. Without a sync layer, the inbox stays in the Front app.

Plugin configuration in wp_options, plus channel mapping data when WordPress sources are wired into Front inboxes. Captured leads depend on which form integration captures them, sometimes a custom table, sometimes postmeta, sometimes a direct pipe to Front without a WP record.

Yes. Filters compose at the dashboard level. Scope every card to a specific source page, UTM, or date range with a single saved view. Each chart recomputes against the filtered source.

Only if your stack has an API bridge or webhook listener that propagates WP changes to Front. The chart dashboard itself is read-only; the SleekView table handles row-level edits, and the bridge handles the round trip.

No. SleekView Charts is admin-side only. It does not enqueue scripts on the public site or intercept page requests. The Front widget loads exactly as it always does, with no performance impact.

Yes. Charts, table, and kanban layouts read from the same source. Switching between them is a layout toggle, not a data migration, so a filter set saved at the source applies wherever you view it.

Yes. Each card exports its computed series as CSV or JSON. Useful for handing data to a non-WP stakeholder, monthly reporting, or pulling chat-lead data into a spreadsheet for ad-hoc analysis.

Yes. Saved dashboards are gated by capability so marketing sees source-page cards, sales sees the channel distribution, and reporting roles get a read-only view of the same source. Inline edits remain in the table layout.