> ## Documentation Index > Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt > Use this file to discover all available pages before exploring further. # Call Details > Everything the Call Details panel shows for a single call — the recording player, the Details, Transcript, Analysis, Data Collection and Notes tabs, the editable end reason, objective toggles, system notes, per-call cost and PDF export. ## What is the Call Details panel? Click any row in the [Call Log](/calls/history) and the Call Details panel slides open beside the table. It is the complete record of a single call: the audio recording, the summary and metadata, the full transcript, post-call analysis, the data your script collected, and a notes area for your team. The panel header shows the contact's name and the call's date and time, with two icons on the right — one to download the call as a PDF and an **X** to close the panel. While a call is still in progress the panel updates live — the transcript streams in as the conversation happens, and the summary, analysis and collected data appear shortly after the call ends. For live listening — currently in beta to selected invites only, reach out to the Voxworks team to join — see [Live Monitoring](/calls/live-monitoring). *** ## Recording player Directly under the header sits the recording player: a waveform of the call audio with a play/pause button, an elapsed-time counter and a mute toggle. Click anywhere on the waveform to jump to that point in the call. The recording loads when you open the panel — you'll briefly see *Loading recording...*. If no audio exists for the call (for example, a call that never connected), the player shows *Recording not available* instead. *** ## Details tab The first tab is a one-screen digest of the call, in three sections. ### Call Summary A written summary of what happened on the call, generated automatically after the call ends. If the call hasn't produced one, the section reads *No summary available*. ### Call Objectives If the call's script defines [Call Objectives](/scripts/call-objectives), each objective is listed with its result: * A **green tick** — the objective was met * An **empty circle** — the objective was not met * A **Pending** badge — the result hasn't been determined yet **Objective results are editable.** Click any objective to toggle it between met and not met — useful when you review a call and disagree with the automatic assessment. The change saves immediately and flows through to your Dashboard's Objective Met % metric. ### Metadata A field-by-field record of the call: | Field | Description | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | Type | Inbound, Outbound or Web. | | Call Script | The script that ran on the call, with the script version it was pinned to (e.g. `v2.1`) and a **Test** badge if it was a [test call](/calls/test-calls). | | Batch | The batch the call belongs to, if it was placed by the [Batch Scheduler](/batches/overview). | | Origin | The phone number the call was placed from. | | Destination | The phone number that was called. | | Duration | The call length. | | Status | The call's status, with a coloured indicator. See the [statuses reference](/calls/statuses). | | End Reason | How the call ended — editable, see below. | | Call ID | The call's unique identifier. Hover the row for a copy button. | | Job ID | A technical identifier for the call session. Handy to quote when speaking to Voxworks support about a specific call. Hover for a copy button. | ### Editing the end reason Hover over the **End Reason** row and a pencil icon appears. Click it to reclassify how the call ended, choosing from: * **AI Hangup** * **Failed** * **User Hangup** * **Voicemail** This is useful when the automatic classification got it wrong — for example, a call marked **Voicemail** that actually reached a person. The change saves immediately (*End reason updated*) and is reflected wherever the call appears, including Call Log filters. The full set of end reasons and what each means lives on the [statuses reference](/calls/statuses). *** ## Transcript tab The full conversation, rendered as chat bubbles — the assistant's turns on the right, the contact's on the left, labelled with the contact's first name. If the call produced no conversation, the tab reads *No transcript available*. On live calls the transcript streams in as the conversation happens, and a scroll-to-latest button appears if you've scrolled up while new turns arrive. ### Refined transcription Transcripts are polished a few seconds behind the live conversation: a correction pass reconciles what was heard against the whole exchange and fixes mis-transcriptions of names, numbers and short answers. Where a contact's turn was adjusted, a small sparkle icon appears on the bubble — hover it to see the original transcription under a *DeepListen adjusted* label. Because the assistant acts on what it hears in the moment, the final transcript can occasionally be *more* accurate than what the assistant responded to — which explains the rare case where an in-call decision doesn't quite match the transcript text you read afterwards. *** ## Analysis tab The results of [Post-Call Analysis](/scripts/post-call-analysis) for the call. At the top you'll see the crux of the call (a headline of eight words or less), a short summary and any recommended next steps. Below that, the **Classification** section lists the standard analysis fields — including the call's Outcome, whether an opt-out was requested, whether recording/monitoring was disclosed and approved, whether a calendar booking was made, whether the contact asked for a human or asked if they were speaking to an AI, and a sentiment score from −1.00 (negative) to +1.00 (positive). If your script defines its own analysis fields, they appear in a **Custom Fields** section with the labels you configured. A footer line records when the call was analysed and which outcome set was used. If the call hasn't been analysed, the tab reads *No analysis available for this call.* *** ## Data Collection tab Everything your script's [Data Collection](/scripts/data-collection) fields extracted from the call. A count at the top shows progress at a glance — e.g. *4 of 6 fields collected*. Each field is listed with its label, a **Required** badge where applicable, its description, and the extracted value formatted to its type — Yes/No badges for booleans, option labels for choice fields, formatted dates and times, clickable links for URL, email and phone values, and a dash where nothing was found. Two empty states tell you why the tab might be blank: * *No data collection fields configured for this script.* — the script doesn't define any fields * *Data extraction has not been performed for this call.* — fields exist, but the call hasn't produced values (for example, it hasn't finished yet) *** ## Notes tab A free-text notes area for your team. Click anywhere in the empty area (*Add your first call note.*) to start typing. Notes support Markdown formatting — headings, lists, links, bold and code all render once saved. Save with the tick icon, or discard your changes with the **X**; the panel shows *Unsaved changes* or *No changes yet* below the editor so you always know whether there's something to save. ### System Notes Below your own notes, a **System Notes** section appears when the platform recorded automated activity during the call. Each entry is timestamped and shows the type of event, the tool involved and what it did — for example an SMS being sent, a transfer being attempted, or a calendar booking that failed. System notes are read-only; they are the call's automated audit trail. *** ## Per-call cost Every completed call records its cost in cents against the call record. Cost isn't shown in the detail panel itself — you work with it from the [Call Log](/calls/history), where **Cost (cents)** is available as a filter and sort field and is included in CSV exports. Your running balance and billing details live under **Settings → Billing**. *** ## Exporting a call as PDF Click the download icon in the panel header to generate a **Call Summary Report** PDF for the call. The report includes: * The contact's name and the call's date and time * The metadata grid (Type, Script, Batch, Origin, Destination, Duration, Status, End Reason, Call ID) * The Call Summary * The Objectives with met/not-met indicators * A Data Collection table — Field, Value, Confidence and Status for each configured field * The full Transcript The file downloads as `_call_summary.pdf` — ready to attach to a CRM record or share with someone who doesn't have a Voxworks login. *** ## Next Steps * [Call History](/calls/history) — the Call Log table the detail panel opens from: filters, search, saved views and exports * [Call Statuses, End Reasons & Outcomes Reference](/calls/statuses) — what every status and end reason means * [Data Collection](/scripts/data-collection) — define the fields your script extracts from every call * [Post-Call Analysis](/scripts/post-call-analysis) — configure the classifications that appear in the Analysis tab