The Intercom WordPress plugin's main job is to inject the Messenger snippet, pass user identify calls to Intercom, and apply page-level rules for when the widget shows. Settings, secret keys, and identify rules live in wp_options under the intercom_settings key. Intercom itself owns the conversation history and reporting at intercom.com, and the WP admin offers a connect screen rather than a chart layer.

SleekView Charts reads what the WordPress side actually keeps locally, plus any data a webhook lands in WP. Production setups usually wire the Intercom conversation-closed webhook into an intercom_conversation custom post type with operator, page URL, segment, response time, and outcome saved as postmeta. SleekView picks up that CPT and renders chart cards: conversations per operator, breakdown by segment, daily volume from post_date, and average response time as a number KPI.

The same dashboard layers in WordPress user data. Because Intercom identifies WP users with their user_id and user_hash, the intercom_conversation post can store the WP user ID as postmeta. SleekView joins that to wp_users for a bar of conversations per WP role, and to wp_usermeta for plan or subscription-segment breakdowns. The result is a single Intercom dashboard that knows about the WP user table without an export step.

Intercom owns conversations, but WordPress owns the users, the subscriptions, the page rules, and the post type the rest of the site runs on. Asking which paid plan drove the most support tickets last week, which page triggered the most identify events, or which WP role generated the longest response times needs both sides in one chart. The default Intercom dashboard knows none of that WP context, and pivoting between two tools every time a question lands slows decisions.

SleekView Charts puts the WP side of Intercom in WordPress where the user table, the postmeta, and the page metadata already live. The intercom_conversation CPT and intercom_settings option become first-class chart sources alongside any other dataset on the site. Operator load, segment mix, response times, and per-role volume all sit in the same admin as the WP users that drove them.

Reporting and triage share one source of truth, so a number on the dashboard always agrees with a count on the conversation list.