No. Chat transcripts, visitor sessions, and operator activity live in the Tidio cloud and are accessible through the Tidio dashboard or their API. SleekView is a WordPress-side data tool — it surfaces only what's stored in your WP database. If you need transcript data in WP, you'd need a sync layer (Tidio's API plus Zapier, Make, or custom code) and SleekView would then tabulate whatever that layer writes locally.

Mostly wp_options for Tidio plugin config, plus any custom tables or postmeta keys your form or integration plugins write to. Schema varies by setup — Gravity Forms entries, WPForms entries, Fluent Forms submissions, or webhook landing tables all look different. SleekView lets you point at any of them and exposes the columns inside as sortable fields. No assumption about a single schema.

Yes for fields that live in WordPress — status flags, segment tags, assignment, custom fields written locally. Anything stored in Tidio's cloud (visitor properties, conversation tags, operator notes) has to be edited there. SleekView is honest about that boundary: WP-side edits go through standard WordPress hooks, and changes intended to flow back to Tidio still require Tidio's API.

No. SleekView is a WP-side data tool by design — pushing edits back to Tidio's cloud would require their API or a sync platform like Zapier or Make. The combination works well: SleekView gives you the list and triage UX in WordPress, your sync layer handles the round trip to Tidio when needed. Many teams find they only need WP-side edits anyway.

No. Views run admin queries on demand against the relevant tables and don't add front-end weight. The chat widget loads from Tidio's CDN as it always does, untouched. SleekView is admin-only — it doesn't enqueue scripts or styles on the public site, doesn't intercept page requests, and doesn't add database overhead outside the admin user context.

Yes. Any saved view exports to CSV directly with the columns and filters you've set. Useful for monthly marketing reports, handing a list to a sales rep without API access, or feeding data into a spreadsheet for analysis. The export is a one-click action from the view header — no separate export add-on or external tool needed.

For the WordPress-side data, yes. Filter by email, view all locally stored records associated with that address, export the result, and inline-delete or mark for redaction. For the Tidio-cloud-side data (transcripts, visitor sessions), you still need to use Tidio's data export tooling. But SleekView covers the WP half of the request, which is often the part teams forget about.

Yes. The plugin writes its settings as wp_options rows. SleekView can build a view scoped to those option keys, which is useful when you've inherited a site and need to audit the chat configuration without clicking through the Tidio settings panels. Things like enabled features, API keys (redacted), and integration toggles all surface as readable rows.