Groove is a simple, friendly help desk that gives small teams a shared inbox with conversations carrying a status, an assigned agent, a mailbox, tags, and a customer record. The Groove inbox surfaces conversations as folder-style lists like Open, Pending, Closed, and Spam, which works well for solo agents but limits cross-mailbox visibility for team leads who need queue shape on one screen.

SleekView Kanban authenticates with the Groove API using your API token and pulls every conversation along with its current status, assigned agent, mailbox, customer name, subject, and last activity timestamp. It groups the records into columns by the conversation status field, so Open, Pending, Closed, and Spam each get a swimlane, and any Groove tag is available as a board filter for cross-mailbox workflows on the kanban screen.

Dragging a card from one status to another writes the change through the Groove API. Promoting Open to Pending captures a waiting state, marking Pending as Closed resolves the conversation, and moving Spam back to Open restores a flagged thread cleanly. Groove rules, automations, customer notification settings, and webhook integrations all continue to fire because SleekView calls the same endpoints the Groove app uses internally for any status change you trigger.

Groove is a friendly, approachable help desk that wins small teams over with its simplicity, but that simplicity makes the cross-mailbox backlog harder to see because every mailbox keeps its own folders and counters. A kanban view turns the conversation queue into a layout that exposes shape across mailboxes. Open is the working queue across all the team's shared inboxes, Pending is the parked work that needs nudging, Spam is the flagged-and-isolated lane, and Closed is the closed pile.

The relative size of those columns answers questions no folder ever does at a glance, like whether Pending is growing faster than Open is shrinking, which usually means agents are parking conversations instead of resolving them. Drag and drop matters because Groove status changes drive rules, automations, customer notifications, and reporting, and turning that change into a one-motion drag while keeping the API in the loop makes mailbox hygiene feel correctly sized for support work without breaking any of the downstream automations.