No. SleekView reads what your WordPress database holds. If you run a sync layer that mirrors HelpCrunch conversations into a custom WP table or postmeta, those rows become sortable, filterable, and kanban-able. Without a sync layer, HelpCrunch conversations stay in the HelpCrunch app, which is where the team management and reporting features already operate.

Plugin configuration sits in wp_options. Captured leads from contact forms or pre-chat surveys depend on which integration captures them. Some bridges write to a custom table, some to postmeta, some pipe directly to HelpCrunch without a WP record. SleekView surfaces whichever path your stack uses, with the columns inside, instead of assuming a single schema.

Yes. Pick the status column as the kanban grouping field and the same source renders as a board with one column per status value. Drag a card from open to in-progress and the row's status field updates through the WordPress write path with the matching hooks firing.

Only if your stack has a webhook listener or API bridge that propagates WP-side changes to HelpCrunch. SleekView itself edits WordPress data only, which keeps the boundary predictable. Many teams find WP-side edits are enough for the records they sync locally.

No. SleekView is admin-side only. It doesn't enqueue scripts on the public site, doesn't touch the embed code, and doesn't intercept page requests. The HelpCrunch widget loads exactly as it always does, with no performance impact and no behaviour change visible to site visitors.

Yes. Sorts compose, so primary by priority and secondary by age (oldest first within each priority bucket) is a single saved view. Useful for triage queues where high-priority stale leads should sit at the top and recently captured low-priority ones can wait.

Yes. Any saved view exports to CSV with the columns and filters you've configured, regardless of layout. Useful for handing data to a non-WP stakeholder, monthly reporting, or pulling chat-lead data into a spreadsheet for ad-hoc analysis without writing a query against the custom table.

Yes. Saved views are gated by capability, so sales sees the active lead queue, ops sees the webhook-error queue, and reporting roles get a read-only view of the same source. Inline edits honour the same capability checks, which prevents an analyst with view access from accidentally changing status or assignee.