Dear Vapi Support Team, We recently learned that several voices are being phased out and wanted to clarify expected behavior around legacy voice usage. While the voices page indicates that existing agents can continue operating, we’ve found that agents using legacy voices cannot have their base prompt updated. Could you please confirm whether this is an intentional limitation or a temporary issue? Clarifying this soon is important for us, as it affects client communications, roadmap planning, and our future use of the platform. We appreciate your guidance on how best to proceed. Best regards, Or

Hi Or, Thanks for reaching out and for outlining the impact this has on your planning. Yes, this behavior is intentional, not a temporary issue. The voices you’re referring to are part of a set of legacy voices that Vapi is in the process of phasing out (e.g., Harry, Paige, Spencer, Neha, Cole, Hana, Lily). As part of this transition: • Existing assistants using legacy voices may continue to operate for now • New assistants cannot be created with these voices • Updates to existing assistants (including base prompt updates) are not supported while the assistant is using a legacy voice • These voices will be fully retired in a future update (timeline not yet finalized) Because of this, there isn’t a workaround to continue updating prompts while keeping a legacy voice. To proceed with prompt or configuration changes, the assistant will need to be migrated to a supported (active) voice. You can review the currently supported voices here: [https://docs.vapi.ai/providers/voice/vapi-voices](https://docs.vapi.ai/providers/voice/vapi-voices) We understand this affects client communications and roadmap planning, and we appreciate the feedback. Best regards, Shaunak