Voice Agent calls now record two additional system tags so teams can distinguish what happened during the latest Voice Agent conversation without reviewing recordings or reconstructing the result from life-log events.

Use the tags in call-log reporting, filters, exports, or downstream webhook/reporting workflows to answer whether the agent applied any collection tags and whether the caller disconnected while still speaking with the agent.

The applied-tag count also supports cleaner funnel analysis: a handover with collected data can be separated from an empty handover when no buyer was reached.

LAST_VOICE_AGENT_TAGS_APPLIED_COUNT — number of custom tags applied during the most recent Voice Agent conversation; 0 means none were applied.

HANGUP_DURING_VOICE_AGENT_CONVERSATION — true when the inbound caller disconnected while the Voice Agent step was still active; false when the Voice Agent conversation ended or handed over cleanly.

These tags describe platform-level Voice Agent processing state. They do not identify where a caller stopped inside an agent’s scripted conversation; use agent collection tags at handover when step-level reporting is needed.

Reporting teams can classify Voice Agent outcomes more accurately, audit collection-tag coverage, and isolate caller hangups during the agent conversation using structured call data.