Log Voice Agent calls
Subscribe to webhooks to capture what happened on every AIVA call — from basic call data to detailed conversation outcomes and AI-generated content.
AIVA calls generate webhook events just like human-handled calls do. Depending on what your integration needs to log, you have two approaches — and you can use both at the same time.
Subscribe to the regular call webhook events. AIVA-handled calls appear in the same stream as human calls, with standard call data — direction, duration, timestamps, recording URL, and so on. Use these if you already handle call events and just want AIVA calls included.
call.created call.ended transcription.created summary.created ...
Subscribe to AI Voice Agent webhook events to get a dedicated Voice Agent object with AIVA-specific data: session ID, escalation details, call end reason, and answers to intake questions collected during the call.
ai_voice_agent.started ai_voice_agent.ended ai_voice_agent.escalated ai_voice_agent.summary ...
Think about what you actually need to store. If you're logging calls for basic reporting — duration, direction, outcome — standard call events are enough. If you want to know whether the call was escalated, why it ended, or what the caller said during the intake flow, subscribe to the AIVA-specific events.
Here are simple ways to think about:
- Call duration, recording, direction, basic outcome → standard call events
- Whether AIVA answered, escalated, or the caller hung up, and why →
ai_voice_agent.endedandai_voice_agent.escalated - Intake answers collected during the conversation →
ai_voice_agent.summary - Post-call summary, transcript, sentiment, action items → Conversation Intelligence events (requires AI Assist)
Conversation intelligence events
AIVA calls also produce Conversation Intelligence events — the same AI-generated content that AI Assist generates for human-handled calls. This means you can receive post-call summaries, transcriptions, sentiment analysis, key topics, and action items for every AIVA call, automatically.They arrive on a different event stream and carry a different object shape. See the Conversation Intelligence API reference for the full list of events and attributes.
Use
ai_voice_agent_session_idto correlate events
All four AIVA events for the same call share the sameai_voice_agent_session_id. Use it to join events together when building a full picture of a call across your system.
Updated 5 days ago