SleekView for LiveAgent: WP-side widget & contact form config as tables
LiveAgent tickets, agents and macros live in the LiveAgent cloud. The WP plugin keeps chat-button code, form-to-ticket mappings and JS settings in wp_options. SleekView gives ops one table for that wiring.
♾️ Lifetime License available
Tickets in LiveAgent — wiring in WordPress
LiveAgent's WordPress plugin handles two integration surfaces: a chat-button code snippet that loads the LiveAgent widget on the front end, and a set of form-to-ticket mappings that route contact-form submissions into specific LiveAgent departments with assigned priority. The chat-button code lives in wp_options. The form mappings live in wp_postmeta on each form, with department ID, priority and ticket type stored against the form post.
None of that is summarized anywhere. The default LiveAgent plugin UI shows the chat-button code in a textarea and asks each form plugin to surface its own LiveAgent integration block. There is no list view of every form-to-department mapping, no filter for forms whose target department was deleted in LiveAgent, and no per-form last-submission timestamp. SleekView reads the chat-button option and parses the form-mapping postmeta from each supported form plugin into one table.
The most useful column is the orphaned-department flag. When a department is deleted in LiveAgent, the WP-side mapping points at an ID that no longer exists; new submissions silently fail to route, and the support team only finds out when somebody asks why a request never came through. SleekView marks those rows as Department gone, surfacing the failure before it costs response time. Inline-editing the department field reroutes the form to a current department in one click.
Workflow
LiveAgent wiring, surfaced and audited
Read both storage paths
wp_options and the per-form department mappings from wp_postmeta. Each storage path becomes a row type in the same audit table.
Cross-check departments
Inline-edit routing
Track dead intakes
Sample columns
A typical LiveAgent form integration view
postmeta on each form. SleekView pivots them.
wp_options + wp_postmeta
| Form | Department | Priority | Type | Last submission | Status |
|---|---|---|---|---|---|
| Contact | Support | Normal | Ticket | Apr 24 | Active |
| Sales lead | Sales | High | Ticket | Apr 24 | Active |
| Bug report | Engineering | Urgent | Ticket | Apr 22 | Active |
| Feedback | (deleted) | — | — | Mar 11 | Department gone |
Comparison
Default LiveAgent settings vs SleekView
Default LiveAgent plugin
- Form-to-department mappings live on each form's settings
- No quick way to see which forms post to which departments
- Stale mappings (department deleted in LiveAgent) don't show
- Chat-button code is buried in a textarea
- Per-form priority overrides aren't summarized
SleekView
- All form mappings on one filterable surface
- Detect orphaned forms whose department no longer exists
- Inline-edit department and priority routing
- Track last-submission per form to spot dead intakes
- Multisite roll-up of chat-button installs
Features
What SleekView gives you for LiveAgent
Routing audit
Confirm every form posts to a current LiveAgent department before reorganizing your support team. SleekView flags rows whose target department is gone.
Inline routing edits
Move a form from "Sales" to "Customer Success" by editing the department field in the row. No need to open the form's editor or the form plugin's settings panel.
Multisite chat install
Across networks, every blog has its own LiveAgent button code. SleekView shows them all so agencies can confirm consistency in one network-admin view.
Audience
Who uses SleekView for LiveAgent
Support managers
Audit which WP forms feed which queues so SLAs match the team that owns each request, not the team that used to own it before the last reorg.
Agency support leads
Review every client's LiveAgent install and form routing in one view during onboarding, then walk through the table on the kickoff call.
Marketing ops
Spot dead form intakes (no submissions in N days) and either retire them or fix routing. The audit replaces a quarter-end form-by-form review.
The bigger picture
Form routing drifts faster than support teams notice
Support teams reorganize. New departments get created when a product line spins up. Old departments get archived when a product sunsets.
LiveAgent handles those transitions cleanly inside its own UI, but the WordPress side does not get the memo. A contact form that used to route to "Tier 1 Support" keeps writing the old department ID into every new ticket payload, and the LiveAgent API silently fails to route because the destination is gone. The form looks healthy in WordPress (submissions complete, the user sees the success message) and the failure surfaces only when somebody on the support team asks why a particular kind of request stopped arriving.
Sometimes that takes weeks. SleekView's contribution is to make the routing footprint visible. Every form mapping in one table, with the current department name resolved, and a status pill that flags every orphaned mapping the moment a department is archived.
The audit is fast enough to run weekly. The fix is one inline edit. Together those two things stop the slow leak that broken routing causes.
Questions
Common questions about SleekView for LiveAgent
No. Tickets, agents and macros live in LiveAgent's cloud where the customer record is canonical. SleekView reads only the WP-side wiring: chat-button code, form-to-department mappings and routing flags. Pulling tickets into WordPress would duplicate the support database and add legal weight to the WP install, which is not what a routing audit needs to do.
When a form integrates with LiveAgent, the department ID, priority and ticket type are saved as postmeta on the form's post (or in form-plugin-specific config for builders like Gravity, Fluent and Contact Form 7). SleekView reads the standard locations and produces one clean audit table regardless of which builder was used to create the form.
Counts live in LiveAgent. SleekView shows the last-submission timestamp from the WP-side log if your form plugin records it; for full counts, use the LiveAgent dashboard. The WP-side timestamp is enough to spot dead intakes (no submissions in 30 days) without round-tripping to the LiveAgent reports.
Yes. The next form submission posts to the new department ID. Existing tickets in LiveAgent are not moved; that is a LiveAgent-side action that the support manager runs from inside the platform. The forward-only behavior is what most teams expect during a reorg, since moving historical tickets retroactively would scramble SLA reports.
Yes. The chat-button code option is its own row in the view; you can have one configuration for chat-button installs and another for form mappings. The two storage paths render as different row types in the same audit, with their own filters and inline-edit fields, so the audit covers both surfaces in one place.
Email piping happens entirely on the LiveAgent side; WordPress is not involved. SleekView's scope is the WP-side wiring only. For email-piping audits, the LiveAgent dashboard is the source of truth and the right place to inspect the mailbox-to-department configuration.
Yes. Each blog has its own chat-button option. SleekView aggregates per-blog options into a network-wide audit so agencies running LiveAgent across many client sites see every install in one table. Filtering by department ID or button code works the same way across the network.
HelpDesk-only installs do not use the chat button, only the form-to-ticket mappings. SleekView surfaces only the form rows on those installs; the chat-button row is empty, which is the expected state. The audit table adapts to whichever LiveAgent surfaces are actually in use, without forcing every site to look the same.
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