✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for LiveChat by LiveChatInc

SleekView Kanban groups LiveChat conversations into Queued, Chatting, Pending, and Closed columns so agents drag a chat to update its status in one gesture instead of opening the conversation panel and using the chat menu for every state change.

♾️ Lifetime License available

SleekView Kanban board for LiveChat (livechatinc.com)

LiveChat chats on a real kanban board

LiveChat exposes each conversation with a status like queued or chatting or pending or closed, an assigned agent, a group, and a visitor record. The native LiveChat agent app shows chats in a vertical tab list that highlights whoever last sent a message. It is great for replying but it does not show queue health across status values at a glance.

SleekView Kanban reads the LiveChat conversations mirrored into WordPress and groups them by status. The board renders Queued, Chatting, Pending, and Closed as labelled columns. Cards expose visitor handle, last message snippet, agent, group, and wait time, so an agent can decide what to do next without leaving the board for the LiveChat panel.

Drag a Queued chat onto an agent's lane in Chatting to take it. Drag a Chatting card to Pending while waiting on a customer reply. Drag closed chats to Closed at the end of the shift. SleekView writes the new status back to the LiveChat conversation record, so the change is visible everywhere the conversation is read across the workspace.

Workflow

From LiveChat tabs to a working board

1

Connect the conversation store

Point SleekView at the LiveChat conversation table mirrored into WordPress. SleekView reads every conversation, including status, group, agent, visitor handle, last message snippet, and timestamps, without altering the LiveChat agent app or its routing rules in any way.
2

Pick the status column

Select the conversation status field as the kanban grouping. SleekView reads the distinct values, including Queued, Chatting, Pending, and Closed, and renders each as a column with a live count of conversations sitting in that state at this moment.
3

Choose what shows on each card

Decide which LiveChat fields render on the card front. Most teams pick visitor handle, last message snippet, assigned agent, group, and queue wait time. Cards give enough context to triage without opening the conversation in the LiveChat agent app.
4

Enable drag and drop

Turn on drag and drop so agents move chats between columns by dragging cards. SleekView writes the new status to the LiveChat conversation record, refreshes the column counts, and propagates the change to anyone else viewing the same board within seconds.

Sample board

Sample LiveChat board across four columns

A snapshot of LiveChat conversations split across Queued, Chatting, Pending, and Closed, each card showing visitor, last message, agent, group, and wait time.
Queued
11
Pricing comparison with competitor
Group: Sales - waiting 4m
Cannot finish credit card checkout
Group: Support - waiting 6m
Need invoice copy for accounting
Group: Billing - waiting 2m
Chatting
27
Walking through SSO config steps
Agent: Anders - 3m active
Helping with custom field mapping
Agent: Beatriz - 6m active
Quoting yearly subscription seats
Agent: Caroline - 2m active
Pending
6
Waiting on dev team for bug fix
Agent: Anders - 28m wait
Visitor stepped away mid conversation
Agent: Beatriz - 17m wait
Finance to confirm refund eligibility
Agent: Caroline - 41m wait
Closed
138
Resolved widget install on Shopify
Agent: Anders - closed today
Confirmed plan upgrade to Team plan
Agent: Beatriz - closed today
Issued partial refund per policy
Agent: Caroline - closed today

Comparison

LiveChat default tabs vs SleekView Kanban

Default LiveChat agent app

  • Default LiveChat tab list highlights newest message, not the state of the queue
  • Setting a chat to Pending happens inside the per chat menu one chat at a time
  • Groups and agents are visible only after clicking into the chat detail panel
  • Queue health by status is split across reports rather than visible on the work screen
  • Bulk close at end of shift is one chat at a time inside the agent app

SleekView Kanban

  • Drag a LiveChat conversation from Queued to Chatting to pick it up
  • Column counts surface backlog in Pending without opening reports
  • Cards show visitor, agent, group, last message, and wait time at once
  • Filter the board by group so Sales and Support each see their own queue
  • End of shift close becomes a bulk drag into Closed instead of menus

Features

What SleekView Kanban gives you for LiveChat (livechatinc.com)

Drag rewrites LiveChat status

Every drag updates the LiveChat conversation status in storage. The agent app, any admin report, and the visitor side widget all see the new value through their normal reads. There is no separate publishing step and no temporary local state to clear after a move.

Group lanes

Filter the board by LiveChat group so Sales agents see only Sales chats and Support agents see only Support. Supervisors keep the unfiltered board to spot a Queued backlog hitting one group and rebalance by dragging chats across lanes during the shift.

Visible queue wait

Every Queued card shows minutes since the visitor connected. Agents pick the oldest queued chat first rather than the latest one to ring. Supervisors see the queue growing or shrinking live, and SLA risk stops hiding behind a quiet sidebar badge.

Audience

Where the LiveChat board sharpens a shift

Queue triage

Agents take LiveChat conversations during peak hours. The board makes Queued a visible column with wait times, so agents pick the oldest first instead of grabbing whichever chat last buzzed in their browser tab in the LiveChat agent app.

Group based coverage

Sales, Support, and Billing share a LiveChat account with groups. The board filters by group so each team only sees its own four columns, while a supervisor switches to the full view to balance load and rebalance across groups when needed.

Pending follow up

Chats waiting on a customer answer pile up in Pending rather than mixing with Chatting. Supervisors scan that column for stalled threads, drag dead ones to Closed, and leave warm ones for follow up, which keeps the working columns honest.

The bigger picture

Why a board fits LiveChat better than a tab list

The LiveChat agent app optimises for replying. It bubbles the most recent message and lets agents click between active chats quickly. That is exactly right when an agent is mid conversation.

It is exactly wrong when the agent is deciding what to do next. A kanban board fills that gap. Queued, Chatting, Pending, and Closed each become a column, and the team can read queue health off the column counts without leaving the screen for a report.

Drag and drop also collapses common state changes into one motion. Picking up a Queued chat by dragging it onto a lane is faster than clicking the chat, finding the take chat button, and confirming. Marking a chat Pending by dragging it across the board is faster than opening the chat menu and selecting Set as pending.

Multiplied across a busy shift, the saved clicks add up. The other underrated win is supervisor visibility. With a single screen showing every group's queue and every agent's lane, a supervisor can spot uneven load instantly and intervene by dragging chats themselves.

The native agent app makes that level of oversight clumsy. The kanban board makes it cheap.

Questions

Common questions about SleekView Kanban for LiveChat (livechatinc.com)

Yes. Every drag writes the new status to the LiveChat conversation record. The agent app, reports, and the underlying conversation history all reflect the new value as soon as they read the record. There is no separate sync step or temporary local state to flush.

 

SleekView reads the distinct values from the conversation status column. Standard LiveChat deployments expose Queued, Chatting, Pending, and Closed. Any additional statuses you define show up as their own columns automatically, and any column can be hidden from the working view.

 

Yes. The Kanban view filters on any column on the conversation record. Filter by group for a team view, by agent for a personal lane, or combine the two. Supervisors leave the filter off to see workspace wide load and rebalance by dragging cards across lanes.

 

Yes. The board refreshes on an interval, so wait time advances live for cards still sitting in Queued. The moment an agent picks up a chat, the wait time resets in line with the LiveChat status transition and the card moves out of the Queued column into Chatting.

 

The Closed column paginates, so only a small window loads at a time. Queued, Chatting, and Pending stay responsive even when Closed carries years of conversation history. You can also restrict Closed to today or this week so it always reflects current shift work.

 

Drags are optimistic and verified by the next refresh. If two agents move the same card within one refresh window, a soft conflict warning surfaces so the second agent can confirm or revert. The conversation never silently lands in the wrong status without notice.

 

Yes. Any text or enum column on the conversation record can be the kanban grouping. Teams often add Priority, Topic, or Lead Stage and group on that. Drag and drop writeback continues to work regardless of which column is driving the current board layout.

 

No. Automated rules and manual drags both write to the same status field, so whichever fires last wins. If a bot closes a chat that an agent has just dragged back to Chatting, the manual move takes effect and the bot will respect the new state on its next run.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView