This is expected behavior with Vapi right now. The usual solution is to save progress outside Vapi after each step (current step, answers, flags), then inject that state back into the prompt or metadata when the user calls again so the assistant resumes instead of restarting. Prompts should be step-aware and able to skip completed sections cleanly. Quick question: do you already persist a user or call identifier that you can use to reliably rehydrate state on the next call? @Sree