MessageBird for WordPress' own messagebird_log custom post type and the meta fields it writes per record. No data is copied, no analytics service is involved, the cards render straight off the log the plugin already maintains in WP.

Yes. The plugin logs WhatsApp sends to the same post type with channel set to whatsapp and template_id reflecting the approved WABA template. SleekView Charts treats WhatsApp sends as a slice of the same dataset, so channel-mix and per-template cards include them automatically.

Yes when the plugin's inbound webhook is enabled. Inbound messages land as the same post type with a direction meta of inbound, so a Bar grouped by template_id with a direction=inbound filter ranks which templates drive replies, not just deliveries.

Yes. The status meta records delivered, failed, expired and the rest of MessageBird's lifecycle states. A Pie grouped by status flags the failed share at a glance and an Area with a status filter trends failure rate against time so a drift surfaces before customers do.

No. WordPress indexes the post type by date and ID, and SleekView Charts batches the meta joins behind a cache. Logs with hundreds of thousands of messagebird_log rows render the dashboard in well under a second on typical Kinsta or WP Engine hardware.

Yes. Each saved chart dashboard is scoped by WordPress capability. Support leads see the operational cards while marketing ops sees the campaign cards, with each role saving its own filter presets without changing the underlying MessageBird log.

Yes. Conversations are tracked as their own thread records linked to the contact. A Number card for active conversations and a Bar grouped by assigned agent give a simple shape for who is carrying the load this week.

Yes. Every chart card is backed by a SleekView dataset, so the export button on the table view exports exactly the filtered rows powering the chart. Useful for post-incident reviews where someone needs the raw delivery records, not just the picture.