Front Chat is the embeddable chat surface attached to the Front shared inbox. The WordPress side of it is a small embed plugin that injects the chat snippet and stores the chat ID, teammate routing rules, and page-targeting settings in wp_options under front_chat_settings. Front itself owns conversations on app.frontapp.com, and the WP admin offers a settings screen rather than a chart layer.

SleekView Charts reads what the WordPress side actually keeps locally plus anything Front webhooks land in WP. Most production setups configure the Front conversation-closed webhook to POST into a front_conversation custom post type with teammate, inbox, channel, tags, and response time saved as postmeta. SleekView picks up that CPT and renders chart cards: conversations per teammate, inbox mix as a donut, daily volume from post_date, and average response time as a number KPI.

The dashboard layers in tag analysis too. Front conversations are heavy on tags (billing, urgent, churn-risk, feature-request) which the webhook stores as a serialized array under front_tags. SleekView normalizes that into a bar of conversations per tag so the team sees which themes dominate the queue this week versus last. The same admin that holds the chat embed now also holds the reporting layer, with WordPress capabilities applying identically to both.

Front owns conversations across email, chat, and SMS, but every WordPress signal that drives those conversations (which pages get the embed, which WP users are paying customers, which posts the visitor was on when they opened the widget) lives in WordPress. Asking which paid plan generated the most chats last week or which content drove the most billing inquiries needs both sides in one chart. The default Front analytics screen knows none of that WP context, and pivoting between two systems every time a question lands slows the answer.

SleekView Charts puts the WP side of Front in WordPress where the user table, the postmeta, and the page metadata already live. The front_conversation CPT and front_chat_settings option become first-class chart sources alongside any other dataset on the site. Teammate load, inbox mix, response times, and per-tag volume all sit in the same admin as the WP users and pages that drove them.