No. Chat history, visitor sessions, and conversation logs live in the Tawk.to cloud and are accessible through their dashboard or API. SleekView is a WordPress-side data tool — it surfaces only what's actually stored in your WP database. If your team needs transcripts in WP, you'd need a sync layer using Tawk's API, and SleekView would then tabulate whatever that layer writes locally.

Mostly plugin options — embed config, API keys, feature toggles. Some sites also pipe form captures, pre-chat survey data, or webhook payloads into WP custom tables or postmeta. That's what SleekView tabulates. Schema varies by setup; if you're not sure what's there, point SleekView at the database and it lists candidate sources, then you decide which ones to expose as views.

For option-row config, yes. SleekView can build a view of the Tawk-related wp_options rows and let you edit them inline, which is useful for auditing or quickly toggling embed-side features. Anything controlled from the Tawk dashboard (departments, agent assignments, triggers) has to be changed there — that's the SaaS-side configuration, not the WP-side embed config.

Not directly. SleekView reads and writes WordPress data; it doesn't make outbound API calls to Tawk's servers. For pulling chat data from Tawk's API into WP, or pushing WP edits back to Tawk, you'd need a separate sync layer — Zapier, Make, or custom code. SleekView would then tabulate whatever that sync layer writes to your database, but the API integration itself isn't part of the plugin.

Yes. Any saved view exports to CSV directly from the table header with the columns and filters you've configured. Useful for monthly reports, sharing data with stakeholders who don't have WP admin access, or feeding records into a spreadsheet for offline analysis. No separate export plugin needed.

Yes. SleekView only reads and writes WP-side data — it doesn't touch the Tawk embed script, the widget JavaScript, or the live chat connection. The plugin runs admin-side queries on demand, so there's no front-end weight, no widget interference, and no impact on visitor experience. You can install, configure, and use it without anyone outside the WP admin noticing.

Yes. If your store runs WooCommerce or another e-commerce plugin, you can join Tawk-side captured emails against the orders table by customer email or user ID. That lets you see which chat-started leads converted, which customers initiated chat post-purchase, or which visitors are repeat buyers. The join runs server-side so the view stays fast even with large order histories.

For WP-side records, yes. Filter by email, view all locally stored records, export the result, and inline-edit or delete as needed. For Tawk-cloud records (transcripts, visitor sessions), you still need to use Tawk's data export tooling — that's outside SleekView's scope. But the WP half of a GDPR request is often the part teams forget about, and SleekView covers that cleanly.