Tracing gives you full visibility into what happened during a test call or live call. It's one of the most powerful features for making your voice agents production-ready.
With traces, you can see:
- The exact conversation that occurred
- What prompts were sent to the LLM
- Which tools the LLM had access to (and which it called)
- Speech-to-text transcriptions of user input and Transcription errors
Traces are organized by event type. The two most important sections to focus on are:
### STT (Speech-to-Text)
These entries capture the transcription of what the user said during the call. Each STT entry shows the text conversion of the user's speech at that point in the conversation.
**Example:**
STT: "Yeah, I would want to check what your operating hours are."
### LLM (Language Model Calls)
These entries show every call made to the LLM. Each LLM trace includes:
- **Prompt** - The full prompt sent to the LLM (combination of global prompt + node-specific prompt)
- **Conversation history** - The entire conversation up to that point
- **Available tools** - All tools the LLM can access for that node
Each LLM call shows the tools available to the agent at that moment. These fall into three categories:
### System Tools (Default)
Every node includes these by default:
- **Safe Calculator** — Helps LLMs perform math accurately
- **Get Current Time** — Retrieves current time
- **Convert Time** — Converts time to a specific timezone
### Pathway Tools
These correspond to the pathways (node transitions) you've configured. For example, if your node has pathways to "End Call" and "Move to Summary," you'll see those as available tools.
The tool descriptions shown in traces match the descriptions you set in your pathway configuration.
Any external tools you've attached to the node (e.g. any custom tools you created for API endpoints for booking, order submission, etc.) will appear here. See the [custom tools documentation](/voice-agent/tools/http-api).
