Skip to content

Adding transcriber auto fallback logic to docs#1016

Open
sagar-vapi wants to merge 1 commit intomainfrom
sagar/add-transcriber-autofallback
Open

Adding transcriber auto fallback logic to docs#1016
sagar-vapi wants to merge 1 commit intomainfrom
sagar/add-transcriber-autofallback

Conversation

@sagar-vapi
Copy link
Copy Markdown
Contributor

@sagar-vapi sagar-vapi commented Apr 9, 2026

Description

Recent assistant property added to let vapi decide transcriber fallback & not let call fail

Tested, running locally.

Screenshot 2026-04-08 at 6 25 31 PM

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 9, 2026

- For **HIPAA/PCI compliance**, ensure all fallbacks are compliant providers (Deepgram or Azure).
- For **HIPAA/PCI compliance**, ensure all fallbacks are compliant providers (Deepgram or Azure) and review data routing implications before enabling auto fallback.

## FAQ
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can add an endpointing question here, like what happens if my tranascriber has endpointing capabilities? -> if fallback happens it will fallback to heuristics endpointing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants