✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Charts for Tidio: chat and visitor data dashboards in WP

The Tidio plugin stores the project key and identify rules in wp_options under tidio_chat_settings, and webhook-driven setups sync closed chats and AI bot conversations into a tidio_chat CPT with operator, source, channel, and rating as postmeta. SleekView Charts groups all of that into one WP dashboard.

♾️ Lifetime License available

SleekView Charts dashboard for Tidio Live Chat

Tidio chats and visitors charted in WordPress

The Tidio plugin injects the chat widget and the optional Lyro AI chatbot, and stores the project key, identify rules, and per-page targeting in wp_options under the tidio_chat_settings key. Chats and visitor sessions live in the Tidio cloud, and the WP admin shows a connect screen rather than a chart layer. Teams who want a single WordPress dashboard get none.

SleekView Charts reads the WordPress side plus anything a Tidio webhook lands in WP. Production setups wire the Tidio conversation-closed webhook into a tidio_chat custom post type with operator, source (human or Lyro bot), channel (chat, email, messenger), rating, response_time, and page URL saved as postmeta. SleekView picks up that CPT and renders chart cards: chats per operator, channel mix as a donut, daily volume from post_date, and average response time as a number KPI.

The same dashboard layers in human-versus-bot analysis. The tidio_source postmeta separates Lyro AI conversations from human operator chats, so a single chart card reveals what share of the queue Lyro is now handling and how that share changes month over month. Joined to wp_posts for page-origin analysis and to wp_users for logged-in visitor data, the dashboard becomes a real WordPress reporting surface rather than a tab switch to tidio.com.

Workflow

From Tidio webhooks to a WP dashboard

1

Detect the Tidio data path

SleekView reads the tidio_chat_settings option for the project key and identify rules and registers any tidio_chat CPT populated by the standard Tidio conversation-closed webhook as a charts-ready dataset with operator, source, channel, and rating.
2

Pick chart dimensions

Operator powers a workload bar, channel powers a routing donut (chat, email, messenger), tidio_source powers a Lyro-vs-human donut, post_date powers a daily volume area, and tidio_response_time postmeta powers an average KPI.
3

Layer in human vs Lyro analysis

Split tidio_chat posts by the tidio_source postmeta (human or Lyro) and compare resolution rates, response times, and ratings across both. A weekly area chart of bot share shows AI handoff trends month over month.
4

Save the dashboard

Save the layout as a SleekView, scope it to support-lead and operations roles, and the same cards reopen for every user with access. Layouts export to JSON for copying between staging and production WordPress sites.

Sample dashboard

Charts you can build from Tidio data

Four cards covering volume, operator workload, channel routing, and human-vs-Lyro share, all read from the tidio_chat CPT and tidio_chat_settings option.
Number · Default

Chats this week

A single KPI counting tidio_chat CPT posts for the current week with last week underneath for context. Reads post_date so the headline always matches the timeline area chart shown further down the dashboard layout.
Count
Bar · Horizontal

Chats by operator

Horizontal bar ranking operators by closed-chat count from the tidio_operator postmeta on each tidio_chat post. Surfaces who carried the queue and who has capacity for the next support shift on the rota.
Count group by tidio_operator
Pie · Donut

Channel mix

Donut split across Tidio channels (chat widget, email, Messenger, Instagram) from the tidio_channel postmeta on each tidio_chat post. Confirms which inbound channels are dominant for the current reporting window.
Count group by tidio_channel
Pie · Donut

Human vs Lyro share

Donut split by the tidio_source postmeta across human operator chats and Lyro AI conversations. Reveals what fraction of the queue Lyro is now resolving end-to-end and how that share has shifted recently.
Count group by tidio_source

Comparison

Default Tidio dashboard vs SleekView for WordPress

Default Tidio cloud dashboard

  • Reports live on tidio.com, not next to the WP embed and rules
  • No native join from chats to wp_posts or wp_users
  • Custom WordPress CPT from webhooks has no chart layer
  • Lyro-vs-human share needs an export to be visualized
  • Switching tabs between Tidio and wp-admin breaks support flow

SleekView Charts

  • Chart tidio_chat CPT by operator, channel, source, or rating
  • Plot chats by post_date as a daily or weekly area chart
  • Donut for human-vs-Lyro share from tidio_source postmeta
  • Average response-time KPI from tidio_response_time postmeta
  • WordPress capabilities applied identically to charts and tables

Features

What SleekView Charts gives you for Tidio Live Chat

Lyro share donut

Donut grouped by tidio_source postmeta across human operator and Lyro AI conversations. Shows what fraction of the queue Lyro is resolving without escalation and how that share trends across reporting periods.

Channel mix

Donut grouped by tidio_channel across chat, email, Messenger, and Instagram. Reveals which inbound channel dominates the queue and supports the case for staffing or rule changes in tidio_chat_settings.

Response-time KPI

Average of tidio_response_time postmeta on closed conversations. The same number Tidio surfaces in its own dashboard, visible in WordPress alongside the rest of the site's data and capability filters applied.

Audience

Who builds Tidio dashboards with SleekView

Support leads

This week's chat KPI, operator workload bar, and response-time average. Three cards summarize the morning shift without leaving WordPress for the Tidio dashboard tab.

AI operations

Lyro-vs-human share donut joined to rating averages. Track how much of the queue Lyro handles end-to-end and whether AI-resolved chats keep CSAT in line with human-resolved ones.

Operations

Daily chat volume against operator hours. The area chart surfaces capacity issues a week before SLAs slip and staffing decisions land in time to prevent the queue burning out the team.

The bigger picture

Why Tidio needs a WP-side dashboard

Tidio is the chat surface, but WordPress owns the pages, the WP users behind logged-in visitors, the subscription tier, and the embed rules that decide where the widget appears. Asking which paid tier opened the most Lyro-resolved chats, which page drove the longest response times, or which channel mix shifted after a campaign needs both sides in one chart. The default Tidio dashboard knows none of that WP context, so the workaround is an export to a spreadsheet, which lags behind reality.

SleekView Charts gives Tidio that layer using the same WordPress dataset Tidio integrates against. The tidio_chat CPT and tidio_chat_settings option become first-class chart sources alongside any other dataset on the site. Operator load, channel routing, human-vs-Lyro share, and per-page volume all sit in the same admin as the WP posts and users that drove them.

Questions

Common questions about SleekView Charts for Tidio Live Chat

The plugin stores the project key, identify rules, and embed settings in wp_options under tidio_chat_settings. Chats themselves live in Tidio. Most production setups wire the Tidio conversation-closed webhook into a custom tidio_chat post type so the WP side has the chart-ready dataset.

 

Without the webhook, the WP side only stores the project key and identify rules. Charts are limited to coverage of the widget across wp_posts. For operator, channel, source, and rating cards, configure the Tidio webhook to POST into the tidio_chat CPT first.

 

Yes. The webhook saves the conversation origin as tidio_source postmeta (human or Lyro). SleekView groups by that postmeta for a donut, a bar, or a weekly area chart of bot-resolved share. Comparing AI and human rating averages takes a second chart card.

 

Yes. SleekView honors WordPress capabilities for the tidio_chat post type. An operator role sees their own chats while a support lead sees the full team's. The capability filter applies identically to chart cards and the underlying SleekView table view of the same dataset.

 

Yes. Custom visitor properties pushed via the Tidio identify call land in postmeta on each tidio_chat post during webhook processing. Any select-style property becomes a groupBy dimension for a donut, and any numeric property becomes a sum or average aggregation card.

 

Charts run aggregate queries on view load. Open the dashboard and the numbers reflect the current state of tidio_chat including any webhook posts written up to that moment. There is no caching layer to refresh and no scheduled job that lags behind live data flow.

 

Yes. Clicking a slice or bar opens the SleekView table with the same filter applied. From the operator with the highest bar this week, one click jumps to that exact list of tidio_chat posts, each linking to its transcript in the Tidio dashboard one click further.

 

Charts query tidio_chat using the same indexes WordPress maintains for post-type and postmeta lookups. On sites with tens of thousands of chats archived, dashboards load in well under a second from the admin context with no extra database tuning required.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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