SleekView for LiveChat: chat license and embed config as tables
The official LiveChat WordPress plugin stores the license number, group routing, and visibility settings in wp_options. SleekView turns those into a working audit table with inline edits and saved views.
♾️ Lifetime License available
LiveChat configuration as an audit table
The official LiveChat WordPress plugin (from livechatinc.com) embeds the chat widget using a license number stored in wp_options under livechat-license-number. Additional sub-keys cover group routing, visibility toggles, and the WooCommerce integration where applicable. The actual conversations, contacts, and tickets all live in LiveChat's SaaS application.
The default plugin admin gives a connect-disconnect button and a small settings panel. It doesn't expose group routing, visibility overrides, or cached integration state as a list. SleekView reads the option group, unserializes sub-keys, and adds any per-post or per-page toggles stored in postmeta, so the team can audit the embed configuration as a real table.
Inline edits route through update_option() and update_post_meta(). That means standard WordPress hooks fire, audit logs capture changes, and the LiveChat plugin's own listeners see the change exactly as they would after a settings-screen save.
Workflow
From a settings panel to a real configuration table
Read the option group
Compose columns
Save group views
Edit inline
Sample columns
A typical LiveChat configuration view
wp_options (livechat-license-number, livechat_options) + wp_postmeta (per-post toggles)
| Group | Key | Value | Status | Updated by | Updated |
|---|---|---|---|---|---|
| License | livechat-license-number | 12345678 | Connected | alex@studio.co | Apr 22 |
| Routing | default_group | Sales | Active | ria@design.io | Apr 16 |
| Visibility | hide_on_checkout | true | Hidden | tom@hello.dev | Apr 04 |
| WooCommerce | track_orders | false | Disabled | mia@brew.coop | Mar 30 |
Comparison
Default LiveChat admin vs SleekView
Default LiveChat admin
- Settings panel shows current values but no rule list
- Group routing sub-keys aren't surfaced as a sortable list
-
Per-post visibility overrides in
wp_postmetaaren't audited anywhere - WooCommerce integration toggles hide inside a serialized option
- No drift detection between staging and production environments
SleekView
-
Expand serialized
livechat_optionsinto one row per sub-key - Audit group routing and visibility rules from a saved view
-
Inline-edit values and write through
update_option() - Surface per-post overrides as a filterable column
- Diff license number and config between environments
Features
What SleekView gives you for LiveChat
License and routing audit
Confirm at a glance which license number is active and which default group receives new chats. Filter by environment to catch the moment a staging license accidentally hits production.
Inline routing edits
Change the default group or a visibility flag from the table. Writes route through update_option() so the LiveChat plugin's own listeners fire and the widget reflects the change on next load.
Visibility coverage
Filter every published page by visibility override to see which URLs hide the widget. Spot the legacy rule that's still hiding LiveChat on a page that should now show it.
Audience
Who uses SleekView for LiveChat
Marketing operations
Audit visibility coverage before a campaign launch. Inline-enable or disable the widget on specific URLs without opening each post one at a time.
Support leads
Confirm that the right default group receives new chats and that the WooCommerce integration sub-keys are wired up the way the team expects.
Site administrators
Diff LiveChat configuration between staging and production by exporting two saved views. Catch license-number mistakes and group routing drift early.
The bigger picture
Why a SaaS chat embed deserves an operational table
LiveChat is one of the longest-running independent live chat products on the market, with a mature WordPress plugin that does exactly what an embed plugin should: small footprint, stable behavior, fast to install. The cost of that minimalism is operational opacity. Once a site has been through a few content cycles, a few developer handovers, and at least one migration, the configuration spreads across an option group, a handful of postmeta entries, and a settings panel that wasn't built for ongoing audit.
Editors disable the widget on a one-off page and forget. A developer copies the database to staging and the live license keeps embedding. Marketing changes a default group during a campaign and the next quarter nobody remembers why.
SleekView gives that small but operationally critical configuration a real table. Each license, each routing rule, each visibility override becomes a row that can be filtered, sorted, exported, and inline-edited. Conversations stay in LiveChat's app.
The WordPress side gains the audit surface it was missing.
Questions
Common questions about SleekView for LiveChat
No. Chats, tickets, and contacts all live in LiveChat's SaaS app. SleekView only reads what the WordPress plugin stores locally, which is the license number, the configuration option group, and any per-post toggles.
If the plugin stores group routing or default-group selection inside livechat_options, SleekView unserializes and lists those sub-keys as rows. The routing logic itself runs in LiveChat's SaaS once a chat opens.
Yes. Writes route through update_option() and update_post_meta(), firing the standard WordPress hooks. The LiveChat plugin and any audit log react exactly as if the change came from the settings screen.
Yes. The license number row is inline-editable. Pair SleekView with an audit log to track rotations, and pair it with a staging-aware deployment to ensure the right number lands in the right environment.
If LiveChat's WooCommerce integration is active, its toggles live in the option group as sub-keys. Filter by group equals WooCommerce to audit them, and inline-edit to flip the integration on or off.
No. SleekView runs in wp-admin and reads options on demand. The frontend LiveChat script loads identically to a stock install, with no extra HTTP requests added by SleekView.
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 any unexpected drift.
Yes. Each subsite has its own LiveChat license number and option group. SleekView reads the current site; network admins 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 Deposits
- Woocommerce Payments Stripe
- Woocommerce Shipping Usps
- Funnelkit Funnel Builder
- Woocommerce Wholesale Gateway
- Edd Amazon S3
- Edd Conditional Emails
- Edd Commissions
- Magento Bridge
- Edd Recommendations
- Ecwid
- Shipperhq Woocommerce
- Woocommerce Deutsche Post
- Cartflows
- Atum Inventory Management
- Memberium
- Memberpress Affiliate Royale
- Memberpress Importer
- Private Content Restricted Content
- Memberpress
- Membergate Pro
- Premium Content Block
- Wishlist Quickfront
- Memberpress Buddypress
- Memberpress Bundle
- Armember Pro
- Simple Membership Pro
- Content Control Cm
- Wp Private Content Plus
- Cimy User Extra Fields