SleekView for Kommunicate for WordPress
Kommunicate's WordPress plugin writes every conversation into the kommunicate_log custom post type. SleekView reads it directly so support leads, bot trainers and customer success each get a sortable, filterable, inline-editable view over the slice they actually run.
♾️ Lifetime License available
Bot conversations and human takeovers in one chronological list
Kommunicate's WordPress plugin embeds the live chat widget and syncs conversation events into a kommunicate_log custom post type, with meta for source (bot or human), status, channel, assigned_agent and conversation_id. The platform's hybrid Kompose-plus-human model means every conversation lands in one log with a clear bot or human source flag.
The default admin renders the log as a chronological list. "All bot conversations that ended in human takeover this week" is not one click away. "All human-handled conversations Lisa is currently working on Facebook" requires manual filtering. Source, channel, assigned agent and status are all in meta but none are surfaced as a column on the row.
SleekView reads the kommunicate_log post type directly. A conversation view shows source, channel, status, assigned agent and last-message time as proper columns, sortable by any of them. Inline edits route through the plugin's CRUD layer where supported, so reassign and status-change operations stay in sync with Kommunicate's platform. Same data behind the chat widget, presented as a workspace the team can actually manage.
Workflow
How SleekView reads your Kommunicate for WordPress schema
Connect the Kommunicate log
Compose your column set
Save and scope the view
Edit inline and ship
Sample columns
A typical Kommunicate for WordPress conversation view
wp_posts + wp_postmeta (kommunicate_log)
| Conversation | Source | Channel | Status | Agent | Last message |
|---|---|---|---|---|---|
| Pricing question | Bot | Web widget | Resolved | Kompose | Apr 24 10:58 |
| Refund request | Human | Open | Lisa | Apr 24 10:51 | |
| Account locked | Bot then Human | Web widget | Pending | Marc | Apr 24 10:42 |
| Shipping update | Bot | Resolved | Kompose | Apr 24 10:31 | |
| Bug report | Human | Web widget | Escalated | Jon | Apr 24 10:18 |
Comparison
Default Kommunicate for WordPress admin vs SleekView
Default Kommunicate conversation log
- Log renders chronologically, source and agent are not visible on the row
- Filtering by source, channel and status together requires re-clicking facets
- Bot handoffs are not surfaced as a distinct status
- Bulk-tagging conversations for bot retraining requires per-row clicks
- No saved per-role views (support queue vs bot-trainer review pile)
SleekView
- Read directly from kommunicate_log with meta surfaced as proper columns
- Pivot source, channel and assigned_agent into typed columns alongside core fields
- Inline-edit status, agent and tags across many conversations in one pass
- Save filtered views per role ("Bot handoffs this week", "Open human queue")
- Switch between conversation and event views in one tabbed page
Features
What SleekView gives you for Kommunicate for WordPress
Conversations with real Kommunicate columns
Combine kommunicate_log fields with source, channel and agent in one filterable workspace. Replaces a chronological list with a workspace support and bot trainers can both use.
Filter combinations the default list can't
Filter to source of bot then human and status of open in one click. Saved filters become role-specific views for support, success and bot trainers.
Inline edits through Kommunicate hooks
Reassign agents, tag conversations for retraining or update status inline. Edits route through Kommunicate's CRUD so the platform sync stays accurate.
Audience
Who uses SleekView for Kommunicate for WordPress
Support leads
Filter to open human conversations and sort by last-message time. Reassign in the row instead of opening each conversation to see who is on it.
Bot trainers
Filter to source of bot then human and tag the conversations the bot got wrong. Bulk-export the filtered set to feed the next Kompose training round.
Customer success
Filter to escalated status across channels and pivot to triage. Catch high-friction conversations before they end up in a churn review.
The bigger picture
Why a hybrid bot inbox needs a workspace, not a feed
Kommunicate sells a hybrid inbox where some conversations end with the bot and others escalate to a human, and the WordPress plugin records both with a clear source flag. The default admin then renders the result as a list, which works for finding one conversation and not for evaluating bot performance or balancing human workload. A filterable, sortable, role-scoped table changes posture entirely.
Support sees only open human conversations. Bot trainers filter to handoffs and tag the bot-misses. Customer success spots escalations before they ripen into churn.
Same Kommunicate log, same WP post type, completely different operational posture without rebuilding any of the integration.
Questions
Common questions about SleekView for Kommunicate for WordPress
Kommunicate for WordPress' own kommunicate_log custom post type and its meta. No data is copied, no analytics service is added, the table renders straight off the log the plugin already maintains.
Yes. The plugin writes one log row per conversation regardless of which engine answered, with a bot identifier in meta. SleekView treats both engines as source values so filters and columns work the same across them.
Yes when the plugin exposes a tag CRUD endpoint. SleekView calls the same action the conversation screen uses, so tags fire the existing hooks and become a filterable column for the next training pass.
Yes when the Kommunicate feedback widget is enabled. Ratings sync to meta, so SleekView shows them as a sortable column alongside source for an instant bot-versus-human quality picture.
No. WordPress indexes the post type by date and ID, and SleekView batches meta joins behind a cache. Logs with hundreds of thousands of kommunicate_log rows render the table in well under a second on typical managed-WordPress hardware.
Yes. Each saved view is scoped by WordPress capability so support leads see the open queue while bot trainers see only handoff conversations. Each role saves its own filter and column presets.
Yes when Kommunicate is connected to multiple channels. SleekView surfaces channel as a column, sortable and filterable, so a per-channel view is one click away.
Yes. Any filtered view exports to CSV with the exact column set on screen. Useful when a quarterly bot review needs the raw conversation data, not just a screenshot.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout