Hi Retell Support,
We're using warm transfers, and we’ve noticed that all failed transfers return the same generic tool result:
{"status":"Transfer failed due to an error.. Please inform the customer that the transfer did not go through and offer to try again or assist them directly."}
This happens whether the call is declined, reaches voicemail, or fails due to a technical issue.
Issue:
The main agent has no way to know why the transfer failed.
We can't differentiate between voicemail, decline, or error in real time or in post-call analysis.
This limits our ability to train agents and provide accurate responses to customers.
Request:
Could you provide a way to:
Distinguish between failure types (declined, voicemail, error, etc.)
Include the reason in the tool result or via webhook metadata, so agents can respond accordingly.
This would help improve agent behavior and overall call experience.
Thanks!Hi Retell Support,
We're using warm transfers, and we’ve noticed that all failed transfers return the same generic tool result:
{"status":"Transfer failed due to an error.. Please inform the customer that the transfer did not go through and offer to try again or assist them directly."}
This happens whether the call is declined, reaches voicemail, or fails due to a technical issue.
Issue:
The main agent has no way to know why the transfer failed.
We can't differentiate between voicemail, decline, or error in real time or in post-call analysis.
This limits our ability to train agents and provide accurate responses to customers.
Request:
Could you provide a way to:
Distinguish between failure types (declined, voicemail, error, etc.)
Include the reason in the tool result or via webhook metadata, so agents can respond accordingly.
This would help improve agent behavior and overall call experience.
Thanks!