HelpCrunch combines live chat, email, and chatbots into a single agent inbox, with conversations carrying a status, an assigned agent, a customer record, and tags for routing. The HelpCrunch dashboard surfaces conversations as a chronological list with filters for open, unassigned, and resolved, which works for an agent answering messages live but limits cross-team visibility into the broader queue.

SleekView Kanban authenticates with the HelpCrunch API using your project token and pulls every conversation along with its current status, assigned agent, customer name, channel, and last message timestamp. It groups the records into columns by the conversation status field, so Open, In Progress, Snoozed, and Closed each get a swimlane, and any HelpCrunch tag is available as a board filter for cross-channel workflows.

Dragging a card from one status to another writes the change through the HelpCrunch API. Promoting an Open conversation to In Progress assigns it to the dragger, snoozing parks a conversation cleanly with an expected wake time, and closing it clears the active queue. HelpCrunch automations, customer notification rules, and the audit log all continue to fire because SleekView calls the same endpoints the HelpCrunch agent app uses internally, so reporting and integrations stay clean.

HelpCrunch bundles chat, email, and chatbots into one inbox, which is great for an agent answering messages but makes cross-channel queue shape harder to read because everything folds into the same list. A kanban view turns the conversation queue into a visible layout that exposes shape. Open is the unassigned incoming volume, In Progress is the active work owned by individual agents, Snoozed is the parked work that needs nudging at a specific time, and Closed is the closed pile.

The relative size of those columns answers questions no list ever does at a glance, like whether Snoozed is growing because the team uses it as a parking lot or whether In Progress is stalling because conversations get picked up but never resolved. Drag and drop matters because HelpCrunch status changes are how automations, notifications, and audit logs stay in sync with reality, and turning that change into a one-motion drag while keeping the API in the loop makes the work feel correctly sized for support teams running multi-channel support across WordPress.