Exports

All exports

Export	Where	Who can run it	Format
Report CSV	Results, “Take it with you”	Owner, admin, supervisor, quality reviewer, client viewer	CSV
Usage CSV	Setup, Billing, Export CSV	Owner, admin	CSV
Checked list	A list’s check panel, with the check result and reasons for each person. Client viewers see masked numbers. See check a list	Roles that can open the list	CSV
Do-not-call list	Safety, Do not call	Owner, admin, compliance	CSV
Audit log	Safety, Audit	Owner, admin, compliance	CSV
Evidence pack	A person’s journey record, Download evidence pack	Owner, admin, compliance	ZIP

Files that start a cell with =, +, - or @ get a quote in front. A spreadsheet then shows the text instead of running it as a formula. This is done for the report CSV, the usage CSV and the list export.

Report CSV

The four links download one file each for the period and campaign you picked.

• The numbers above: one row for the whole period.
• By day: one row for each day.
• By campaign: one row for each campaign.
• By agent: calls, talk time, hand-overs taken, billable hand-overs, review count and average score, and seconds talking, in wrap-up and available.

The first three have the same columns: the counts from reading the funnel, revenue in cents, talk time in milliseconds, AI seconds, AI cost, the rates and the two cost rates. A rate that cannot be worked out is empty.

Usage CSV

Columns: day, campaign, kind, quantity and cost in dollars. It matches the Billing page. See usage and charges.

Do-not-call and audit exports

• The do-not-call export has a hash for each number, plus scope, source, note and date added. It never has phone numbers. The list keeps only hashes. Up to 500,000 rows.
• The audit export lists each entry with its link to the one before it, oldest first, up to 200,000 rows. Pick the dates it covers on the page.
• Running either export is itself written to the audit log.

See do-not-call and audit and evidence.

Evidence pack

One ZIP for one person’s journey. It holds:

File	Holds
journey.json	The journey record
consents.json	The consents on file, with the quotes
transcripts.json	Transcripts of the calls
qa_reviews.json	Quality reviews of those calls
compliance_checks.json	The checks run before each call
recordings/	One WAV for each recording
manifest.json	The size and sha256 fingerprint of every other file, and a missing list

The sha256 fingerprint lets anyone check a file was not changed after the export. manifest.json is not listed in itself. The response also carries a fingerprint of the whole ZIP.

What “missing” means

If one part could not be included, the pack is still made and the manifest names the part and gives the reason under missing. A recording that does not match the fingerprint recorded at the time is left out and listed. An empty missing list means every part was found. The journey record itself is required: without it there is no pack.

The export is written to the audit log first. If that cannot be written, the export is refused.

Not yet

The evidence pack was written against assumed answers from the journey, compliance and recording services. Those endpoints exist now, but a complete pack from a live system has not been checked. After your first download, open manifest.json and read missing. If recordings are not connected, the screen says “The evidence pack is not ready yet because recordings are not connected. Try again later.”

Note

Reading a transcript or a recording is not written to the audit log in this build. Only the evidence export is.