Skip to main content

Report columns

Column presets

Choose a column preset when requesting a report:
  • Operational — call identification, telephony details, duration, status, Outcome category, and health. This is the default preset. It also has the Over agent limit column: yes when the call lasted longer than the agent’s max call duration plus a minute — the calls that did not close in time.
  • Quality — everything in Operational, plus Sentiment, Sentiment score, Call successful, Analytics status, Interruptions, Incidents, Max incident severity, and the p50/p95 percentiles of time to first token and turn time.
  • Business — a short set: Call ID, Started at, Agent, Call status, Status reason, Outcome category, Call successful, Summary, and the custom post-analytics fields of the agents included in the report.
  • Full — everything in Quality, plus Summary, the custom post-analytics fields, Recording link, and the full conversation transcript. The link leads to the call card with the player and opens after signing in to the cabinet; when the call has no recording, the cell is empty.

The transcript as a column

The Full preset carries a whole-transcript column: the entire dialogue in one cell, Agent: and User: in utterance order. An interrupted utterance is marked [interrupted], an utterance where the caller asked the agent to wait is marked [asked to wait]. Agent replies that were never played to the caller are not in the file — they can be seen only in the call card. In XLSX the cell comes with line breaks and a fixed column width so the file stays readable. A transcript reaches the file only when the column was actually picked: an explicit column list overrides the preset entirely, so Full with a trimmed list carries no transcripts.

The column builder

If you need a specific set of fields rather than a whole preset, build it in the report form. The left panel is the catalog of available columns, grouped as Call, Quality, Content, v2 result, Campaign, Custom post-analytics fields and Call variables, each with a readable label and a search box; the right panel is what you selected, in the order it will appear in the file — drag a row, or move it with the up and down buttons. A preset is the starting point rather than a separate mode: pick one, see exactly which boxes it ticks, adjust, and the selector switches to Custom template. An empty selection cannot be generated — a report with no columns would silently fall back to a preset. Each catalog group header shows how many of its fields are selected, such as “2 of 3”, and a Select all / Clear all button. While a search is active the button becomes Select found (N) / Clear found (N) and acts only on the fields you can see; fields hidden by the search are left as they are. Newly selected fields are appended to the end of the selection in catalog order. The same works in the report window on the campaign page. The Call group has an Organization column — the name of your organization. It is not part of any preset. The Outcome category column in the Call group holds the row of the campaign’s outcome breakdown the call falls into, as a machine code: talked (Human Conversation), screener_human_handoff, screener_voicemail_handoff, screener_no_handoff, voicemail and so on. Until the call is finalized the cell is empty. The catalog comes from the server, built by the same code that builds the report itself, so “it was in the list but not in the file” cannot happen. One detail is worth knowing:
  • Custom post-analytics fields are listed from the organization’s agents, or, when the filter selects agents, per each selected agent, one or several — not per call in the period. The list is therefore a superset: a field that exists on an agent but has no calls in the selected period will be exported as an empty column. You can see what you are choosing, which is the point.
Headers inside the file default to the column keys (session_id, started_at) rather than the readable labels from the interface: parsers on your side depend on them, and renaming them by default would break integrations silently. When you do want a readable header, set it yourself — see Column labels. The Column headers file setting decides what goes into the header row: Column labels — your labels, and the column key where there is no label; Technical keys — always the keys, labels are not used. The column builder: the catalog with groups and search on the left, the selected columns in order on the right
Columns are picked from the catalog, not typed as a comma-separated list of keys. The catalog shows everything available, your custom post-analytics fields included, and fills the key in for you. If you build reports through the API, the column keys there are the same.

Call variables

The Call variables group gives one column per variable, holding the value the call ended with — the same value as on the Data tab of the call card. The value came from the upload file or the API, or was written by the agent during the call. The column is filled for every call of the selection, including unanswered ones and calls without post-call analytics.
  • The list is built from the agents. It holds the variables declared in the Agent variables panel of the agents selected in the filter, or of all the organization’s agents when no agent is selected; see Agent variables. If no agent declares variables, the group says so.
  • A variable not in the list can still be exported — for example, one the agent extracts during the call without declaring it in the panel. Request it by name through the API, with the column key var:<variable name>.
  • Presets and saved templates do not change. Variable columns get into a file only when you pick them.

Voicemail

In the Campaign group, seven columns show the voicemail decision for the attempt: Voicemail policy mode, Voicemail policy source, Voicemail withheld by, Voicemail outcome, Voicemail message result, Voicemails today and Voicemails in 7 days. The first five hold machine codes, like Status reason; the last two hold counters of messages left. For a call outside a campaign and for an attempt without frequency rules the cells are empty. These columns are not part of any preset. Voicemail message result tells how the message itself ended: left — played to the end, cut — cut off midway, unvoiced — never played, closed — the machine closed before the message, error — the message failed. The cell is empty when the agent did not try to leave a message.

Call screener

In the Campaign group, two columns show how the agent recognized the callee’s call screener:
  • Screener recognized by — phrase: a phrase from the organization’s list; model: the model decided; watch: the screener spoke after a person had already answered.
  • Screener greeting — the screener’s first recognized words.
Without a call screener both cells are empty. The columns help grow the phrase list: export a report for a period, keep the rows with model and add stable phrases from the greetings on the Call screener phrases page.

v2 form columns

The catalog holds 21 columns that make the file repeat reports in the v2 format:
  • v2 result — five columns carrying the call’s status and result in the v2 vocabulary: Status (v2), Final result (v2), Promise (v2), Overdue reason (v2) and Final result, basic report (v2).
  • Campaign — eleven columns about the campaign, the contact and the attempt: campaign id and name, the contact’s number exactly as you uploaded it, name, external key, row number in your file, attempt number, the reached and counted-attempt flags, Contact ID and Attempt ID.
  • The Call group carries Voice gender and Start language; Content carries two v2 conversation formats and Client speech — a column holding the caller’s speech alone.
None of them belong to a preset. A report where you did not pick columns explicitly will not carry them: these sources are only read when a column asks for them.
Final result (v2) does not fully match v2 files, and that is not a defect. In v2 this value is rewritten by the dialing strategy after the export, so full agreement on it is not reachable. Status (v2), Promise (v2) and Overdue reason (v2) match.