Skip to main content
A call is the voice connection. A run records one execution of an agent. Phone calls, browser tests, and campaign calls produce run records. Text tests can also create runs without an audio recording.

​
Review a conversation

Open Conversations to find recent activity, or open an agent’s Runs view. Select a run to review the available transcript, audio, extracted data, analysis, and integration results. Some results appear after the call ends. A recording or transcript can be unavailable when a call did not connect or when processing has not completed. Treat missing artifact URLs as unavailable rather than constructing your own URL.

​
Interpret run state

The run API uses state and is_completed: Completion does not by itself mean that the caller answered or that your business task succeeded. Review call disposition, available logs, and extracted results. Provider call statuses and campaign statuses have their own meanings.

​
Available results

Cost estimates depend on the selected services and available pricing information. Compare them with provider billing when reconciling usage. For applications, use list runs and get a run. Store artifact URLs securely because they can grant access to call content.