Transfer Failure Fallback Not Working – Bot Disconnects Instead of Booking Appointment
Abu Bakar Nisar
I’m currently testing the call transfer and call forwarding behavior in my voice bot and I’m running into an issue with the fallback handling when a transfer fails.
I have tried all available transfer options — blind transfer, warm transfer, and the experimental transfer method. In the experimental transfer configuration, I set the call ending flag to false. With this setup, the call itself does not end when the forwarding fails, which is good — however, the bot still gets disconnected and does not continue the conversation.
My requirement is that when call forwarding or transfer fails, the bot should remain active, continue the conversation, and move the caller into the appointment booking flow instead of disconnecting.
Right now, even though the call is not ended in the experimental setup, the bot drops off and does not resume control of the conversation.
Could you please guide me on how to properly implement a fallback so that after a failed transfer attempt, the bot continues the flow and proceeds with appointment booking? Step-by-step configuration guidance would be greatly appreciated.
Thank you for your support.
Best regards,
Abu Bakar