Callbell for WordPress' own callbell_log custom post type and the meta fields it writes per record. No data is copied, no analytics service is added, the cards render straight off the log the integration already maintains.

Yes. The 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 Callbell populates the existing pie and bar cards automatically.

Yes. SleekView Charts supports multi-axis grouping, so a stacked Bar can group by assigned_team on the X axis and stack agents within each team. Useful for seeing how workload distributes inside a team, not just across teams.

Yes when the integration writes first_response_minutes to meta. A Number card for average response time across the team and an Area trend per team flag drift before SLA is widely missed.

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 callbell_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 managers see team-load cards while individual team leads see their own agent breakdown. Each role saves its own filter presets independent of the others.

Yes when Callbell syncs conversation tags and notes to meta. A Pie grouped by primary tag reveals which topics dominate the inbox this month, which feeds directly into docs or product investment decisions.

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 quarterly review needs the raw conversation log, not just the picture.