@Dhruv This usually happens when there’s no fallback set for a failed transfer in Vapi.
If transfer fails, the call keeps ringing unless you handle transfer.failed / no-answer. Also, it starts a new convo because a new call session is triggered.
Make sure your fallback:
Handles failed transfer events
Routes back using the same conversationId
Resumes the active session (don’t create a new call)