From 8efb6615946a6591f4c5e49650e8b142213437f9 Mon Sep 17 00:00:00 2001
From: Vapi Tasker <tasker@vapi.ai>
Date: Tue, 3 Feb 2026 00:37:18 +0000
Subject: [PATCH] docs: add FAQ explaining why legacy voices are being phased
 out

---
 fern/providers/voice/vapi-voices/legacy-migration.mdx | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/fern/providers/voice/vapi-voices/legacy-migration.mdx b/fern/providers/voice/vapi-voices/legacy-migration.mdx
index e302ed4c1..60e603baf 100644
--- a/fern/providers/voice/vapi-voices/legacy-migration.mdx
+++ b/fern/providers/voice/vapi-voices/legacy-migration.mdx
@@ -70,6 +70,10 @@ We've selected replacement voices from ElevenLabs using their voice matching too
 ## FAQs
 
 <AccordionGroup>
+  <Accordion title="Why are these voices being phased out?">
+    We're updating our voice library to ensure all voices meet our current licensing and consent standards.
+  </Accordion>
+
   <Accordion title="How were the replacement voices selected?">
     We used ElevenLabs' voice matching tool to find the most appropriate replacements for each legacy voice based on tone, style, and characteristics. Replacements should not change your pricing.
   </Accordion>