Per-agent scorecard

FeatureAIService
Shipped
July 22, 2026 at 5:19 PM UTC
Author
Kamo
Commit
eea25b9

What each agent actually did: conversations, how often a person had to take over and why, outreach outcomes including the ones held back, and what it cost. Every number is one the data can actually support. Three things are deliberately NOT here: - **No token totals.** They are real on the sync path and fabricated on the streaming one (content.length()/4), so any total is part invented. Cost answers the same question honestly, because it is null rather than guessed where the price is unknown. - **No resolution or deflection rate.** Nothing observes whether a conversation ended well, and 'no handoff occurred' is not evidence of success. - **No per-version message or handoff counts.** Those are not aggregated per version, and emitting 0 for them would be a fabrication rendered as a measurement - the precise failure this screen exists to avoid. Cost carries an explicit tracked flag and a null amount rather than 0 when nothing in the window was priced, so an org whose traffic predates pricing sees 'not recorded' instead of a confident $0.00. pricedCalls is the authority rather than the sum, so a genuine zero from priced free-tier calls still reads as tracked. Transcript prose is gated on VIEW_SALES_AGENT_TRANSCRIPTS separately from the counts - the model's summary of a specific visitor is conversation content, not a metric. Agents with no traffic return a structurally complete empty scorecard: an agent missing from the list reads as a bug, an agent present with zeros reads as the truth. parseHandoffArguments is now shared with the chat path rather than reimplemented, so the coercion of invented reasons to OTHER cannot drift between the two. Suite is 150 tests, green.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing