Kommunicate for WordPress' own kommunicate_log custom post type and the meta fields it writes per record. No data is copied, no analytics service is added, the cards render straight off the log the plugin already maintains in WP.

Yes. The plugin writes one log row per conversation regardless of which engine answered, with the bot identifier in meta. SleekView Charts treats Kompose and Dialogflow as slices of the same source dimension, so the bot vs human pie counts both engines as bot-resolved.

Indirectly. The clearest proxy is handoff rate: conversations that started with the bot and ended with a human. A high or rising handoff rate suggests the bot is missing intents or content, and an Area trend surfaces the direction even without an explicit confidence score.

Yes when the Kommunicate feedback widget is enabled. Ratings sync to meta, so a Number card for average rating and a Pie split across rating values give an instant view of conversation quality across both bot and human cases.

No. WordPress indexes the post type by date and ID, and SleekView Charts batches meta joins behind a cache. Logs with hundreds of thousands of kommunicate_log rows render the dashboard in well under a second on typical managed-WordPress hardware.

Yes. Each saved chart dashboard is scoped by WordPress capability, so support leads see operational cards while bot trainers see accuracy and handoff cards. Each role saves its own filter presets independent of the others.

Yes when Kommunicate is connected to multiple channels (web widget, Facebook, WhatsApp, Line). A Pie grouped by channel splits conversations across them, and a stacked Bar can slice each channel by bot vs human for a deeper view of where the bot is most effective.

Yes. Every chart card is backed by a SleekView dataset, so the export button on the table view exports exactly the filtered rows powering the chart. Useful when a quarterly bot review needs the raw conversation data, not just the visual.