Skip to main content

Release Notes: 2026-07-22 — Reporting — Call State Tags and Voice Agent Funnel

System call-state tags let you report Voice Agent and post-agent progress without recordings; Call Summary VA columns use the same signals.

D
Written by Denise Abdullah

Call State Tags: Report Voice Agent Progress Without Recordings

Released: July 22, 2026

Category: Enhancement

Location: Reporting → Call Log (tags / filters); Reporting → Call Summary → Voice Agent metrics

Why this matters

  • When calls are not recorded, ops still need to know how far a Voice Agent call got—and what happened after handover—using data on the call itself.

  • Call Summary Voice Agent columns are more accurate because they are driven from those same stage signals instead of thin post-call guesses.

What changed

System call-state tags on the call

  • Moja now writes positive stage tags during the call for the Voice Agent path, buyer/target path, and RTB attribution where applicable.

  • These are system tags on the call log—available for Call Log review, filtering, and reporting—without requiring a recording.

Tag reference

Tag

Meaning

LAST_VOICE_AGENT_ATTEMPTED

VA node entered

LAST_VOICE_AGENT_REACHED

VA actually connected

LAST_VOICE_AGENT_HANDOVER

Handover confirmed

LAST_VOICE_AGENT_FINISHED

VA finished (incl. after tool-call handover)

LAST_BUYER_ATTEMPTED / LAST_BUYER_REACHED

Buyer/target dial / answer

BUYER_FAILURE_REASON

Why buyer path failed (no bid, busy, no-answer, etc.)

LAST_RTB_GROUP / LAST_RTB_FORMULA + ping timing tags

RTB attribution

What you can answer with these tags

  • Did the Voice Agent get attempted / actually connect?

  • Did handover complete?

  • After the agent path, was a buyer attempted or connected?

  • If not, what failure class was recorded?

  • Which RTB group/formula was last in play (when RTB applies)?

Call Summary Voice Agent columns (built on the same tags)

  • VA Conn / VA No Conn and related % columns use the Voice Agent–eligible call set more consistently.

  • Post-agent outcomes split cleanly across: VA Buyer Conn, VA Buyer No Conn, VA No Buyer, VA Dropoff Before RTB, VA Empty Handover.

  • VA Buyer Conn % uses connected ÷ (connected + buyer no-connect + no buyer). Dropoff and Empty Handover stay out of that percentage.

  • VA No Buyer and related totals were corrected so No Buyer does not incorrectly stay at zero.

  • Column header tooltips explain each Voice Agent metric in product.

Where to find it / How to use it

  • Single-call / state reporting: Reporting → Call Log → open a call → review system tags (and Call Life for the timeline).

  • Use Call Log filters on call tags to build views such as “agent reached, no buyer connected.”

  • Rollup metrics: Reporting → Call Summary → Voice Agent columns; hover headers for definitions.

  • Calls from before these stage tags existed keep prior Call Summary behavior where tags were not present. New traffic after this release uses the tag-based funnel.

Important scope note for conversation steps

  • These system tags track platform stages (agent / handover / buyer / RTB), not every line inside the Voice Agent script.

  • In-script steps (for example ZIP check → silence vs invalid vs success) are still captured when your Voice Agent collects and hands over those fields as tags. Configure those collection tags on the agent if you need step-level reporting beyond platform stages.

Impact

  • Customers can report on Voice Agent and post-agent call state without relying on recordings.

  • Call Summary Voice Agent performance metrics are trustworthy enough for day-to-day ops.

  • Clearer separation of agent reach, handover, buyer attempt/connect, no buyer, and dropoff.

Did this answer your question?