Call Auditing for Businesses: How the Module Works
The enterprise call auditing module: send recordings from your operation, organize by agents, teams, and scripts, and track metrics — via dashboard and API.
The call auditing module is an enterprise feature for operations that record calls — call centers, sales teams, support. Instead of transcribing call by call manually, your operation sends recordings at scale and receives processed audits, organized by agent, team, and script.
What the module offers
- Audits at scale: each recording sent becomes an audit processed asynchronously — you send it, and the result arrives in your system via webhook.
- Operation setup: agents (with an external identifier from your system), teams, and versioned scripts — to evaluate the call against the script in effect at the time.
- Metrics: analytical summary of the operation and a per-agent view.
- Usage and consumption: track what the operation processed in the period.
Where do I manage it
Management is in the organization dashboard, at /dashboard/organization/auditorias. There, OWNER and ADMIN create the organization API keys that the integration uses:
- Up to 10 active keys per organization;
- Each key has permission scopes (e.g., create audits, read audits, read usage and analytics) — by default, what wasn't granted is denied;
- A compromised key can be revoked immediately, without affecting the others.
The keys belong to the organization, not the user. Treat them as infrastructure secrets: environment variable on your server, never in the front-end or spreadsheets.
How recordings come in
Two paths, designed for telephony:
- By URL — if your PBX/platform exposes the recording at a public
httpsURL, send the URL directly. - By upload — if the recordings don't have a public URL, the API provides a temporary upload URL (valid for 1 hour) to upload the file, and you reference that upload in the audit.
Each submitted audit requires a webhook to receive the result — the operation doesn't need (and shouldn't) poll for status. Deliveries are signed and automatically retried if your server is down (up to 6 attempts). Technical details, endpoints, and code examples in Enterprise auditing API.
Use the agent's external identifier field with the same ID as your telephony system. That way, per-agent metrics match 1:1 with your internal reports.
What do I need to get started
- Active enterprise plan with an organization configured;
- A technical contact to generate the key and configure the webhook;
- Access to the recordings (public URL or files for upload).
If your operation has high volume or specific requirements, talk to sales — the custom plan covers scenarios outside the standard.
FAQ
Is the module available on individual plans?
No — it's an enterprise-context feature, managed by the organization and its API keys.
Who can create integration keys?
OWNER and ADMIN of the organization, in the audit dashboard. There are up to 10 active keys, each with its own scopes.
My recordings don't have a public URL. What now?
Use the upload flow: the API returns an upload URL valid for 1 hour, you upload the file, and create the audit referencing that upload.
How do I receive the results?
By webhook, mandatory for each audit. Signed deliveries (HMAC) with automatic redelivery.
Related articles
Didn't resolve? Open a ticket — our team responds quickly.