I’ve dealt with similar VAPI issues before and can help you fix both. For email capture, it usually needs a smarter character-by-character flow with confirmation checks. For the busy case, it’s about how Twilio call statuses are mapped inside VAPI. Are you currently handling the transcription logic natively in VAPI or routing through Twilio first? @Madhavan