Data Exports let you pull operational data out of SquawkVoice for external reporting, BI tooling, compliance archiving, or backup. Exports are available for call records and AI agent configurations.Documentation Index
Fetch the complete documentation index at: https://docs.squawkvoice.ai/llms.txt
Use this file to discover all available pages before exploring further.
Export Types
Call Records
Export your call history as a CSV file. Includes caller ID, duration, status, disposition, and agent — with optional filters applied.
AI Agent Config
Export a complete snapshot of any AI agent’s configuration as a JSON file for backup or migration.
Call Records Export
Call record exports are initiated from the Call History page.- Open Studio → Optimize → Call History.
- Use the search and filter controls to scope your export — apply date range, agent, status, or disposition filters as needed.
- Click Export CSV.
- The file downloads immediately.
| Field | Description |
|---|---|
| Caller ID | The inbound phone number or identifier |
| Date & Time | Call start timestamp |
| Duration | Total call length |
| Call Status | Completed, failed, no-answer, busy, etc. |
| Agent | The AI agent that handled the call |
| Call SID | Unique call identifier (Twilio SID) |
| Disposition | Outcome set by the agent during or after the call |
The export respects all active filters. If you want a full unfiltered export, clear all filters before clicking Export CSV.
AI Agent Configuration Export
You can export a full snapshot of any AI agent as a JSON file. This includes the agent’s settings, prompt, variables, action references, and knowledge base configuration.- Open the AI agent in Studio → Build → AI Agents.
- Click the ⋮ menu on the agent card (or the options menu inside the agent editor).
- Select Export.
- The file downloads as
ai-agent-{agentId}.json.
- Back up a working agent configuration before making significant changes
- Migrate an agent to a different workspace
- Share a configuration with the SquawkVoice support team for troubleshooting
Tips
- Filter before exporting call records to keep file sizes manageable when working with high call volumes.
- Use Call SID in call record exports as the stable join key if you need to correlate exported data with telephony records from Twilio.