✨ 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 Crisp

SleekView Kanban authenticates with the Crisp API and groups every conversation by its state field, so you can drag a card from Pending to Unresolved or Resolved and the state writes back to Crisp through the official endpoint without leaving the WordPress admin.

♾️ Lifetime License available

SleekView Kanban board for Crisp

Crisp conversations as a board inside WordPress

Crisp organizes every conversation into one of four states, Pending, Unresolved, Resolved, or a custom segment, and surfaces them in its own inbox in the Crisp dashboard. The dashboard is excellent for handling live chats and emails, but reviewing the long tail of Unresolved conversations from last week happens through filters and scrolling, not a layout that shows the queue shape across operators.

SleekView Kanban authenticates with the Crisp API using your website identifier and pulls every conversation along with its current state, assigned operator, contact name, channel, and last message timestamp. It groups the records into columns by the state field, so Pending, Unresolved, and Resolved each get a swimlane, and any segment you use in Crisp can be added as an extra board filter.

Dragging a card between columns writes the new state through the Crisp conversation API. The change appears in the Crisp dashboard within a few seconds, the contact sees a consistent state if they return to the chat, and any webhook or Zapier zap listening for conversation events receives a payload. Conversations from chat, email, Messenger, Twitter DMs, and Slack channels all sit on the same board because Crisp normalizes them into a single state field.

Workflow

From Crisp conversations to a live board

1

Connect Crisp

Paste your Crisp website identifier and API tokens into SleekView. It authenticates with the Crisp API, lists the available state values and segments, and offers each one as a grouping axis before the kanban board renders any conversation cards on screen.
2

Pick the status column

Select conversation state as the kanban axis. SleekView reads the Crisp default values of Pending, Unresolved, and Resolved, plus any custom segments, and renders them as columns in whatever order matches your support team workflow for the day.
3

Choose what shows on cards

Pick the fields that matter on a card front: contact name, last message preview, assigned operator, channel icon for chat or email, and time since the last message. Long previews truncate and a card click opens the full thread inside Crisp.
4

Enable drag-and-drop

Toggle drag-and-drop on. Moving a card calls the Crisp API to update conversation state, so the change appears in the Crisp dashboard within seconds, and any webhook or Zapier zap listening for conversation events receives a normal payload as expected.

Sample board

Sample Crisp conversations board

A live Crisp board with four columns mapped to conversation state. Each card shows contact, channel, operator, and last message time, and dragging writes the new state back through the Crisp API.
Pending
9
Lisa asking about EU VAT invoice on Pro plan
Operator Mira, last msg 3m
Returning contact about webhook signature change
Operator Ravi, last msg 9m
Email reply from Acme about renewal date
Operator Sara, last msg 12m
Unresolved
17
Investigating webhook retries for failed Stripe events
Operator Mira, since 2d
Customer testing CSP fix on a staging environment
Operator Ravi, since 1d
Waiting on screenshot of failing OAuth screen
Operator Sara, since 4d
Follow up
6
Reminder to chase enterprise quote post-trial
Follow up 5d, Mira
Check in on NPS detractor from last week
Follow up 3d, Sara
Resend onboarding doc to delayed signup
Follow up 7d, Ravi
Resolved
112
Walked contact through SSO setup flow
Resolved by Mira, 1h ago
Confirmed refund processed on annual plan
Resolved by Ravi, 5h ago
Shipped translation fix in 2.4.1 release
Resolved by Sara, 1d ago

Comparison

Crisp inbox vs SleekView Kanban

Default Crisp inbox view

  • The Crisp inbox shows conversation state as a filter, not as the layout of the screen itself
  • Working through Unresolved means scrolling a list rather than seeing the column at a glance
  • Reassigning a long Unresolved conversation requires opening it and using a dedicated picker
  • Channels like chat, email, and Messenger share an inbox but the queue shape is hard to read
  • There is no native WordPress dashboard for Pending, Unresolved, and Resolved counts together

SleekView Kanban

  • Pulls conversations through the Crisp API and groups by the state field
  • Drag a card and the new state writes back through the official Crisp conversation endpoint
  • Card front shows contact, channel icon, operator, last message preview, and reply time
  • Filter by operator, channel, or segment without losing the column layout or count badges
  • Chat, email, Messenger, Twitter DMs, and Slack conversations all sit on the same board

Features

What SleekView Kanban gives you for Crisp

State as the layout

Every Crisp conversation lands in a column matching its state field. Pending conversations form the active queue, Unresolved is where deeper work sits, Follow up is parked work with intent, and Resolved is the closed pile that anchors the right side of the board for context.

Drag to update conversation state

Dragging a card from Pending to Unresolved calls the Crisp conversation API to set the new state. The change appears in the Crisp dashboard within seconds, the contact sees a consistent state, and any webhook or Zapier zap listening for state changes receives a normal payload.

Filter by operator or segment

Pick a single operator and the board shrinks to their conversations, or filter by Crisp segment to focus on a specific customer cohort. Filters apply across columns and the count badges update so the team can still see the shape of the queue after multiple filters.

Audience

Support teams running Crisp at scale

Morning triage

Open the kanban first thing, scan Pending to see what came in overnight, drag the high-priority conversations to specific operators, and review the Unresolved column for items that still need work after a few days in the queue.

Unresolved cleanup

Filter to Unresolved and sort by age, then either resolve, follow up, or reassign the items that have been sitting too long. The board makes long-lived Unresolved cards painfully visible so they get the attention they need from the team.

Cross-channel review

Walk through the board by channel filter during a weekly review to spot whether one channel is generating disproportionate Pending volume or Unresolved tail. Adjust staffing, canned responses, or chatbot triggers based on what the kanban reveals.

The bigger picture

Why the Crisp kanban view matters

Crisp is one of the most multichannel inboxes on the market, blending chat, email, Messenger, Twitter DMs, and Slack into a single conversation list. That breadth is a strength for operators answering messages, but it makes queue shape harder to see at a glance because every channel folds into the same inbox stream. A kanban view turns the conversation state into a visible layout.

Pending is the active intake, Unresolved is the work that is dragging on, Follow up is the parked work with intent, and Resolved is the closed pile. The relative size of those columns is a leading indicator of team health, and it is much harder to ignore a growing Unresolved column when it is a colored block on the screen than a counter behind a filter. Drag and drop matters because state changes are how Crisp tracks resolution and follow-up, and turning that change into a one-motion drag instead of opening each conversation makes the work feel correctly sized.

SleekView keeps the Crisp API in the loop so webhook automations, segments, and audit logs all keep working.

Questions

Common questions about SleekView Kanban for Crisp

It works with the free Crisp plan because the conversation API SleekView uses is available without a paid tier. Paid Crisp plans unlock extra fields like segments and integrations, which SleekView shows on cards automatically when present in the conversation payload returned by the Crisp API.

 

Yes. The board defaults to conversation state because that is the most common axis, but you can switch to operator to swimlane by team member, or to channel to see chat, email, Messenger, and Slack split out. Switching axes only affects the view, not the underlying state field.

 

SleekView calls the Crisp conversation update endpoint to set the new state. The change appears in the Crisp dashboard within a few seconds, the contact sees a consistent state if they return to the chat, and any webhook or Zapier zap listening for conversation events fires.

 

Yes. SleekView calls the Crisp API with the API tokens tied to your operator account, so visibility and edit permissions match your Crisp role. Conversations that are restricted to specific operators stay restricted, and write access on the kanban matches what the operator has in Crisp.

 

Each card carries a small channel icon so you can tell at a glance whether the conversation came from website chat, email, Messenger, Twitter DMs, or a Slack channel. State grouping is consistent across channels because Crisp normalizes Pending, Unresolved, and Resolved into one state field.

 

Yes. Filters sit above the board and apply to every column at once. Pick an operator and the board shrinks to their conversations, layered with channel and segment filters, and the count badge on each column updates so you can still see the queue shape after filtering.

 

SleekView polls the Crisp API on a short interval and updates the board without a full page reload, so when another operator moves a conversation from Pending to Resolved you see it slide across within a few seconds. You can also force a refresh for an instant snapshot.

 

It is a separate SleekView page inside WordPress that you can pin to the admin menu or embed on the frontend with a shortcode for team displays. The Crisp dashboard remains the place to answer messages live, and the kanban gives you a queue view that lives alongside it.

 

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