Yes. Fluent Support's own tables (fct_tickets, fct_ticket_responses, fct_customers, fct_agents) are the source. SleekView joins them so customer name, agent name, and product show inline as resolved values rather than raw IDs, and sort and filter operations hit indexed columns directly for speed even on inboxes with tens of thousands of tickets.

Yes. Inline writes route through Fluent Support's ticket-update functions, which means status-change hooks fire, automations run, agent assignment notifications send, and the activity log entry appears exactly as it would after a single-ticket update from the inbox. Bulk operations iterate through the same path so side effects are identical to manual edits.

Yes. Custom fields registered through Fluent Support settings are stored on the ticket row as JSON. SleekView extracts individual keys as their own columns, sortable and filterable. The agent UI lists the keys actually present on tickets in your installation, so you pick from a real list instead of guessing field names.

Yes. Pick the status column as the kanban grouping field and the same source renders as a board with one column per status value (open, in-progress, on-hold, closed, depending on your configuration). Drag a card across columns to update status inline through Fluent Support's own write path.

Yes. Fluent Support assigns agents to specific products or business inboxes; SleekView honours that scoping at the row level so an agent only sees tickets they are permitted to see, even when sharing a saved view with a support lead who has wider access. Capability checks gate inline edits the same way.

Responses live in fct_ticket_responses and can be a separate view for moderation, or surfaced as a last-response summary column on the tickets table so an agent sees the latest customer message without opening the ticket. Both views can coexist, which is useful when a lead reviews thread quality alongside the queue itself.

Yes. fct_tickets stores created and last-response timestamps, so a computed column like hours since last customer reply is straightforward, as is a filter for tickets older than 24 hours awaiting reply. A view of breached tickets sorted by hours overdue gives a support lead an instant escalation list.

Yes. If FluentCRM is active, SleekView can join the contact record from the CRM tables onto the ticket row, so columns like lifetime value, tag list, or last-campaign-opened sit alongside ticket status. Useful for prioritising VIP customers in the same kanban view as the regular queue without juggling two screens.