SleekView groups by the state field on wp_icwp_conversations because that matches the Open, Snoozed, and Closed values Intercom uses, plus the Pending bucket the plugin derives. You can also group by team_id or by assignee_id for swimlanes.

Yes. SleekView updates the local cache for instant feedback and queues a PUT through the plugin's Intercom API client. Intercom returns the confirmed state, the cache reconciles, and the change appears in Intercom Inbox and the mobile app.

Yes. Because the writeback uses the official Intercom REST API, bots, workflows, and custom apps configured on the Intercom side run exactly as they would when an agent changes state inside Intercom Inbox directly through the web interface.

Yes. Any custom data attribute the plugin syncs into wp_icwp_conversations can be added to the card front. Tags render as colored chips, numeric attributes render as badges, and dates show as relative time so cards stay compact across columns.

Yes. SleekView filters the board by the WordPress user's mapped Intercom team access, so an agent only sees conversations they are permitted to see in Intercom. Cross-team permission mappings are honored for leads who triage across teams.

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

Yes. Filter the board by tag to show only conversations tagged vip, only conversations tagged with a specific product, or any combination of tags, and save the filter as a named board. Each board keeps its columns, filters, and card layout.

SleekView listens for the plugin's sync events and refreshes the affected columns when a new conversation lands in the cache. New cards appear with a brief highlight, column counts update, and the lead spots a growing backlog quickly each time.