docs: document HANDOFF_TO response metric for voice handoffs#461
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document HANDOFF_TO response metric for voice handoffs#461mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a May 2026 release note explaining that voice handoffs now populate the
HANDOFF_TOresponse metric with the handoff destination, alongside the existingHANDOFF_REASON.Changes
releases/notes/26.05.mdxwith a new accordion entry describing theHANDOFF_TOmetric, when it is emitted, and how to enable it as a response metric.Context
The voice agent previously emitted only
HANDOFF_REASONon handoff call outcomes, so the destination configured on the handoff (for example,FRONT_DESK) was silently dropped before reaching dashboards and the Conversations API. Customers who had already enabledHANDOFF_TOas a response metric will now start seeing it populated, which is worth flagging in the release notes.HANDOFF_TOis already referenced in Metrics, API keys, and the Conversations API, so no further reference-doc changes are needed.