Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.oration.ai/llms.txt

Use this file to discover all available pages before exploring further.

The Analytics page shows you a visual map of how customers interact with your agents and flows. Whether you’re debugging a tricky drop-off or tuning a high-performing flow, it gives you the data you need to make better decisions. You can reach it by clicking Analytics in the sidebar, under the Conversations heading.

Overview

Analytics uses a Sankey chart — a flow diagram where wider paths mean more conversations followed that route — to show you the sequence of events in a conversation. At a glance, you can see:
  • Where customers engage most
  • Where they tend to drop off
  • How often specific events are triggered
You can filter the chart by:
FilterDescription
Entity typeAnalyze a specific Agent or a Flow
Date rangeFocus on a particular timeframe
Event definitionsAgents only — filter by events you’ve defined, like intent matches

Agent analytics

Agent analytics helps you understand how a specific AI agent handles conversations.
1

Select your agent

In the Entity selector, choose the agent you want to analyze.
2

Set a date range

Pick the timeframe you want to look at using the Date range selector.
3

Filter by events (optional)

Use the Event definitions dropdown to focus on specific events. If you leave this empty, the chart defaults to showing system events.

Configuring event definitions

Event definitions let you track meaningful milestones in a conversation — things like a customer confirming an appointment or providing their phone number. Before they show up in analytics, you’ll need to set them up in your agent’s settings.
1

Go to agent settings

Navigate to your agent and open its Settings page.
2

Open post-call analysis

Select the Post-call analysis section.
3

Create a new event

Click to add a new event, then fill out the definition form.
Each event definition needs a Name and a Description of when it should fire. You also choose how Oration detects it:
  • AI detection — Oration’s AI reads the conversation transcript and decides whether the event occurred based on your description. Great for nuanced, context-dependent moments.
  • Regex pattern — You provide a regular expression (e.g., \d{3}-\d{3}-\d{4}) to match exact text in the transcript. You can choose whether to check messages from the agent, the customer, or both.
Use AI detection for open-ended events (like “customer expressed frustration”) and regex patterns for structured data (like phone numbers or order IDs).

Reading the chart

The chart traces the path of conversation events between your customers and your agent. Thicker lines mean more events followed that path. Hover over any part of the chart to get an exact count:
  • Hover over a node — see the event name and its total event count across all conversations in the selected date range.
  • Hover over a link (the band connecting two nodes) — see the source and target event names, each with a colour indicator, and the number of events that moved along that specific path.
Use the chart to:
  • See the most common conversation paths
  • Find where conversations frequently end
  • Check how often specific events are triggered

Flow analytics

Flow analytics shows you how callers move through your IVR or flow setup — node by node.
1

Select your flow

In the Entity selector, choose the flow you want to analyze.
2

Set a date range

Pick the timeframe using the Date range selector.
Flow analytics doesn’t use event definitions — it tracks movement through your flow’s nodes instead.

Reading the chart

Instead of conversation events, the chart tracks how callers move through each node in your flow — things like Play Audio, Condition, or Transfer. Every node shows its icon and label so you can orient yourself quickly. Hover over any part of the chart to get an exact count:
  • Hover over a node — see the node name and the number of conversations that passed through it in the selected date range.
  • Hover over a link (the band connecting two nodes) — see the source and target node names, each with a colour indicator, and the number of conversations that moved along that specific path.
Use the chart to:
  • See what percentage of callers reach each node
  • Spot where callers drop off before finishing the flow
  • Confirm your routing logic is working as expected