SleekView groups by the status column on wp_fs_tickets because that matches the React inbox filter chips every agent already uses. You can also group by priority, by assigned_agent_id, by mailbox, or by any custom field from wp_fs_meta for tailored boards.

Yes. SleekView writes through Fluent Support's REST status endpoint so fluent_support/ticket_status_updated, the assigned-agent hook, and any workflow automations you configured for the mailbox fire exactly as they would from the React inbox itself.

Yes. Any field stored in wp_fs_meta can be added to the card front, including custom fields you configured per mailbox. Numeric values render as badges, dates as relative time, and dropdown values render as colored chips matching Fluent palette.

Yes. Filter the board by mailbox_id to show one inbox at a time, and SleekView honors the Fluent Support business-hours configuration for SLA badges so out-of-hours tickets render with the correct countdown adjusted for the mailbox's configured hours.

Yes. Boards are saved views, stored per user or shared per role. The billing agent loads a board grouped by status filtered to the billing mailbox, the escalation manager loads an Urgent-only board, the underlying fs_tickets table stays a single source.

Yes. Kanban, Table, and Charts are three render surfaces over the wp_fs_tickets dataset. Switch between them in one click in the SleekView header, and the existing React inbox continues to work for agents who prefer the per-ticket reply panel.

Yes. Filters compose on top of the kanban grouping, so a board can show only tickets for a specific product tag, only Urgent priority, or only tickets assigned to a specific agent. The filter applies across every column in the board view.

SleekView polls for new tickets at a configurable interval, defaulting to thirty seconds. New rows appear in the New column with a brief highlight, and the column counts update so the lead spots a growing backlog before manual refresh.