No. SleekView reads what your WordPress database holds. If you run a sync layer that mirrors Help Scout conversation rows into a custom WP table or postmeta, those rows become sortable, filterable, and kanban-able. Without a sync layer, Help Scout conversations stay in the Help Scout app, which is where their reporting, workflows, and mailbox UI already live.

Beacon 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 Help Scout 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 inline through the WordPress write path, with the same hooks firing as a table-based edit.

Only if your stack has a webhook listener or API bridge that propagates WP-side changes to Help Scout. 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, since the conversation itself stays managed in the Help Scout app.

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 conversations should always sit at the top, and low-priority recent ones can wait until the high pile is clear.

Yes. Saved views are gated by capability, so support agents see their own queue, leads see the team 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 assignee or status from inside a report.

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

Help Scout tags and folders are managed in the Help Scout app. If your sync layer mirrors them into a custom WP column, SleekView treats that column the same as any other. Filter by tag, group the kanban by folder, or save a view per folder. Without a sync layer, those values stay cloud-side along with the conversations they describe.