Respond.io is built for cross-channel business messaging on WhatsApp, Messenger, Instagram, SMS, email, and webchat, with a focus on workflows that route, qualify, and follow up on conversations. Every Respond.io conversation carries a status, an assigned agent, a team, a channel, a contact record, and tags. The Respond.io inbox surfaces conversations as filterable lists, which is correct for agents but limited for cross-channel queue visibility from WordPress.

SleekView Kanban authenticates with the Respond.io API using your workspace access token and pulls every conversation along with its current status, assigned agent, team, channel, contact name, subject, tags, and last activity timestamp. It groups the records into columns by the conversation status field, so Open, Pending, Done, and Closed each get a swimlane, and any Respond.io tag is available as a board filter for cross-channel support workflows.

Dragging a card from one status to another writes the change through the Respond.io API. Promoting Open to Pending captures a waiting state, marking Pending as Done resolves the conversation, and moving Done to Closed finalizes the lifecycle. Respond.io workflows, automations, customer notification rules, and webhook integrations all continue to fire because SleekView calls the same endpoints the Respond.io inbox uses internally for status changes and tag updates on conversations.

Respond.io is built for cross-channel business messaging at scale, with WhatsApp Business API, Messenger, Instagram, SMS, email, and webchat all blending into a single agent inbox. That breadth is a strength for teams handling thousands of conversations a day 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 across all the team's channels.

Open is the working queue, Pending is the parked work awaiting customer reply, Done is the agent-resolved work awaiting closure, and Closed is the closed pile. The relative size of those columns answers questions no inbox view ever does at a glance, like whether WhatsApp generates disproportionate Pending volume because of template approval delays or whether Instagram DMs get stuck in Open because of platform throughput limits. Drag and drop matters because Respond.io status changes drive workflows, webhooks, and reporting, and turning that change into a one-motion drag while keeping the API in the loop makes work feel correctly sized.