Call details
Opening a row in History opens the call card: the conversation together with what the platform recorded about the call. The card opens as a panel on the right, over the list. The card header holds:- the agent, the call’s position in the selection — N of M, or Not in current filters when the call is outside the selection — and the ↑/↓ arrows to the previous and next call on the current page of the list (the ↑/↓ keys work too);
- the Attach to Copilot, Open agent and Download log buttons, see actions;
- the channel and direction, the numbers, the date, the duration and the number of turns, the call status with its reason, and the call ID;
- the call’s campaign — a chip with its name; clicking it opens the campaign. A phone call outside any campaign shows No campaign; a chat or a web call has no chip;
- the health badge next to the status — for administrators and developers only;
- the recording player, see recording.
- Transcript — the conversation, in the simple or full view, see below.
- Overview — the Summary from post-call analytics, Call results — the fields AI filled in after the call, Call health and Details: dial time, agent version, engine mode.
- Data — the variables passed to the agent and the webhook deliveries for the call.
- Transcript and events — what the conversation shows in the full view, and the post-call analytics result.
- Troubleshooting a call — provider failures, the caller speaking over a reply, glued replies, turn latency and the synthesis cache.
- Call recording — the player, the stereo waveform and why a recording may be missing.
Simple and full view
For every role the conversation column opens in the simple view — just the dialogue. It shows only the replies that were actually heard: a reply that was never played and the private briefing to the operator are hidden together with their text, and there are no interrupted, not played or operator briefing labels. Node transitions, tool calls, call events and the latency lines are not shown either. Each bubble is labelled with who is speaking — Agent or Client — and the time from the start of the conversation. If a reserve served the call — the model, recognition or voice — the card header shows Reserve services were used: in the recording line, or next to the status for a call without a recording. Everyone who sees the card sees it. Which reserve served what is shown in the full view. The header of an agent reply has a ▶ button: Play reply plays it from the call recording, and until there is a recording — Play the synthesized phrase (from the TTS cache). The timestamp on a reply moves the recording to that point. Administrators and developers see the provider failures the call did not recover from even in the simple view (see troubleshooting a call). The Show system events checkbox above the conversation switches to the full view — the column exactly as described in the sections below: transitions, events, reply labels and latency. Only administrators and developers have the checkbox; the choice is remembered in the browser for each user. The Copy button appears when the conversation has replies and copies the transcript to the clipboard, one reply per line:Agent: … / Client: …. It copies exactly what the column shows: in the simple view only the replies that were heard; in the full view also the replies that were not heard and the marks [interrupted], [not played] and [operator briefing]. The button is available to every role.
The Timeline view
A voice call with a stereo recording has a Chat / Timeline switch above the conversation; the choice is remembered in the browser. Timeline lays the replies out on one time axis: the agent on the left, the client on the right, the height of a block is the length of the speech, and the reply text is shown in full. This shows pauses, long replies and the places where both sides talked at once.- The end of a reply is taken from its channel of the recording. When the recording cannot tell, it is estimated from the text, and the reply is marked approx.
- Simultaneous speech is marked on the line — Both talking — and the reply shows Talking over the other side for and how long.
- An interrupted reply shows its unspoken tail faded, marked Interrupted. A client line said outside a turn is labelled Said outside a turn.
- A click on the line plays the recording from that moment, and the playhead moves along the line. The − and + buttons change the scale.
A member and a manager see the simple view only. They do not have the checkbox at all, and the platform sends them the card without events, transitions, incidents and technical fields — so the observer card and the Details block on the Overview tab are not shown to them either. See roles.
Health
The Call health block on the Overview tab shows whether the call ran into technical problems: OK, Warning, or Error, with the specific reasons listed (for example a failed transfer, a slow turn, or a speech recognition error). With no reasons, the block says so: “No issues — the call went smoothly”. The block is shown to every role; the badge of the same verdict in the card header, next to the call status, is shown to administrators and developers only. A call that never connected does not spoil health when the reason sits with the subscriber or their operator: No answer, Busy, Declined by callee, Invalid number, Blocked as spam. Only a failure of the dialing infrastructure — Trunk auth failed, Provider unavailable, SIP routing error — counts as an error; an unfamiliar reason produces a warning rather than silence. Health is about the technical execution of the call — it’s separate from conversation quality (sentiment and success, covered by analytics), and rule violations (covered by incidents). Use the Any health filter on the History page to find calls with problems.The operator code on a failed dial
Next to the reason, a call that never connected shows the numeric code assigned by the telecom operator — for example “Busy (486)”. Operators interpret these codes differently, so the platform does not offer a reading of its own and says plainly to check the meaning with your own operator. The code is in the cabinet, in report exports, in the Web API, and in webhooks — on every row, so analysing a selection needs no manual matching. Worth knowing: the Declined by callee reason in most cases actually means “busy” — the code helps you see that.A cancelled dial
A dial stopped before it connected — by the button in the cabinet or by aPOST /v1/calls/{id}/end request through the Web API — gets its own reason, Cancelled before the dial, with the Not connected status.
What follows from that:
- a cancellation does not spend a contact attempt, nor the per-number frequency cap: you stopped the dial yourself, and the platform does not count that as an attempt to reach someone;
- a cancellation does not spoil the call’s technical health — it is a human decision, not a platform failure;
- a cancellation by the agent’s own function before dialing is a separate reason, Cancelled by a pre-dial function: in incident analysis and in campaign reporting these are different events.
Webhook deliveries
The Webhook deliveries block on the Data tab lists every webhook notification sent for this call: the event, the delivery status — delivered, queued, sending or dead-letter — the number of attempts with the last response code, and the update time. Clicking a row expands the attempt history. Deliveries that are queued or dead-letter have a Retry button to resend them manually; a member and a manager see it disabled, with the hint Not available for this role.Actions
- Open agent — jump to the agent that handled the call. A member and a manager see the button disabled, with the hint Not available for this role: the agent editor is not open to them.
- Attach to Copilot — add the whole call to the Copilot context (phone numbers and email addresses are masked) and open the agent editor with the Copilot panel. Shown only to those who can edit agents — administrators and developers.
- Download log — export the full call record as a JSON file: the transcript, events, variables, analytics, the health verdict, the recording metadata (without the audio itself) and the flow configuration that was active at the time. Secrets in the file are masked, but it can contain personal data, so treat it accordingly. Only administrators and developers have the button.