Respond.io for WordPress' own respondio_log custom post type and the meta fields it writes. No data is copied, no analytics service is added, the cards render straight off the log the integration already maintains in WordPress.

Yes. The webhook integration writes one log row per event regardless of channel, with the channel name in meta. SleekView Charts treats every channel as a slice of the same dataset, so adding a new connector in Respond.io populates the existing pie and bar cards automatically.

Yes. SleekView Charts supports multi-axis grouping, so a stacked Bar can group by assigned_agent on the X axis and stack channels per agent. Useful for seeing which agents specialise in which channels rather than just totals.

Yes when the integration writes first_response_minutes to meta. A Bar filtered to rows above the SLA threshold ranks conversations breaching SLA, and an Area trend on average response time flags drift before the threshold is crossed widely.

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

Yes. Each saved chart dashboard is scoped by WordPress capability, so support leads see operational cards while marketing leads see channel-share cards. Each role saves its own filter presets independent of the others.

Yes. The plugin writes source as meta when Respond.io detects which campaign or page started the conversation. A Pie grouped by source reveals which acquisition surfaces drive the most inbound conversations across all channels.

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 when a customer-success review needs the raw event log, not just the visual.