SleekView groups by the status field on wp_zdwp_tickets because that matches the New, Open, Pending, Hold, Solved, and Closed values Zendesk uses. You can also group by group_id for team boards or by assignee_id for per-agent swimlanes.

Yes. SleekView updates the local cache for instant feedback and queues a PUT through the plugin's Zendesk API client. The Zendesk side returns the confirmed status, the cache reconciles, and the change appears in Zendesk Support and the mobile app.

Yes. Because the writeback uses the Zendesk REST API, any triggers, automations, and SLA policies you have configured on the Zendesk side run exactly as they would if the agent had changed the status inside Zendesk Support directly without the kanban.

Yes. Any custom field the Zendesk plugin syncs into wp_zdwp_tickets can be added to the card front. Tags render as colored chips, numeric fields render as badges, and date fields show as relative time so cards stay scannable across columns.

Yes. SleekView filters the board by the WordPress user's mapped Zendesk group and brand, so an agent only sees tickets they are permitted to see in Zendesk itself. Multi-group permission mappings are honored for cross-team triage views.

Yes. The plugin's list admin and dashboard widget still work, and the kanban adds a queue management view that neither offered. All three read from the same wp_zdwp_tickets cache so numbers stay consistent across the WordPress admin surfaces.

Yes. Filter the board by ticket_form_id to show only Billing tickets, only Technical tickets, or only Sales tickets, and save the filter as a named board. Each board keeps its columns, filters, and card layout for the team running that form.

SleekView listens for the plugin's sync events and refreshes the affected columns when a new ticket lands in the cache. New cards appear with a brief highlight, column counts update, and the lead notices a growing backlog before the next refresh.