SleekView Kanban for Drift conversations
SleekView reads the Drift cache table that mirrors playbook and human conversations, then renders one card per conversation grouped by status so reps drag Open, Pending, and Closed cards and the change flows back to Drift through the API.
♾️ Lifetime License available
Drift's conversational marketing needs a board
The Drift WordPress integration syncs Drift conversations into a local cache (wp_drift_conversations) with status, ownerId, playbookId, and contact tags. Drift's web app shows the live inbox with the agent inbox, leaderboards, and routing rules, but inside WordPress the same data lands as a flat list filtered by status. Teams that want to coordinate playbook follow-ups inside WordPress lose the board view Drift made famous.
Drift uses status values of Open, Pending, and Closed for human conversations, plus the integration tracks a derived bucket for playbook-initiated chats waiting on a human handoff. SleekView reads wp_drift_conversations, joins the user cache for owner name, and the playbook cache for playbook name. Card fronts show conversation subject, contact, owner, playbook tag, account tier, and last message timestamp.
Dragging a card from Open to Pending updates the local cache and queues a PUT to Drift through the integration's API client. drift_after_conversation_update fires locally, Drift returns the confirmed status, and the change appears in Drift's web app within seconds.
Workflow
From cached Drift conversations to a board
Connect Drift integration
Pick status to group by
Choose what shows on each card
Enable drag-and-drop status changes
Sample board
Sample Drift conversations board layout
Comparison
Default Drift plugin vs SleekView
Default Drift integration
- Integration admin lists conversations, no native WordPress kanban view at all
- Reps tab into the Drift web app for board-style queue coordination across teams
- Playbook handoff queue invisible from WordPress without Drift's own inbox open
- Owner reassignment needs the Drift app, not the WordPress integration screen
- Account tier badges visible only inside the conversation detail panel in WP
SleekView Kanban
-
Group by
status,ownerId, orplaybookIdfields - Drag updates the cache and queues a PUT through the Drift API client directly
- Card fronts show contact, owner, playbook, account tier, and last message
- Filter by playbook, account tier, or campaign tag and save per-rep boards
- Same drift_conversations cache renders as Table or Charts in one single click
Features
What SleekView Kanban gives you for Drift
Drag conversations back to Drift
Move a card from Open to Pending and SleekView updates the local cache, queues a PUT through the integration's Drift API client, and Drift's web app and mobile app reflect the change. Routing rules on the Drift side run as if used in inbox.
Per-playbook board views
Build a board per playbook: Pricing, Demo request, Enterprise outreach. Each saved view filters by playbookId, picks its tag palette, and surfaces the custom fields that playbook collects, so the rep lands on a board ready for that motion.
Reassign owners in WordPress
Switch grouping from status to ownerId and the board shows per-rep load. Drag a card between reps to reassign through the Drift API, no tab into the Drift app needed, the rep picks up the new conversation inside the WordPress admin quickly.
Audience
Who uses SleekView Kanban for Drift
Conversational sales reps
Run the shift from a WordPress board instead of the Drift app. Pull from Open, drag to Pending after a meeting link, drop to Closed on a booking. Account tier chips flag enterprise leads without opening the conversation detail.
Sales leads on routing
Group by ownerId for per-rep load, reassign by dragging Handoff cards into a quieter rep's column, then switch to status view to confirm Open cleared and Pending is moving fast enough before the SLA window closes.
RevOps on weekly review
Flip the dataset to Charts for closed-per-day, time in Pending, and per-playbook conversion rate. Kanban handles the live shift, charts handle the retro, both read from the cache without parallel exports.
The bigger picture
Why Drift teams want the board in WordPress
Drift built conversational marketing around the live inbox. Playbooks open the conversation, routing rules assign owners, and the inbox view gives reps a board-like queue across statuses. The Drift WordPress integration brings the data into the admin but stops at a flat list, which means reps who want to coordinate handoffs and pending follow-ups tab into Drift's web app and lose the WordPress context where the rest of the marketing site sits.
A kanban grouped by status reads from the cache table the integration already maintains, writes through the Drift API client it already configured, and brings the queue view into WordPress. Columns count their conversations, account tier chips surface on every card, and dragging across columns updates Drift so the routing rules and playbook automations keep firing without a parallel layer.
Questions
Common questions about SleekView Kanban for Drift
SleekView groups by the status field on wp_drift_conversations because that matches the Open, Pending, and Closed values Drift uses, plus the Handoff bucket the integration derives. You can also group by ownerId or by playbookId for swimlanes.
Yes. SleekView updates the local cache for instant feedback and queues a PUT through the integration's Drift API client. Drift returns the confirmed status, the cache reconciles, and the change appears in Drift's web app and the mobile app.
Yes. Because the writeback uses the official Drift REST API, routing rules, playbook automations, and notification rules configured on the Drift side run exactly as they would when a rep changes status inside the Drift inbox directly.
Yes. Any contact field and any account attribute the integration syncs can be added to the card front. Account tier renders as a colored chip so enterprise leads are visible at a glance without opening the conversation detail panel inside WP.
Yes. SleekView filters the board by the WordPress user's mapped Drift team and ownership access, so a rep only sees conversations they are permitted to see in Drift itself. Cross-team permission mappings are honored for sales leads on routing.
Yes. The integration's list admin and dashboard widget still work, and the kanban adds a queue management view that neither offered before. All three read from the same wp_drift_conversations cache so numbers stay consistent across surfaces.
Yes. Filter the board by playbookId to show only conversations from the Pricing playbook, only conversations from the Demo request playbook, or any combination of playbooks, and save the filter as a named board for the rep running that motion.
SleekView listens for the integration's sync events and refreshes the affected columns when a new conversation lands in the cache. New cards appear with a brief highlight, column counts update, and the rep notices new leads quickly each time.
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