Freshchat is the Freshworks modern messaging product, blending chat, chatbots, WhatsApp, and Apple Business Chat into a single agent inbox. Every Freshchat conversation carries a status, an assigned agent, a group, a channel, a user record, and a stack of properties. The Freshchat inbox surfaces conversations as filterable lists with status hidden behind view selections, which is correct for chat agents but limited for cross-group queue visibility.

SleekView Kanban authenticates with the Freshchat API using your subdomain and API token and pulls every conversation along with its current status, assigned agent, group, channel, user name, subject, and last activity timestamp. It groups the records into columns by the conversation status field, so New, Assigned, Resolved, and Reopened each get a swimlane, and any Freshchat property tag is available as a board filter for cross-channel workflows.

Dragging a card from one status to another writes the change through the Freshchat Conversations API. Promoting New to Assigned routes the conversation, marking Assigned as Resolved closes it, and dragging Resolved to Reopened restores it cleanly for further engagement. Freshchat IntelliAssign rules, business hours logic, customer notification settings, and webhook integrations all continue to fire because SleekView calls the same endpoints the Freshchat agent app uses internally for any status changes.

Freshchat is built for modern messaging with chatbots, IntelliAssign routing, and a long list of channel integrations including WhatsApp and Apple Business Chat. That breadth is a strength for chat-first teams but makes cross-channel queue shape harder to see because the default inbox folds everything into one list with channel as just one filter among many. A kanban view turns the conversation queue into a layout that exposes shape.

New is the unassigned incoming volume across channels, Assigned is the active work, Reopened is a critical visibility column for re-engagement, and Resolved is the closed pile. The relative size of those columns answers questions no inbox view ever does at a glance, like whether Reopened is growing because canned responses are too aggressive or whether one channel generates disproportionate New volume that needs better routing or chatbot triage upstream. Drag and drop matters because Freshchat status changes drive IntelliAssign, business hours logic, and reporting, and turning that change into a one-motion drag while keeping the API in the loop makes work feel correctly sized.