Outbound Call Then Cost Analytics
A 3-step recipe with Vapi. We can help you get access.
Recipe · 3 steps
Outbound Call Then Cost Analytics
with Vapi
Run an outbound call and then aggregate its cost and duration via analytics.
- Place the outbound call from the existing assistant and number.
- Read the call status and branch: loop while still active, continue to analytics once the call has ended.
- Query the analytics endpoint to aggregate total cost and call duration over the reporting window.
What you'll need to have ready
- apiToken: Vapi private API key used as a Bearer token.
- assistantId: The id of an existing assistant to run the call.
- phoneNumberId: The id of an existing phone number to place the call from.
- customerNumber: The destination phone number in E.164 format to dial.
- rangeStart: ISO 8601 start of the analytics reporting window.
- rangeEnd: ISO 8601 end of the analytics reporting window.
For your developer
Arazzo workflow vapi-ai:call-then-analytics, 3 operations: CallController_create → CallController_findOne → AnalyticsController_query. Specs on APIs.io.