Drift positions itself as a conversational sales platform first, with live chat and chatbot conversations feeding sales reps directly. Every conversation in Drift carries a status like Open, Pending, Assigned, or Closed, plus an assigned rep, a routed playbook, and the contact information collected by the bot. The Drift conversation list shows these in a filterable list, but the broader pipeline view across reps and playbooks needs filters and tab switching.

SleekView Kanban authenticates with the Drift REST API using your access token and pulls every conversation along with its current status, assigned rep, contact email, playbook tag, and last message timestamp. It groups the records into columns by the conversation status field, so Open, Pending, Assigned, and Closed each get a swimlane, and any custom playbook or tag is available as a board filter for sales workflows.

Dragging a card from one status to another writes the change through the Drift API. Routing an Open conversation to a specific rep becomes one drag, marking a conversation Closed cleans it from the active queue, and dragging a Pending conversation back to Open reopens it for further follow-up. The Drift activity log records every change because SleekView calls the same endpoints the Drift admin uses, so attribution and reporting stay clean.

Drift is built for revenue conversations, and revenue lives or dies by how fast a sales rep picks up a hot lead. The default Drift inbox is a chronological list with filters, which is correct for an SDR answering chats one by one but limited for a sales manager who needs to see pipeline shape across reps and playbooks. A kanban view turns the conversation queue into a layout that exposes the shape of the pipeline.

Open is unrouted demand, Pending is bot-collected leads waiting on rep pickup, Assigned is active selling work, and Closed is the result. The relative size of those columns answers questions no list ever does at a glance, like whether the team is keeping up with inbound or whether a specific playbook is creating Pending volume that nobody is touching. Drag and drop matters because Drift status changes are how Salesforce, HubSpot, and reporting all stay in sync with reality, and turning that change into a one-motion drag while keeping the API in the loop makes pipeline hygiene feel correctly sized for sales work.