SleekView Kanban for WSDesk Pro
SleekView reads the wsdesk_ticket post type and joins the wsdesk_status taxonomy, agent assignment, and priority fields, then renders one card per ticket grouped by status so agents move Open, Awaiting reply, On hold, and Solved cards.
♾️ Lifetime License available
WSDesk's list does not show the queue
WSDesk stores every ticket as a wsdesk_ticket post and tracks workflow state through the wsdesk_status taxonomy (Open, Awaiting reply, On hold, Solved by default). Priority sits in the wsdesk_priority taxonomy, agent assignment in postmeta under _wsdesk_agent, channel and source land in custom fields. The default Tickets screen is a sortable list with a status dropdown.
SleekView reads wsdesk_ticket posts and joins the status and priority taxonomies plus the assigned agent meta. The natural grouping field is wsdesk_status, the same buckets agents already use to triage. Card fronts surface subject, requester email, priority tag, assigned agent name, and last reply date so the lead reads the queue without opening any ticket.
Dragging a card from Open to Awaiting reply writes the wsdesk_status term through WSDesk's CRUD layer and triggers wsdesk_after_status_change, the agent-assignment hook, and the SLA timer reset. Closing tickets after a resolution becomes a drag from Awaiting reply to Solved, and the same hooks fire as if the agent had used the ticket edit screen, so reports stay accurate.
Workflow
From WSDesk list to live board
Connect WSDesk tickets
Pick wsdesk_status to group by
Choose what shows on each card
Enable drag-and-drop status changes
Sample board
Sample WSDesk tickets board layout
Comparison
Default WSDesk vs SleekView Kanban
Default WSDesk list
- Tickets list mixes Open and Solved, status dropdown forces reload to switch
- No drag-and-drop, every status change needs the ticket edit screen to open
- Priority and agent live in extra table columns the lead has to scan row by row
- SLA countdown hides behind tooltip icons and never surfaces on the main list
- Cannot see backlog shape per priority or per agent without a custom report
SleekView Kanban
-
Group by
wsdesk_status,wsdesk_priority, or assignee -
Drag writes through the CRUD layer and fires
wsdesk_after_status_change - Card fronts show subject, requester, priority tag, agent, and SLA badge
- Save per-shift boards: triage, escalations, per-channel, per-agent swimlane
- Same wsdesk_ticket dataset renders as Table or Charts in one single click
Features
What SleekView Kanban gives you for WSDesk Pro
Drag tickets between statuses
Move a card from Open to Awaiting reply and SleekView writes wsdesk_status through WSDesk's CRUD layer. wsdesk_after_status_change fires, the SLA timer resets, and the change lands in the ticket history with the moving agent recorded automatically.
SLA badges on every card
Card fronts show the SLA countdown as a colored badge so the lead spots tickets about to breach without opening each one. Sort the Open column by SLA remaining and the most urgent cards float to the top automatically each refresh.
Per-agent swimlanes
Switch the grouping field from wsdesk_status to assigned agent to see one column per agent. Drag a card from Sara's overloaded column to David's quieter column and SleekView writes the assignment meta through the WSDesk CRUD layer.
Audience
Who uses SleekView Kanban for WSDesk
Inbound support agents
Pull from Open, drag to Awaiting reply after sending the response, drop into Solved on customer confirmation. Priority and channel show on the card front so the next pick matches the SLA window automatically.
Support leads on triage
Group by priority for the morning standup, reassign by dragging cards between agent columns at midday, and end the shift on the status view to confirm the team cleared Open before the cutoff.
Ops on weekly review
Flip to Charts view for solved-per-day, average time in Awaiting reply, and per-agent throughput. Kanban handles the live shift, charts handle the retro, both read the same dataset.
The bigger picture
Why WSDesk teams outgrow the list view
WSDesk's default Tickets screen treats every ticket the same: a flat list sorted by date, with a status filter at the top of the page. That works for a single-agent operation answering a few tickets a day. It stops working the moment a team needs to coordinate.
The lead wants to see how many tickets sit in Open versus Awaiting reply, who is overloaded, and which High-priority cards are about to breach the SLA. The list view hides all of that behind dropdowns and pagers. A kanban grouped by wsdesk_status surfaces the queue shape on a single screen.
Counts on each column header tell the lead whether to throw more agents at Open or to chase customer replies in Awaiting reply. Priority badges on every card flag urgent work without sorting. Per-agent swimlanes show overload before it turns into missed responses.
And because drag writes through the WSDesk CRUD layer, the SLA timers, status hooks, and assignment integrations the team already depends on keep firing exactly as before.
Questions
Common questions about SleekView Kanban for WSDesk Pro
SleekView groups by the wsdesk_status taxonomy because that is the field every WSDesk agent already triages around. You can also group by wsdesk_priority for triage shifts, or by the _wsdesk_agent meta for per-agent swimlanes during peak hours.
Yes. SleekView writes through WSDesk's CRUD layer so wsdesk_after_status_change, the SLA timer logic, and the email-template engine fire as if the agent had used the ticket edit screen, including any custom automations you registered against the same hook.
Yes. Any field on the wsdesk_ticket post including postmeta, taxonomy terms, and computed SLA values can be added to the card front. Numeric values render as badges, dates as relative time, and long strings truncate to keep cards scannable.
Yes. SleekView reads the WSDesk SLA timer and renders it as a colored badge on every card. Sort within a column by SLA remaining and the most urgent tickets surface at the top, so the lead spots imminent breaches before they happen for real.
Yes. Boards are saved views stored per user or shared per role. The billing agent loads a board filtered to the billing channel, the escalation manager loads an Urgent-only board, and the underlying wsdesk_ticket dataset stays a single source of truth.
Yes. Kanban, Table, and Charts are three render surfaces over the wsdesk_ticket dataset. Switching between them is one click in the SleekView header, and the existing WSDesk Tickets list continues to work for users who prefer the dense table layout.
Yes. Filters compose on top of the kanban grouping, so a board can show only tickets in the billing channel, only High and Urgent priority, or only tickets assigned to a specific agent. The filter applies to every column visible in the board.
SleekView polls for new tickets at a configurable interval, defaulting to thirty seconds. New rows appear in the Open column with a brief highlight, and the column counts update so the lead notices a growing backlog before the next manual refresh.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout