Conductor can create an analytics dashboard from a request such as "Build a dashboard of call volume and latency by agent". The dashboard appears on Analytics like one you built yourself, and you can edit, rearrange or delete its charts there.
Build a dashboard#
Ask in a Conductor conversation#
In the side panel or on Home, describe the dashboard. Mention "dashboard", "chart", "graph" or "visualise" so the request is routed to the dashboard action, or let Conductor pick it.
Open it#
The reply names the dashboard and the number of charts. Choose Open dashboard name (side panel) or Open "name" in Analytics (Home).
Name the dashboard in your message with "dashboard for ...", "dashboard of ...", "dashboard about ...", "dashboard called ..." or "dashboard named ...". Otherwise it is called "Conductor dashboard".
What Conductor can chart#
With an OpenAI key, Conductor chooses the charts from these options:
| Option | Values |
|---|---|
| Metric | call_count, call_duration, call_cost, success_rate, negative_sentiment_rate, e2e_latency |
| Measurement | count, sum, avg, median, p90, min, max, rate |
| Breakdown | none, agent, direction, call_type, disconnection_reason, user_sentiment |
| Chart type | line, bar, column, donut, number, table |
In mock mode it uses keywords in your message:
| Your message mentions | Chart added |
|---|---|
| volume, count, how many, calls per, number of calls (or none of the topics below) | Calls per day (line, count) |
| Always added | Success rate (number, compared with the previous period) |
| sentiment | Negative sentiment (line, rate) |
| latency, slow, speed | E2E latency p90 (line) |
| cost, spend, money | Cost (bar, sum) |
| duration, long | Average duration (line) |
"By agent", "per agent" or "each agent" breaks the charts down by agent; "direction", "inbound" or "outbound" breaks them down by direction.
Limits#
| Limit | Value |
|---|---|
| Dashboards per workspace | 10. Conductor refuses to build an eleventh: "A workspace can have at most 10 dashboards. Delete one first." |
| Charts per Conductor dashboard | 12 |
| Layout | Two charts per row, each half the width of the grid |
| Time zone | Australia/Sydney |
| Filters | None. Add filters on Analytics afterwards. |
Ask about a dashboard#
Attach a dashboard (Dashboards tab in Attach context) to ask questions about it. Conductor sees its name and chart titles, not the chart data.
Send analytics to the edit panel#
Ask Conductor in the Analytics header opens the agent edit panel with a summary of the period in view attached: total calls, success rate, average duration, p50 end-to-end latency, sentiment counts and the top disconnection reasons, for the selected agent if one is chosen. Use it to ask for agent changes based on the numbers, for example "success rate is low and many calls end with inactivity, what should change in the prompt?" See Build and refine.
Guided tour#
Ask "Walk me through building a dashboard", or type "analytics" in Guided tour. The tour opens Analytics and highlights adding a chart, its breakdowns and saving it.
Related#
- Conductor overview
- Call and chat history to investigate the calls behind the numbers.