Transcript and events
This is part of the call card: the conversation column in the full view and the Overview tab with the post-call analytics result.Transcript and call events
This page describes the full view, with Show system events switched on — see simple and full view. The transcript shows each reply in order. Every agent reply is captioned with its node. A transition between nodes is a chip in the middle of the feed,from → to, right before the reply of the node the conversation moved to; the chip carries the condition badge used on the canvas edges (ALWAYS, PROMPT and others), and the badge’s tooltip names the transition type in words. When the model chose the transition, its decision is tucked into the chip: a click on the chip shows who decided and how confidently. A decision with an error or a timeout is expanded right away. A model decision to stay in the node makes no transition and shows as a separate event line.
Alongside the transcript, the platform shows call events at the point where they happened, each with an icon, a short summary, and a status pill you can click to expand into full detail (request/response, stages, or arguments):
- Function call — a function or tool was called, with its arguments, response, and duration.
- Knowledge base search — a query was run against a knowledge base, with the passages returned and how relevant they were.
- Call transfer — a call transfer attempt, with its stages (hold, dialing, answered, briefing, bridged, and so on) and outcome. On a warm transfer the stages can include operator briefing skipped: the caller could not be isolated, with a warning status: the platform could not take the caller off the agent’s audio, so it connected the operator without the briefing rather than let the caller hear it. If the caller hangs up while the agent is announcing the transfer, the outcome is Caller left before the transfer (
caller_left): this is not a failure, the agent says no error line, and the call closes as an ordinary hang-up by the caller. - Silence reminder — a silence reminder was played.
- Auto-end — the call ended automatically, for example after too much silence.
- Voicemail — an answering machine was detected and the agent carried out the action from its settings: hung up or left a message. Answering machine detection — the detector’s verdict after which the call went on: a person answered, or a voicemail was recognized but the agent is set to continue as with a human. Both events name the reason for the verdict and show what decided: exact phrase, model hint, model, provider signal, monologue, silence on the line, audio model, phone number, screener phrase or IVR pattern. When a phrase decided, the phrase itself and its source are shown next to it — for example organization list from the Voicemail phrases page, or agent phrases. The marker phrase in the interim transcript note means the phrase was caught in the middle of the greeting, without waiting for the final speech recognition result.
- Caller hung up — the caller ended the call.
- Code node — a code step ran and updated variables.
- Call settings override — an Override Settings node switched the voice, speed, language, volume, models or speech recognition for the rest of the call.
- An event with the code
turn_rollback— a pause split the caller’s sentence in two; see a reply glued from fragments below.
- interrupted — the reply was cut off by the caller and only the spoken part is shown.
- not played — the reply was generated but the caller never heard it; it’s shown dimmed so you can debug what the agent intended to say without mistaking it for something the caller actually heard. The hint on the label distinguishes two causes: the call ended before the reply started, or the speech was interrupted before its first sound.
- operator briefing — a private message the agent gave to a human operator during a transfer, not heard by the caller.
- said during agent’s reply — a caller utterance spoken over a non-interruptible agent reply; see The caller spoke where interruption was not allowed.
- Reserve model, Reserve voice on an agent reply and Reserve recognition on a caller reply — the reply was served by the agent’s reserve: the answer model, the voice or the recognition.
- asked to wait — the caller asked the agent to wait. The utterance is kept as a record: there was no turn for it, the agent paused. See pause on client request.
An interruption truncates exactly the utterance that was interrupted. When the agent speaks twice within one turn, the truncation lands on the second phrase and leaves the first one — the one the caller actually heard — intact.