Skip to main content
Data Exports let you pull operational data out of SquawkVoice for external reporting, BI tooling, compliance archiving, or backup. You can export your call, chat and email records as CSV files, and any AI agent’s configuration as a JSON file.
Record exports run in the background. You start one from a history page, and when it’s ready you download it from the Data Exports screen. Agent exports are different: the file downloads straight away.

​
Export Types

Call, Chat and Email Records

Export your history as a CSV file, one row per conversation, including each summary and full transcript. The export uses the time range, agents and filters you set. See Call Records Export and Chat and Email Exports.

AI Agent Config

Export an AI agent as a JSON bundle for backup or migration, and bring it back later with Import Agent. See AI Agent Configuration Export.

​
Call Records Export

Call record exports are started from the Call History page.
1
Open Optimize → Call History and set the time range, agents and filters you want. See What the export covers.
2
Click Export, at the top right of the table on the same row as the search box. Studio shows Starting export job… and then Export job started! You will be notified when it’s ready for download. Nothing downloads yet.
3
When the job finishes, Studio shows Export completed and ready for download. If the file can’t be built, Studio shows an Export failed: message instead, and the reason is on the export’s row on the Data Exports screen.
4
Open Manage → Data Exports and select the download icon on your export’s row. See The Data Exports Screen.
Data Exports isn’t in the default sidebar. Add it with Customize sidebar, or press Cmd/Ctrl+K and search for Data Exports. See Navigating Studio.

​
What the export covers

The export is built from the settings on the Call History page at the moment you click Export. It isn’t limited to the rows loaded on screen.
  • Time range. Always applied, so every export covers a range of dates. It’s the range showing in the header. Opened from the sidebar, Call History starts on Last 7 Days, and you can choose Today, Last 30 Days or Custom Range. There is no all-time option, so for a longer history set a Custom Range that covers it. Days are counted in your browser’s time zone, or in UTC if Use UTC is switched on in the time range menu.
  • Agents. Only the agents you selected. With All agents, every agent’s calls are included.
  • Filters. The switches in the Filters menu that are on: Contained, Transferred, Pinned Only, User dissatisfied and Action Errors.
  • Drill-downs. If you opened Call History from a drill-down link on an analytics page, such as a disposition in Call Analytics, the disposition, sentiment or topic that link carried is applied to the export too.
The search box isn’t applied. Text you type in it narrows the list on screen but not the export, so searching for one caller and clicking Export still exports every call in the time range. To get specific calls, narrow them with the time range, agents and Filters first, or filter the CSV afterwards on Call SID, Caller ID or Called Number.

​
What’s in the file

The CSV has one row per call, newest first, with these columns in this order: Two columns can read differently from the Call History screen:
  • Start Time and End Time are always in UTC. The Call History table shows your browser’s time zone unless Use UTC is on.
  • Disposition is the value as recorded. A call the table shows as Contained is recorded as Hangup, so it reads Hangup in the CSV.
Status is one of COMPLETED, IN_PROGRESS (a call that hadn’t finished), ERROR (the call ended with the bot_error disposition) or REJECTED (the call was refused before it started, usually because the balance couldn’t cover it). The Disposition of a REJECTED call reads INSUFFICIENT_BALANCE when the balance was the reason and SYSTEM_ERROR for any other reason, and calls refused before 20 October 2026 all read INSUFFICIENT_BALANCE, whatever the reason. A test call from a campaign that went through the compliance check but never became a conversation is listed as BLOCKED when the check stopped it before a call was placed, or NO_ANSWER when it was placed but not answered. Most other columns are blank on these rows. They aren’t included when Pinned Only, User dissatisfied or Action Errors is on. Only test calls appear this way: the blocked dial attempts that Call History lists for your campaign runs aren’t in the file. See Blocked Dial Attempts.
Call exports include each call’s summary and full transcript, which can contain personal and confidential information from your callers. Treat exported files as sensitive and store them securely.

​
Chat and Email Exports

Optimize → Chat History and Optimize → Email History have the same Export button, at the top of the list, and it works the same way as Call History: it queues a job, Studio tells you when it’s ready, and you download the CSV from Manage → Data Exports. See Chat History and Email History for those pages. The export covers your conversations that match the time range, the agent selection and Pinned Only. The search box and the other filter switches on those pages aren’t applied. The file has the same thirteen column headings as a call export, including Agent Version, Summary and Transcript, so the same warning about sensitive content applies. Refused chats and unanswered emails are in the file too. A chat the visitor was refused as it opened, or a customer email an agent couldn’t answer, because the balance couldn’t cover a session gets a row with REJECTED as its Status and INSUFFICIENT_BALANCE as its Disposition. A chat or email refused for any other reason shows SYSTEM_ERROR there instead, except that emails refused before 20 October 2026 all read INSUFFICIENT_BALANCE. These rows have 0 in Duration (seconds) and nothing in Agent Version, Summary or Transcript, and an email row’s Agent Name reads N/A. Refusals from before 14 October 2026 weren’t recorded. See Chat History and Email History.
The Data Exports list doesn’t say which page an export came from. The file name does: it starts with voice_, chat_ or email_, followed by export and the start and end dates, for example chat_export_20261007_20261013.csv.

​
The Data Exports Screen

Manage → Data Exports lists the CSV exports requested from Call History, Chat History and Email History, and it’s where you download them. It shows exports requested by everyone in your workspace. You can download or delete only the ones you requested yourself.

​
Reading the list

The table shows the newest exports first, loads 20 at a time and loads more as you scroll. It reads No export jobs found. when there are none. Select By Me to show only your own exports. Studio then shows Showing exports by followed by your email address. Select By Me again to show everyone’s. The Status column shows one of four values, in lowercase: Rows update by themselves while the screen is open. If a row that has just failed, or just finished with no data, doesn’t show its reason yet, refresh the page.

​
Export Details

Select any row to open the Export Details drawer. It shows:
  • User — who requested the export.
  • Time Frame — Today, 7 days, 30 days or custom.
  • Pinned Only — Yes if the export was limited to pinned conversations.
  • Date Range and Timezone — the range the export covers and the time zone it was counted in.
  • Status — the same status as in the list.
  • Requested At — when the export was requested.
  • Processed At — when the job finished or failed. It appears once the export has finished.
  • Error Message — shown when the export failed, or finished without a file (see below).
The drawer has Download and Delete buttons. Download stays unavailable until the export is completed and has a file. While the export isn’t completed, the drawer also says Download is available once the export job is completed.

​
Download

Select the download icon on a completed row, or Download in the drawer. The CSV saves to your browser’s usual download location, and Studio shows Export downloaded successfully. If you try to download or delete an export that a teammate requested, Studio shows an error instead, because those actions work only on your own exports.

​
Delete

Select Delete in the drawer, then Delete Export to confirm. Deleting can’t be undone: it removes the export from the list and deletes its file. An export that is still queued or processing can’t be deleted until it finishes.

​
Exports with no data

If nothing matches your time range and filters, the export still finishes as completed, and Studio still shows Export completed and ready for download, but no file is created. The row has no download icon, and the drawer’s Error Message reads No data available for export. With Pinned Only on and no pinned conversations, it reads No pinned calls available for export. Widen the time range or switch off a filter and export again.

​
AI Agent Configuration Export

You can export an AI agent as a JSON file to back it up or move it to another workspace. The file is a bundle designed to be imported back into Studio with Import Agent. Its contents are encrypted, so it isn’t a readable or hand-editable copy of the configuration. It captures the agent as it is currently saved in Studio, including any edits you haven’t published yet, and it includes the agent’s settings and instructions, actions, flows, variables, data transformers, auth profiles and the FAQs and web sources of its linked knowledge groups. An agent you import from the file starts as Not published; see Publishing Your Agent. See AI Agents → Export for what the bundle contains and Import for what happens when you bring it back.
1
Open Build → AI Agents.
2
Select the ⋯ button (More actions) on the agent’s row. Export is in this menu, not inside the agent editor.
3
Select Export. Studio shows Preparing export… and then Export downloaded.
4
The file downloads as assistant- followed by the agent’s name and .json, for example assistant-Support Agent.json.
You can also press Cmd/Ctrl+K and run Export AI Agent. It exports the agent named in the heading of the shortcut group: the one you have open, the one you opened most recently, or your workspace’s most recently updated agent. It runs straight away, so check the name first. See Navigating Studio. When you export this way, each run of characters other than letters, numbers, hyphens and underscores in the agent’s name, such as a space, becomes a single hyphen in the file name, so Support Agent gives assistant-Support-Agent.json. Agent exports download immediately and don’t appear on the Data Exports screen. To export an agent as it was when one of its versions was published, instead of as it is saved now, select Export Version from the version’s menu in Version History. It downloads straight away too, and Import Agent brings it back as a new agent. See Version History. Use agent exports to:
  • Back up a working agent configuration before making significant changes
  • Migrate an agent to a different workspace, using Import Agent at the top of Build → AI Agents
  • Share a configuration with the SquawkVoice support team for troubleshooting
Agent exports contain your agent’s instructions and configuration, and they include the credentials your actions use to connect to other services. Treat exported files as sensitive and store them securely.

​
Tips

  • Narrow the export before you click Export. Set the time range, agents and Filters switches first, because every row carries a summary and a full transcript and files grow quickly with high call volumes. The search box doesn’t narrow an export.
  • Use Call SID in call record exports as the stable join key if you need to correlate exported data with telephony records from Twilio.
  • Check the time zone. Start Time and End Time in the CSV are UTC, so convert them before comparing against Call History if you view it in your browser’s time zone.
  • Delete exports you no longer need. Select the export on the Data Exports screen and delete it once you’ve saved the file where you need it, because it holds conversation content.