Skip to content

Add New Vapi Voices section to legacy migration docs#955

Merged
betzlermeow merged 2 commits intomainfrom
tasker/DEVREL-518-add-new-vapi-voices-section
Feb 26, 2026
Merged

Add New Vapi Voices section to legacy migration docs#955
betzlermeow merged 2 commits intomainfrom
tasker/DEVREL-518-add-new-vapi-voices-section

Conversation

@betzlermeow
Copy link
Contributor

Description

  • Add a "New Vapi Voices" section to the legacy voice migration page (providers/voice/vapi-voices/legacy-migration)
  • Lists the new generation of Vapi Voices: Emma, Nico, Neil, Sagar, Kai, Clara, and Godfrey
  • Placed after the "What this means" section and before the "Replacement voice mapping" table
  • Clarifies that these new voices are separate from the automatic fallback replacements
  • Links to the Vapi Dashboard for previewing the voices

Resolves DEVREL-518

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work
  • Verify the "New Vapi Voices" section appears between "What this means" and "Replacement voice mapping"
  • Verify the Dashboard link works: https://dashboard.vapi.ai

Add a section introducing the new generation of Vapi Voices (Emma, Nico,
Neil, Sagar, Kai, Clara, Godfrey) to the legacy voice migration page.
This gives users migrating off legacy voices visibility into additional
voice options beyond the ElevenLabs replacement mappings.

Resolves DEVREL-518

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Relocated the New Vapi Voices section to appear after the replacement
voice mapping table and before the FAQs, per reviewer feedback.
Also updated 'listed below' to 'listed above' to match new position.

DEVREL-518
@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

@betzlermeow betzlermeow merged commit 6b1fb8c into main Feb 26, 2026
4 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant