The plugin stores the widget ID, agent assignments, and embed rules in wp_options under chatway_settings. Chats themselves live in Chatway. Most production setups wire the Chatway conversation-closed webhook into a custom chatway_chat post type so the WP side has the chart-ready data.

Without the webhook, the WP side only stores the widget ID and targeting rules. Charts are limited to coverage of the widget across wp_posts. For agent, page, rating, and channel cards, configure the Chatway conversation-closed webhook to POST into the chatway_chat CPT first.

The webhook saves the originating page URL as chatway_page postmeta. SleekView joins that postmeta to wp_posts.ID via slug or URL match and renders the bar resolved to post_title, useful for marketing and content teams reviewing widget placement and intent.

Yes. SleekView honors WordPress capabilities for the chatway_chat post type. An agent role sees their own chats while a support lead sees the full team's. The capability filter applies identically to chart cards and the underlying SleekView table view of the same dataset.

Yes. Custom visitor fields pushed by Chatway land in postmeta on each chatway_chat post during webhook processing. Any select-style field becomes a groupBy dimension for a donut, and any numeric field becomes a sum or average aggregation card on the same dashboard.

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

Yes. Clicking a slice or bar opens the SleekView table with the same filter applied. From the agent bar with the lowest rating, one click lands on the exact list of chatway_chat posts that drove the average, each linking to its transcript in the Chatway dashboard.

Charts query chatway_chat 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.