Skip to content

fix: update legacy voice migration pricing wording #903

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vapi-tasker merged 1 commit into from
Jan 30, 2026
Merged

fix: update legacy voice migration pricing wording #903

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions fern/providers/voice/vapi-voices/legacy-migration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,17 +48,13 @@ We've selected replacement voices from ElevenLabs using their voice matching too

<AccordionGroup>
<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 are from the same provider at the same pricing.
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>

<Accordion title="What happens if I don't switch by March 1?">
Any assistants still using legacy voices after March 1, 2026 will be automatically switched to the Option 1 (default fallback) voice shown in the table above.
</Accordion>

<Accordion title="Will my pricing change?">
Replacement voices were chosen at the same pricing.
</Accordion>

<Accordion title="How do I switch my voice now?">
You can switch your assistant's voice in two ways:

Expand Down
Loading