Even for agents that already use a legacy voice, Vapi re-validates all agent properties on any update (including prompt changes). Since Kylie is now restricted, that validation fails and the agent can’t be saved or published there isn’t a partial grandfathering mechanism for voice-only fields. By closest allowed alternatively, I mean a currently supported Vapi voice with a similar tone, pacing, and prosody to Kylie (not the same voice, but the closest match available). If you have access to custom voices, we can also replicate Kylie’s style more closely that way. Happy to walk through the best option based on your use case. @pro1710