SleekView Kanban for AI Engine Pro
AI Engine Pro stores chatbot discussions, queries and statistics in custom tables. SleekView Kanban reads those rows directly and renders one card per conversation, grouped by status so you can triage at a glance and drag cards to update the source.
♾️ Lifetime License available
Triage AI Engine discussions without leaving WordPress
AI Engine Pro keeps every chatbot conversation in the mwai_chats table and every query log in mwai_logs, with a status column on each row. The plugin's built in list view is fine for browsing, but the moment you want to triage flagged conversations, track open follow ups or move resolved chats out of sight, you are stuck filtering one column at a time.
SleekView Kanban points at the same tables, picks the status field as the grouping column and renders one card per discussion. Each card shows the user, the model, the token cost and the last message preview. You drag a card from Pending to Reviewed and the row is updated in mwai_chats immediately, no admin reload, no exports.
Because every column count, card title and meta field is bound to the live row, the board always matches what the AI Engine Pro dashboard would show. You stop guessing whether a conversation was already handled by another moderator.
Workflow
From AI Engine table to live kanban
Connect the AI Engine tables
Choose status as the grouping column
Pick which fields show on the card
Drag a card, write the status back
Sample board
Sample AI Engine discussion board
Comparison
AI Engine logs view vs SleekView Kanban
AI Engine list view
- Discussions appear as a flat paginated list with one status filter at a time.
- No drag and drop, status changes require opening each row in the editor.
- No grouped counts, you cannot see open vs resolved totals on one screen.
- Card style previews are not available, only a raw text snippet column.
- Mobile triage is painful, the list view assumes a wide desktop admin grid.
SleekView Kanban
-
Reads
mwai_chatsandmwai_logsdirectly, no extra mirror table. - Drag and drop writes the new status straight back to the AI Engine row.
- Live column counts always match the row totals in the AI Engine dashboard.
- Card front shows model, token cost and last message in a single glance.
- Works on tablet and phone so moderators can triage from anywhere.
Features
What SleekView Kanban gives you for AI Engine Pro
Two way sync with AI Engine
Every drop in a new column triggers a safe update on the AI Engine source row. Reload the AI Engine dashboard and the new status is already there. No background jobs, no eventual consistency, no risk of a kanban move getting lost in a queue.
Filter before you render
Layer filters on top of the kanban view so a moderator only sees discussions for one chatbot, one model or one date range. The grouping column stays the same, so muscle memory carries across boards and the column counts always reflect the current filter.
Assignable cards
Add an owner column to the AI Engine table or map an existing user reference field. SleekView renders the owner avatar on the card front so the team knows who is handling each conversation. Reassigning is a drag into another swim lane.
Audience
Where AI Engine Pro teams use the kanban view
Support handoff triage
Flagged chatbot sessions land in Pending review. Moderators drag confirmed support issues into a column wired to your ticket plugin and the AI Engine row carries the linked ticket ID.
Safety and guardrail review
AI Engine Pro flags rule violations on the conversation row. The kanban view groups every flagged session into one column so the safety lead clears the backlog without filtering pages.
Sales qualified conversation routing
Chats marked as sales leads sit in a column piped to the sales team. Card meta shows model used and token spend so reps know how warm the lead is before they reply.
The bigger picture
Why a kanban beats a list for AI moderation
AI Engine Pro is one of the busiest chatbot plugins in WordPress, and busy chatbots produce a lot of rows. A long flat list works for archiving, but it falls apart the moment more than one person is responsible for the queue. Moderators end up reopening conversations the team already handled, safety reviewers miss flagged sessions because they were buried on page seven, and sales reps cannot tell which leads were already contacted.
A kanban view solves the part that the list cannot. Status is no longer a filter you toggle, it is the layout itself. Open work piles up visibly, resolved work clears the screen, and the count at the top of every column is the actual row total in the source table, not a stale stat.
Because SleekView writes back to the AI Engine tables directly, you do not need a separate moderator dashboard, a custom database or a job queue. The kanban view is the same data, surfaced in the shape that fits the work.
Questions
Common questions about SleekView Kanban for AI Engine Pro
Yes. SleekView reads from the AI Engine tables that store discussions and queries, so both sources can be turned into kanban boards. You pick the source table when you create the view, and SleekView shows the columns it found, including any custom field you added in AI Engine settings.
Yes. Every drop runs a safe update on the underlying row using the AI Engine primary key. The new status persists immediately, so the next time you load the AI Engine admin or the chatbot dashboard, the change is already there. No background sync, no eventual consistency.
SleekView renders one column per distinct value it sees in the grouping field. If AI Engine writes a new status into a row, a new column appears the next time the view loads. You can lock the board to a fixed set of statuses if you prefer a stable layout.
Yes. The card editor lets you pick a title field plus a single meta line that can combine multiple AI Engine columns. A typical card shows the user as the title and a meta line like GPT-4o, 1.2k tokens, 3 minutes ago, all of which come from the live row.
Yes. SleekView paginates inside each column so a board with a million archived chats still loads in well under a second. The status write is a single indexed update on the primary key, so even a busy chatbot will not feel a noticeable hit on drag and drop.
Yes. SleekView inherits the WordPress capability you configure on the view, so a moderator role can see and move cards while a contributor role can only view. You can also limit which AI Engine columns appear on the card front based on role.
Yes. A common setup is one board grouped by status for triage and a second board grouped by model or by chatbot ID for capacity planning. Both read the same rows, neither needs a duplicate database, and both update live as new conversations arrive.
Yes. SleekView never owns AI Engine data. The plugin reads and updates the AI Engine tables in place, and if you deactivate SleekView the rows continue to live in mwai_chats and mwai_logs untouched. You only lose the kanban view, not the conversation history.
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