What are traces?
Traces let you see the complete flow of a call broken down into individual steps called spans. Each span represents a specific operation — like a conversation turn, an agent response, or a tool execution — with its exact duration. While call logs tell you what happened, traces tell you how long each step took and how they relate to each other.Trace structure
Each call generates a trace with a hierarchical structure. The root span represents the entire session, and individual steps are nested within it:Span types
The span names shown in the trace UI come from the underlying instrumentation, so they may differ slightly from the friendly names in this table. Traces also depend on trace storage availability and may not appear if it is temporarily unavailable.
Information available in each span
Depending on the span type, you can see different attributes:Conversation turns
Executed tools
Path transitions
Use cases
Diagnose slow calls
Identify which step is taking the longest: AI generation? Voice synthesis? An external integration?
Verify conversational flows
Confirm that conversational paths follow the expected transitions between nodes.
Analyze tools
Review which tools were executed, with what parameters, and how long they took.
Understand interruptions
Detect when contacts interrupted the agent and how it responded.