Skip to main content

Report template

Report template

A layout that you need every week can be saved under a name: in the Conversations report window on the campaign page with Save as template, in the Export calls window in History with Save as preset. A template keeps the columns, their order, the export format and the four settings below — column labels, value replacements, extra columns and file options. An unsaved selection is called Custom template. Templates are shared across the organization — up to 50 of them. Every cabinet user sees them in the My templates group and can rename, overwrite or delete any of them. A template name is 1–80 characters long and unique in the organization, ignoring case and extra spaces. A template must contain at least one column. Change anything in a selected template and the selection switches to Custom template. You can then write the changes into the original template with Update template ”…” — it is overwritten after a confirmation — or save them as a new template. The template actions look different in the two windows:
  • Conversations report — buttons above the column list: Save as template, Update template ”…”, Rename and Delete.
  • Export calls — the Save as preset button and the ⋮ Preset actions menu: Update template ”…”, Save as new preset, Rename and Delete.
Update template ”…” appears when the selected template has been changed; Rename and Delete — when a saved template is selected. The forms in the v2 report forms group are system forms and read-only: they cannot be updated, renamed or deleted. To change one, edit it and save a copy — see Ready-made forms. A template is a copy, not a link. The report job takes a snapshot of it at creation, so editing or deleting a template does not change a single report that has already been generated. For the same reason some columns of an old template can turn out unavailable — say, an analytics field was renamed or removed. The form shows how many: in the Conversations report window with the line “N columns in the template, M unavailable now” listing them, in the Export calls window with an “N unavailable” badge next to the Columns heading. In the list of selected columns they are struck through and marked unavailable now, and they do not go into the file. Filters are deliberately not part of a template. The period is different every time, so a template that also froze “1–14 August” would be useless a month later. A template with none of the settings filled in produces the file in its default shape — if you need none of the below, leave them alone. A saved preset selected in the export window, with its menu: Save as new preset, Rename and Delete

Column labels

Every selected column in the right panel opens a Column name field — what it will be called in the file header. Leave it empty and the header shows the column key. A label is up to 200 characters, and it is template data rather than an interface translation: the platform writes exactly what you typed. This is how you produce the file your recipients already recognize, without changing any parser on our side.

Value replacements

The same column carries a Replace value → with this value table, up to 100 rows per column. Matching is exact, on the string form of the cell; an empty value can be replaced too; anything not in the table is exported as is. The usual use is turning technical values into words the report’s reader understands: completed → Reached, voicemail → Answering machine. An expanded column row: the column name in the file and the value replacement table

Extra columns

Add extra column creates a column that is not in the catalog, of two kinds:
  • one value in every row — a constant: an export code, a source name, a batch marker;
  • several columns in one — a join of two to five catalog columns with your separator. An empty part is skipped, so there are no doubled separators.
An extra column takes its own place in the right-hand list alongside ordinary ones; up to 30 per template. The new extra column card: two catalog columns joined with a separator

File options

In the Conversations report window the settings sit in the File options block, in the Any format and XLSX only groups. In the Export calls window they sit in the File section: with Excel the summary sheet and the split into sheets come right under the format, the rest is under More options.
  • Summary sheet — a separate sheet with totals, the last one in the workbook, after the call sheets.
  • Sheet per column — rows are split across sheets: one sheet per value of a column, with the header on each. Agent, call status and status reason are available. The sheet name is the value cut to 31 characters, with the characters Excel forbids (\ / ? * [ ] :) removed; an empty value goes to the sheet ”—”. The column’s value replacements apply to sheet names too.
  • File name — a name pattern of up to 120 characters. {date} puts in the report’s creation date, {template} the template name. {campaign_id} and {campaign_name} are filled when the report has one campaign — from the campaign page or in History with a single campaign in the filter; with no campaign selected, {campaign_id} is replaced by the report’s creation date and {campaign_name} stays empty. The server adds the extension. Every character other than Latin letters, digits, ., _, - and space becomes _ — a campaign name in Cyrillic turns into underscores.
  • Column headers — Column labels: your column names where set, the column key for the rest; Technical keys: always the column keys, your names ignored. An extra column carries its own name either way.
  • All cells as text — numbers and dates are written as text so Excel does not reshape them: no exponential notation on long numbers, no lost leading zeros. In the Conversations report window individual columns can be excepted (Except columns:) and stay numeric.
  • Date format — one of three: ISO 8601, YYYY-MM-DD HH:MM:SS or DD.MM.YYYY HH:MM:SS. It applies to the Started at column.
The File section with Excel selected and More options open: summary sheet, split by sheets, file name, date format, column headers and all cells as text
For CSV the file name, the date format and the column headers apply. The summary sheet, sheet-per-column and all-cells-as-text are properties of an XLSX workbook. In the Conversations report window they stay visible with CSV and are saved in the template, but they are not applied to the file, and the form says so. In the Export calls window they are hidden with CSV.

The language of the file

The service texts inside an XLSX workbook — the sheet names and the nine summary labels (“Total calls”, “Status”, durations, success rate) — come in your cabinet’s language. Three details:
  • The language freezes when the report is created. The file is built in the background, sometimes well after the request, and by then there is no one left to ask — so the language is written into the job alongside the filter. Jobs already created are not rewritten.
  • The names and descriptions of the ready-made system forms are English.
  • Column labels are not translated. Without your own column name the header carries the column key (session_id, started_at) — parsers on your side depend on the keys. Set a readable header yourself, see Column labels.
The Export calls window: the calls of the current view, the column preset and the CSV/Excel format The Export calls window with the Full preset: the hint that full transcripts make the file larger