Перейти к основному содержимому

Export jobs

An export job copies your data to one of your own storage buckets, once or on a schedule: call recordings, voicemail, the call history, team chat with its files, transcripts with their AI summaries, SMS and channel messages, the audit log, faxes and the standard reports. Use it to keep an archive under your own control, to feed a data warehouse, or to meet a records retention rule. Each file is checked after upload, and every run leaves a manifest in the bucket that lists every file with its size and SHA-256.

What you need​

  • A storage destination that passes its test, under Admin, Settings, Storage, Storage destinations.
  • The integrations:write permission, and for the whole company the permission that reads the data you export: recordings:read for recordings and transcripts, voicemail:read, call_history:read, privacy:export for team chat, messaging:read, audit:read, fax:read or reports:read. Nobody can export what they could not read.
  • For the call history, the audit log, the reports and the queue or tag filters, the call history database must be set up on the server.

Create a job​

Open Admin, Settings, Storage, Export jobs and choose Add export job.

  1. Pick the data, the destination and how often: continuously (new records leave within about a minute), hourly, daily, weekly on Mondays, monthly on the 1st, or once for a period you give. Daily, weekly and monthly jobs run at the hour you choose in the job's time zone.
  2. Start from decides how far back the first run goes. Empty means from now on.
  3. Set the path template: where each file goes in the bucket. Show an example path renders it for a sample recording. For example {company}/{yyyy}/{mm}/{dd}/{queue}/{direction}/{call_id}_{caller}_{callee}.{ext}. Dates are in the job's time zone. Names are cleaned to letters, digits and . _ - = @ +, so a caller name can never create a folder.
  4. Choose the formats: Opus (about a tenth of the size) or WAV for audio; CSV, JSON Lines or Parquet for tables, with gzip or zstd compression if you like.
  5. Choose the metadata: the standard fields (call id, company, agent, queue, direction, duration, disposition, retention date, whether the consent announcement played (consent: announced or none) and more) as object metadata, some of them as object tags for lifecycle rules, your own key=value entries, and an optional JSON file next to every file. Hash phone numbers replaces numbers with a hash that stays the same within the job.
  6. Narrow the records if needed: sites, departments, queues, users, directions, numbers or call tags.

Runs​

Runs (in the ... menu of the job, with Run now, Edit and Delete) shows each run with its period, the files and bytes delivered, failures and the manifest's name. Run now starts a run within a minute.

A run that could not deliver every file is marked Partly delivered. Nothing is lost: the job tries the same period again a few minutes later and sends only what is missing. A recording deleted before it was exported is counted as skipped.

A destination that export jobs write to cannot be deleted; change or delete the jobs first.

Install-wide jobs​

Administrators of the whole install find Install export jobs under Admin, Settings, System, Backups. These jobs export several or all companies to an install-wide destination; each company's files carry its own name in the path.

Limits​

  • MP3 is not offered; use Opus or WAV.
  • A call still running when its period closes is exported as it stood; call history runs leave the last 30 minutes for the next run.