The plugin itself stores settings and rules in wp_options, not transcripts. Most production setups configure the Olark chat-ended webhook to POST into a custom olark_chat post type with operator, group, page URL, and duration as postmeta. SleekView charts that CPT directly with no further setup.

Yes, but only for the data the plugin itself keeps locally. That covers the targeting rules in olark_settings and the per-page widget-loaded log if you enable it. For chat-level cards (operator, group, duration) you need the webhook landing posts into the olark_chat CPT first.

Either by enabling the webhook recorder in popular wrapper plugins or by registering the CPT in functions.php with the slug olark_chat and POSTing webhook payloads into it. SleekView picks up any registered post type automatically, so name choices are flexible if your project uses a different convention.

Yes. SleekView honors WordPress capabilities, so an agent's dashboard counts only the olark_chat posts they can read while a manager's covers the full team. The same capability filter applies identically to chart cards and the underlying SleekView table.

Pre-chat survey responses land in postmeta on each olark_chat post when the webhook payload is mapped to meta keys. Any select-style field becomes a groupBy dimension for a donut or bar, and any numeric field becomes a sum or average aggregation card.

Charts run aggregate queries on view load. Open the dashboard and the numbers reflect the current state of the olark_chat CPT and any webhook posts written up to that moment. There is no caching layer to clear and no scheduled job that lags behind live data.

Yes. Clicking a slice or bar opens the SleekView table with the same filter applied. From the operator with the highest bar, one click lands on the exact list of olark_chat posts they handled this week, ready for a transcript review.

Charts query the olark_chat CPT using the same indexes WordPress maintains for post-type and postmeta lookups. On sites with tens of thousands of chats archived, dashboards load in well under a second from the admin context with no extra database tuning required.