SleekView for Kustomer: chat embed config and visibility as tables
The Kustomer chat plugin embeds the widget using a brand ID stored in wp_options with optional per-page visibility metadata. SleekView turns that scattered configuration into a single editable audit table.
♾️ Lifetime License available
Kustomer configuration as a working list
The Kustomer Chat plugin for WordPress embeds the Kustomer Chat widget using a brand ID stored in wp_options under kustomer_settings (with the brand identifier as the key sub-key). Optional visibility configuration covers page-template show/hide rules, and per-post toggles can be saved as wp_postmeta. Conversations and customer profiles all live in Kustomer's SaaS platform.
The default settings screen exposes connection state but doesn't list the visibility rules, brand-ID history, or per-page overrides as a queryable surface. SleekView reads the option group and any per-post overrides, then presents them as a sortable, filterable table. Saved views surface pages where the widget is hidden, sub-keys that have drifted from the brand defaults, and the current brand ID for staging-versus-production checks.
Inline edits route through update_option() and update_post_meta(). WordPress hooks fire normally, so any audit log captures the change and any cache layer that listens for option updates invalidates as expected.
Workflow
From a brand-ID option to a working configuration
Read options and postmeta
kustomer_settings plus per-post kustomer_disable postmeta as a single visibility source.
Compose columns
Save audit views
Edit inline
Sample columns
A typical Kustomer configuration view
wp_options (kustomer_settings, kustomer_brand_id) + wp_postmeta (kustomer_disable per post)
| Scope | Target | Setting | Value | Status | Updated |
|---|---|---|---|---|---|
| Global | kustomer_brand_id | Brand ID | brand_a1b2c3d4 | Connected | Apr 23 |
| Page | /contact | kustomer_disable | false | Visible | Apr 18 |
| Page | /legal/terms | kustomer_disable | true | Hidden | Apr 06 |
| Global | kustomer_settings | locale | en-US | Override | Mar 28 |
Comparison
Default Kustomer admin vs SleekView
Default Kustomer admin
- Settings screen shows current brand ID but no per-page audit
-
Per-post
kustomer_disablepostmeta isn't surfaced anywhere -
Serialized sub-keys in
kustomer_settingshide locale and behavior drift - No saved view of pages where the widget is intentionally hidden
- No drift detection between staging and production brand IDs
SleekView
-
Surface
kustomer_disablepostmeta as a sortable column -
Expand
kustomer_settingsinto rows for locale, behavior, consent - Inline-toggle per-post visibility from one table
- Save audit views per scope (page, template, post type)
- Diff brand ID and config between environments
Features
What SleekView gives you for Kustomer
Visibility audit
Every published page filterable by Kustomer visibility postmeta, so the team can confirm coverage on high-intent pages and spot legacy hide rules in one saved view.
Inline visibility edits
Toggle widget visibility from the table. Writes go through update_post_meta() so any cache or sitemap plugin reacts as if the change came from the post edit screen.
Brand-ID check
Filter by environment and compare the brand ID alongside the locale and behavior sub-keys, catching the moment a staging brand ID slips into a production deployment.
Audience
Who uses SleekView for Kustomer
Marketing operations
Audit which pages hide Kustomer before a launch. Inline-enable the widget on campaign URLs without opening posts one at a time.
Support leads
Confirm at a glance that the production brand ID matches the documented Kustomer brand, and that locale and consent sub-keys haven't drifted from the configured defaults.
Site administrators
Diff Kustomer configuration between staging and production with a CSV export. Catch brand-ID and locale mistakes before either reaches customers.
The bigger picture
Why an enterprise chat embed needs a real audit table
Kustomer is at the enterprise end of the customer-service market, and the customers running it on WordPress tend to be teams who care a lot about brand consistency, locale handling, and consent compliance. The WordPress plugin itself is intentionally light: a brand-ID option, a settings panel, a few sub-keys for behavior and locale, and optional per-post toggles. That minimalism makes the embed fast and reliable.
It also leaves a real operational gap, because the team running the deployment cares about audit, drift, and coverage in a way the settings panel was never designed to answer. SleekView fills that gap by treating the configuration as a real table. Each rule becomes a row, each environment becomes an exportable snapshot, each edit fires the same WordPress hooks the settings screen would.
Conversations stay in Kustomer's SaaS platform. The WordPress configuration that drives where, when, and how the widget appears finally gets the audit surface an enterprise team expects.
Questions
Common questions about SleekView for Kustomer
No. Conversations, customer profiles, and case history live in Kustomer's SaaS platform. SleekView only reads what the WordPress plugin stores, which is the brand-ID option and per-post toggles.
When the Kustomer plugin disables the widget on a single post, it stores a kustomer_disable postmeta value. SleekView lists those posts as rows in the visibility view alongside global rules.
Yes. Writes go through update_option() and update_post_meta(), firing standard WordPress hooks. Any plugin that listens for those changes (audit logs, cache invalidation, sync tools) reacts normally.
Kustomer's WordPress plugin stores consent integration toggles inside the option group. Those sub-keys surface as rows, so a privacy officer can audit them in one saved view.
Operator availability and routing run inside Kustomer's app. The WordPress plugin doesn't store that state locally, so SleekView focuses on the configuration that WP actually owns.
It lives in wp_options, so any user with manage_options can read it from WP. View scoping in SleekView can hide that row from roles that shouldn't see it.
Yes. Any saved view exports to CSV. That's the practical way to capture configuration before a launch and compare it against the post-launch state for drift.
Yes. Each subsite has its own Kustomer option group and postmeta. SleekView reads the current site, and a network admin can switch sites to audit each one independently.
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 checkoutBrowse more
- Woocommerce Conditional Shipping And Payments
- Lemonsqueezy Wp
- Woocommerce Quickbooks
- Restropress
- Cart66 Cloud
- Wp Ecommerce
- Woocommerce Low Stock Alerts
- Gooten Print On Demand
- Woocommerce Product Search
- Woocommerce Shipping Class Rates
- Woocommerce Gift Cards Pro
- Woocommerce Wholesale Order Form
- Woocommerce Canpar Shipping
- Smart Coupons
- Square For Woocommerce