Usage and Call Statistics

Call Statistics shows the voice activity behind your operations and billing. Use it to understand call volume, failed calls, answer rates, trends, and exports. Pair it with Billing when you need to reconcile usage to charges.

What You Can See

The Call Statistics page summarizes your call activity for the active customer. Depending on filters and date range, it can show aggregate statistics, detailed call records, and trend data.

Common questions it answers:

• How many calls did we send or receive?
• Which calls failed?
• Did traffic increase during a specific time window?
• Which of our trunks handled a call? (shown on the Trunk column)
• Can we export records for audit or finance?

If the page is missing or empty, confirm your role has cdrs:read.

Statistics, Details, Trends, and Export

Use the views together:

• Statistics show the high-level picture: volume, outcomes, and performance.
• Details show individual call records.
• Trends show how traffic changes over time.
• Export gives you a CSV for offline analysis, reconciliation, or support tickets.

Start broad with statistics, narrow down with details, then export when you need evidence.

Exporting Call Records

On Call Statistics → CDR Records, set the date range and filters, then choose Export CSV. The export runs in the background — you can keep working or leave the page — and when you are signed in to the portal we email you when it is ready.

A line under the button follows your latest export:

• Waiting to start — the export is queued.
• Gathering calls — your calls are being collected.
• Preparing file — the file is being put together.
• Ready · Download — the file is ready.
• Failed · Try again — the export stopped; the reason is shown in Your exports.

Your exports (next to Export CSV) lists the exports you started for this account in the last 30 days, with one action each: Download, Try again, or Run again for an expired file. The email carries two links: a direct download that works for 72 hours, and Open in WARP, which works for as long as the file is kept (7 days). Exports you started are visible only to you, and only while this account is active.

Limits: one export can cover up to 93 days, and an account can have up to 3 exports in progress at once. The file is a plain CSV with the same 27 columns as before; it opens directly in Excel and Numbers.

Exporting with the API

GET /v1/cdr/export (scope cdrs:read) queues an export and returns 202 with a job_id. Poll GET /v1/cdr/export/jobs/{job_id} until status is done, then download from the returned url (valid for 24 hours; poll again for a fresh one). Exports started with an API key are not emailed and don't appear in Your exports — the integration polls for the file. Exports started through a connected app (such as a Claude or ChatGPT connection) are not emailed either, but they do appear in Your exports when you sign in to the portal. The same limits apply: a range over 93 days returns 400 VALIDATION_ERROR, and a fourth export in progress returns 429 RATE_LIMITED.

Reading Failed Calls

For failed calls, collect enough context to separate routing, capacity, and downstream issues:

• Direction: inbound or outbound.
• Timestamp with timezone.
• Calling number and called number.
• Trunk name (your trunk group that handled the call — blank on older inbound rows recorded before trunk capture).
• SIP status code if available.
• Whether the issue was setup, audio, DTMF, or disconnect.

A burst of 503 responses can indicate CPS back-pressure. Calls that never appear in CDRs may not have reached WARP, or they may have been blocked before normal call handling. Calls that appear with unexpected status codes may need trunk or routing review.

Reconciling Usage to Billing

Usage and billing are related but not identical views.

• Call Statistics shows the activity.
• The billing ledger shows the account transactions created from usage, payments, credits, and recurring charges.
• Invoices summarize a billing period.

If an invoice looks high, start with Call Statistics for the period, then compare the ledger entries and invoice. If you contact support, include the invoice ID, date range, exported CDRs if available, and the specific line or charge you are questioning.

Scopes and API Reference

Call statistics require cdrs:read:

• GET /v1/cdr/statistics
• GET /v1/cdr/details
• GET /v1/cdr/trends
• GET /v1/cdr/export

Dashboard analytics may require analytics:read:

• GET /v1/dashboard/stats

Billing reconciliation requires billing:read:

• GET /v1/billing/ledger
• GET /v1/invoices
• GET /v1/invoices/:id

When to Ask Buzz

Ask Buzz when you want a quick explanation of a metric, a failed-call pattern, or which records to export. Buzz can help connect a call-statistics question to trunks, numbers, and billing, but it uses your scopes. If you do not have cdrs:read, ask a customer admin to update your role or have someone with access export the records.