SleekView for Intercom Fin AI
SleekView reads the Intercom plugin's wp_options, per-role identity settings, postmeta overrides and any local webhook log. Embed status, identity-verification state, captures and events line up as columns you can sort and filter.
♾️ Lifetime License available
Fin AI lives in Intercom. The integration surface lives in rows.
The Intercom plugin admin shows the app ID, the secret and a few visibility toggles. It does not resolve those toggles into the actual list of URLs the Messenger loads on, it does not sit next to identity-verification config per role, and it does not show the form submissions that route into the Inbox. Three separate screens, no shared view.
SleekView reads the WordPress-side data as one dataset. The plugin settings come from wp_options. Per-page overrides come from postmeta. Identity-verification HMAC config sits in options keyed by user role. Captured-lead submissions live in the form plugin's submissions table. Webhook event records, when the site logs them, sit in a custom table.
Intercom's own reporting still owns conversation analytics, Fin resolution rate and team performance. SleekView covers the half Intercom cannot see: per-URL embed status, identity verification coverage across roles, capture flow into the Inbox and webhook event delivery into WordPress.
Workflow
Turn the Intercom plugin's footprint into a table
Pick the source rows
Compose your column set
Save and scope the view
Edit inline and export
Sample columns
A typical Intercom Fin embed and capture view
wp_options (intercom_*) + form plugin submissions + webhook log table
| Source URL | Messenger | Identity | Captured email | Last webhook | Received |
|---|---|---|---|---|---|
| /pricing/ | Loaded | Verified | ana@northwind.io | conversation.user.created | Apr 24 14:02 |
| /account/ | Loaded | Verified | tom@studio.dev | conversation.user.replied | Apr 24 11:47 |
| /contact/ | Loaded | Anonymous | ria@design.co | contact.lead.created | Apr 24 09:21 |
| /checkout/ | Excluded | — | — | — | — |
| /members/ | Suppressed | Unverified | — | webhook.failed | Apr 23 17:08 |
Comparison
Default Intercom plugin admin vs SleekView
Default Intercom plugin admin
- Settings page lists toggles, never resolves them into a per-URL row
- No view of which post types currently load the Messenger script
- Identity-verification coverage across user roles stays scattered
- Lead-capture form submissions live in a separate form plugin screen
- Local webhook event records have no list or filter view
SleekView
- Per-URL rows resolved from Intercom's visibility rules
- Inline Messenger status (Loaded, Excluded, Suppressed) per row
- Identity-verification state column joined per user role
- Joined columns for the latest capture and webhook event per page
- Save filtered views per role (support, RevOps, integration owner)
Features
What SleekView gives you for Intercom Fin AI
Custom column sets per view
Build a support view with URL, embed status and identity verification. Build an integration view with webhook event, status code and received_at. Each role gets the columns it actually uses.
Inline edits on overrides
Flip a per-post embed override, mark an identity-verification gap as accepted risk or update a capture-submission note without bouncing through three admin screens.
Compose precise filters
Combine embed status, user role, form_id, webhook event_type and identity-verification state. Save the filter as a named view your team reuses every week.
Audience
Who uses SleekView for Intercom Fin AI
Support leads
Confirm the Messenger loads on every product and pricing page, and that identity verification is configured for the roles that actually log in to the site.
RevOps
Filter to capture rows by form_id to see which WordPress entry points still feed Intercom and which forms quietly stopped firing after a migration or theme update.
Integration owners
Filter on webhook.failed events to catch a broken endpoint days before the Inbox shows a quiet automation queue and customer messages slip through.
The bigger picture
Why Fin AI's WordPress half needs a real table
Intercom's reporting on conversation volume, Fin resolution rate and team workload is excellent, and SleekView has no useful role there. The WordPress half of the integration is where visibility stops. Embed coverage is a settings toggle nobody resolves into a list.
Identity verification across roles is a checklist nobody audits. Captured-lead submissions live in whichever form plugin a particular funnel page uses. Webhook event records, when they exist, sit in a custom table.
SleekView reads all of that as a single dataset and renders it as one row per URL, submission or event. Support sees embed and identity coverage. RevOps sees capture flow.
Integration owners see webhook delivery. The Intercom UI stays in charge of what Fin does, SleekView covers what WordPress holds.
Questions
Common questions about SleekView for Intercom Fin AI
No. Conversation analytics, Fin AI resolution metrics and team performance reports stay inside Intercom, which is the right tool for those views. SleekView only renders the WordPress-side surface: per-URL Messenger status, identity-verification state, captured leads and any local webhook event records.
WordPress-native rows: the Intercom plugin's wp_options entries, any postmeta used for per-page overrides, the form plugin's submissions table for captures routed to Intercom and a webhook log table if the site writes one. No Intercom API call is required for these views.
The Intercom plugin's identity-verification config maps WordPress roles to a verified or unverified state. SleekView resolves that mapping per row so you see Verified, Anonymous or Unverified next to the URL the user is on, instead of cross-referencing two settings screens.
Yes. Each form plugin stores submissions in its own table. Add each table as a dataset and the view normalises form_id, submitted_email and submitted_at into shared columns spanning Gravity Forms, WPForms, Forminator, Fluent Forms and database-extended Contact Form 7 setups.
Yes. SleekView writes through the plugin's CRUD layer where one exists, so any filters the Intercom plugin or a companion CRM registers on option updates or postmeta saves still fire. Bulk operations iterate the same path so side effects match a manual edit.
Queries hit standard WordPress indexes on options, postmeta and the form submissions tables. Filters and sorts use indexed columns where possible, and expensive resolutions like per-URL embed flags are cached per page-load, so default views stay quick even on installs with high traffic.
Yes. Every SleekView view is gated by WordPress capability, so a support-facing Intercom audit can be limited to support and RevOps roles while developers see a separate, technical view with raw webhook events and override meta.
Yes. The plugin that embeds the Intercom Messenger stores its app ID, secret and identity-verification settings as standard WordPress options. SleekView reads those options, plus any related form submission and webhook log rows, without needing a paid Intercom tier.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout