Inspect a call in Voice Debug Monitor¶
Voice Debug Monitor shows what the Agent heard, which information it uses and which tools it calls. Open it from the Agent’s debug view or from Live Calls.
Prepare a test¶
Check that Debug enabled is on and that you have access to the debug view. Open the call early. Events from before you opened it may not be available.
Use Call Setup to check which settings were used for the call. Start a new test call after changing the configuration.
Read the panels in order¶
| Panel | What it helps establish |
|---|---|
| Call Setup | Greeting, executing Agent, configuration and available pre-processing status |
| Caller Speech | What was recognized, including finalized utterances and pauses |
| Assistant Response | Generated response and timing |
| Prompt context | Resolved history, facts, language and lookup context |
| Knowledge | Search decision, rewritten query and retrieved content where captured |
| Tools | Invocation timing and available results or errors |
If a name is wrong in Caller Speech, inspect recognition before rewriting the prompt. If transcription is right but an action occurs too early, inspect the prompt and tool description.
Check missing information¶
The view shows the information available at that point in the call. Newly saved facts may appear on the next turn. If knowledge is missing, check whether the search decision skipped the lookup.
For a Flow, review routing decisions and the selected specialist in the Flow debug view. The number's entry route and the Flow's intent decision are separate checks.
Share a useful case¶
Use Copy context where offered to capture the selected diagnostic context. Review and remove unnecessary personal information or sensitive integration data before sharing. Include the expected outcome, actual outcome, call identifier and approximate time.
After one targeted change, start a new call and repeat the same scenario. Review the finished summary separately in Call History.