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 sidebar.

Yes. The tokens column on the interaction table sums into a Bar card grouped by model, so finance and operations see which models drive the bill and which ones are underused. The chart card refreshes as new interaction rows land, so the trend stays current between billing cycles without manual rebuilds.

Yes. Each conversation row carries page_slug, and SleekView Charts pivots that into a Bar or Donut card. Marketing leads see which pages drive the most chatbot engagement and which content gaps the bot is being asked to plug for visitors arriving from those URLs across the chosen window.

Yes. Conversations attributed to wp_users.user_id can be filtered by role, and anonymous sessions can be filtered out of any chart card. That separates customer-support traffic from internal-staff testing on the same dashboard without rebuilding the layout for each audience that uses the board.

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

Yes. Each chart card exposes its underlying conversation row set, which exports to CSV with the active filters applied. Finance leads hand the CSV straight to the monthly billing review without round-tripping through a spreadsheet rebuild, and operations uses it for staffing conversations with leadership.

Kognetiks stores assistant runs and file-search interactions in the same database. SleekView Charts can include those rows in the dataset, so a Bar card pivots on assistant_id and a Number card sums file-search invocations alongside the chatbot conversation count for a holistic picture of every Kognetiks feature in use.

Each subsite has its own Kognetiks 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.