SleekView groups by the status integer on wp_fdwp_tickets because that matches the Open, Pending, Resolved, and Closed values Freshdesk uses everywhere. You can also group by group_id for team boards or by responder_id for per-agent swimlanes.

Yes. SleekView updates the local cache for instant feedback and queues a PUT through the plugin's Freshdesk API client. The Freshdesk side returns the confirmed status, the cache reconciles, and the change appears across every Freshdesk surface.

SleekView's writeback queue handles retries and respects the Freshdesk rate limits. A failed write retries with backoff, the card shows a brief pending state, and an admin notice surfaces if a write fails after the configured retry budget runs out.

Yes. Any custom field the Freshdesk plugin syncs into wp_fdwp_tickets can be added to the card front. Numeric values render as badges, date fields show as relative time, and dropdown values render as colored chips matching Freshdesk's UI.

Yes. SleekView filters the board by the WordPress user's mapped Freshdesk group, so an agent only sees tickets they are permitted to see in Freshdesk itself. Cross-team boards are available to roles with multi-group permission mappings set up.

Yes. The iframe still works for deep ticket replies, the dashboard widget still shows counts, and the kanban adds a queue management view that neither offered. All three read from the same cache table so numbers stay consistent across surfaces.

Yes. Filter the board by source to show only chat tickets, only email tickets, or only social tickets, and save the filter as a named board. Each board keeps its columns, filters, and card layout for the team that runs that source channel.

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 spots a growing backlog before the next manual reload.