Tracking voice AI costs: reconcile calls, holds and provider invoices

To understand a voice AI bill, connect each expense to a resource or a call. Start with one example you can explain, then expand to a daily or monthly total. A dashboard total without that mapping makes it difficult to distinguish normal usage, unused resources and an accounting problem.

Keep the amounts distinct

Do not add the reservation and the settled charge as if both were purchases. Also do not interpret an unavailable external cost as zero.

Create a reconciliation row

For each representative call, record its identifier, start time, assistant version, voice configuration, funding arrangement, connected duration and outcome. Add provider and carrier identifiers when available. Keep raw credentials and unnecessary caller information out of the worksheet.

The following is a suggested local accounting record, not a Burki API request:

Call reference:
Configuration and funding mode:
Estimated / reserved / settled / released:
Direct provider expense:
Direct carrier expense:
Other telephone legs:
Verified useful outcome:
Unresolved discrepancy:

A call can be technically completed without producing the intended business result. Keep that distinction when calculating cost per successful task.

Investigate an unusual call

Compare it with a similar normal call. Check duration, assistant speech length, repeated model turns, tool retries and transfer legs. Inspect whether the call remained connected after the useful conversation ended.

Generated speech and heard speech may differ if the caller interrupted or playback failed. Use the provider's usage units and the runtime evidence rather than assuming the transcript alone explains the bill.

If settlement is delayed, record it as unresolved and check the final receipt before drawing a conclusion. Preserve the call identifier and time window for support; a screenshot of the total balance is rarely sufficient.

Reconcile the month beyond calls

Inventory rented numbers and other recurring resources. Assign an owner and purpose to each. A resource with no calls may still be legitimately retained for routing or migration, so verify dependencies before cancellation.

Combine platform statements with direct provider and carrier statements for the same billing period. Account for credits and time-zone boundaries. Avoid double counting a charge collected by the platform and the same amount shown as informational provider usage.

Make improvements measurable

Fix unused resources and repeated work first. Then change one setting at a time and compare the same caller scenarios. Track human recovery as well as provider expense; reducing the bill while increasing failed requests is not necessarily an improvement.

Use Burki's current pricing for the applicable tariffs and BYO guidance for direct-account responsibilities. This process does not assume that every suggested worksheet field or export exists as a dashboard feature; it describes the evidence you need to explain your costs.