Skip to content
AskVault Docs
Try Free →

Export conversations

Written by , Founder, AskVault · Reviewed by Aashiq
Last updated: · 3 min read

Why export

Three patterns:

  1. Customer GDPR data export. Share their conversation history.
  2. Internal compliance. Quarterly archive for audit.
  3. Training data. Use as input for analysis or model improvement.

Single conversation export

Three formats:

JSON. Machine-readable. Full data including metadata.

CSV. Spreadsheet-friendly. Messages with timestamps.

PDF transcript. Human-readable. Branded layout.

Available from any conversation: Conversation > Export > Format.

Bulk export

For many conversations:

  1. Conversations > Filter to the subset you want.
  2. Select up to 200, or click "Export filter".
  3. Pick format and fields.
  4. Click Export.

Smaller exports (under 1,000) complete in under 60 seconds. Larger ones run in background:

  • Email notification when ready.
  • Download link valid 7 days.
  • Files split into 5,000-conversation chunks if very large.

What's included

Per conversation:

  • Messages (all turns).
  • Channel.
  • Customer info (matching identity verification).
  • Tags and audience.
  • Skills triggered.
  • Internal notes.
  • Audit log (claim, escalate, resolve events).
  • Citations when bot answered.

Configurable per export. By default: messages, customer, tags. Audit and notes optional.

CSV column layout

Default columns:

conversation_id, customer_email, channel, started_at, ended_at,
status, priority, tags, message_count, agent_assigned,
csat_rating, csat_comment, first_message, last_message

For per-message export (one row per message), use the "Messages" export mode.

API access

For programmatic export:

Terminal window
curl https://api.askvault.co/v1/conversations/export \
  -H "Authorization: Bearer ak_xxx" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"filter":{"since":"2026-05-01"},"format":"json"}'

Returns a job ID; poll for completion. Useful for nightly archive jobs.

GDPR / customer data export

For end-customer requests:

  1. Contacts > [contact] > Export.
  2. Pick format.
  3. Download.

Includes all conversations for that contact across all channels.

Required for GDPR Article 15 (Right to Access). Complete within 30 days.

Retention and audit

Exports themselves log:

  • Author and timestamp.
  • Filter used.
  • Records exported.
  • File downloaded at.

Useful for compliance: showing who exported what when.

Limits

  • Bulk export size. 10,000 conversations per single export.
  • Background export. Larger volumes split automatically.
  • Download link validity. 7 days.
  • Export jobs concurrent. 3 per workspace.

Common pitfalls

Export too large to email. Split via filter (date ranges).

Missing fields. Pre-export config didn't include them. Re-export with expanded fields.

File format issues. Open CSV in proper spreadsheet tool to handle commas in messages.

PII concerns. Anonymize before sharing externally if needed.

FAQ

Can I schedule recurring exports?

Today, no native schedule. Use API in a cron job. Native scheduling planned.

Can I export audio recordings?

Yes for voice conversations. Audio files in WAV/MP3 included in bulk export.

Will exports respect audience tags?

Yes. Workspace-Editor sees their permitted scope. Workspace-Admin sees all.

Was this page helpful?