Export Reports
Get call data, outcomes and lead fields into your own tools through webhooks, the REST API, the Zoho and Salesforce connector or your warehouse.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
Xebit sends call data to your systems rather than asking you to download it. Every call's outcome, summary, structured fields, transcript and recording can reach your CRM, your own services or your data warehouse as the call ends. Pick the route that matches where your team works.
Export routes
| Route | Best for | What it carries |
|---|---|---|
| Outbound webhooks | Reacting to each call as it ends | Call lifecycle events, outcomes and transfers, to any endpoint you run |
| REST API | Pulling data on your schedule, reports and back fills | Calls, outcomes, recordings, transcripts, campaigns and lists |
| Zoho and Salesforce connector | Keeping CRM records current | Outcome, summary and your fields, written to the right record |
| Your warehouse | Analysis across all calls over time | Call data streamed through the API into your warehouse |
Outbound webhooks
Give Xebit an endpoint and it sends an event when a call starts, ends, transfers or records an outcome. Your handler writes the data wherever it needs to go. This is also how you notify your team or your customers after a call: the webhook fires and your own messaging system sends the message. See Outbound Webhooks.
REST API
Pull calls, outcomes, recordings and transcripts whenever your systems need them, for example a nightly job that builds a spreadsheet for your operations team.
The base URL is https://api.voice.xebit.ai/v1, with a key from the Xebit VoiceCloud dashboard. Mind the rate limits when you pull large ranges.
The base URL is https://<your-xebit-voicekit-host>/v1, with a key from the Xebit VoiceKit admin console. Limits are set by your own deployment.
See Auth Setup and API Keys.
Zoho and Salesforce connector
Connect your CRM once, map the agent's fields to CRM fields, and every call updates the matching record. See Integrations.
Your warehouse
There is no prebuilt warehouse connector. Call data streams through the API into the warehouse you already run, and Xebit builds that hook with your team as part of deployment.
For an ad hoc report, pull the calls you need through the REST API and write them to whatever format your team uses.
What you can export
| Field | What it contains |
|---|---|
| Call ID | The unique ID of the call, useful for matching and for support |
| Contact number | The number called or calling |
| Agent and direction | Which agent handled it, inbound or outbound |
| Time and duration | When the call started and how long it lasted |
| Disposition | How the call ended |
| Summary | What was wanted, agreed and what happens next |
| Structured fields | Everything you defined with the agent, such as lead status, intent or a booked slot |
| Transcript and recording | The full conversation, as text and audio |
Where exports can go
On Xebit VoiceCloud, your endpoints and CRM must be reachable from the internet so Xebit can deliver to them.
On Xebit VoiceKit, delivery starts from your own deployment. On an air gapped deployment nothing leaves the network, so webhook endpoints, CRMs and warehouses must be reachable inside it.
Next steps
- Call Analytics: review calls before you export them.
- Lead Quality Metrics: the lead status you send to your CRM.
- Webhook Failures: when data is not arriving.