No. The conversation viewer stays in place and remains the right place for individual chat inspection and quality review. SleekView Charts adds the cross-cutting weekly dashboard the default screens do not assemble, so the two layers complement each other rather than competing for the same screen real estate inside the admin.

Yes. The contact_id column on the conversation table joins to fc_subscribers, so a chart card can pivot conversations on subscriber status, tags, or lists. Marketing leads use it to see which segments engage most with the bot and which campaigns underperform on lead capture across the chosen window.

Yes. Conversion rate is the count of rows with contact_id present divided by total conversations, which is a straightforward aggregation in SleekView Charts. The Number card surfaces the rolling rate alongside the previous period so changes in onboarding flow show up in the headline KPI immediately.

Yes. Dashboard-level filters apply to every chart card so the whole dashboard responds to a single bot filter or campaign tag filter. That makes per-bot reviews and per-campaign retrospectives a one-click switch rather than a per-card configuration job for each chart in the layout.

Yes. Aggregations run on the indexed columns Fluentbot already maintains on the conversation and message tables, so sites with thousands of weekly conversations render charts in seconds. The Charts engine uses pagination and indexed joins rather than scanning the message body on every render.

Yes. Each chart card exposes its underlying conversation row set, which exports to CSV with the active filters applied. Operations leads hand the CSV straight to the quarterly review without round-tripping through a spreadsheet rebuild, and marketing uses it for campaign retrospectives with leadership.

Both plugins write to neighbouring tables in the same database, and SleekView can join them on contact_id. A single dashboard can show conversation volume next to FluentCRM list growth, so chatbot impact on the email list lives in one place rather than across two browser tabs in the admin sidebar.

Each subsite has its own Fluentbot tables, and SleekView Charts reads the current subsite's data by default. Network-wide dashboards can be configured explicitly when reporting needs to span multiple subsites, with the join layer joining the per-site tables into a single network view of chatbot performance.