Merge remote-tracking branch 'origin/main' into fern/update-api-specs

Author: fern-api[bot]

fern/changelog/2025-02-20.mdx

@@ -0,0 +1,25 @@
+## What's New
+1. **Configure 16 text normalization processors in [FormatPlan](https://api.vapi.ai/api#:~:text=FormatPlan)**: You can now control how text is transcribed and spoken for currency, dates, etc. by setting the `formattersEnabled` array in `Assistant.voice.chunkPlan.formatPlan` (not specifying `formattersEnabled` defaults to all formatters being enabled). See all available formatters in the [FormatPlan.formattersEnabled reference](https://api.vapi.ai/api#:~:text=FormatPlan).
+
+2. **Deepgram [Keyterm Prompting](https://developers.deepgram.com/docs/keyterm)**: The `keyterm` array in [DeepgramTranscriber](https://api.vapi.ai/api#:~:text=DeepgramTranscriber) implements Deepgram's [Keyterm Prompting](https://developers.deepgram.com/docs/keyterm) technology, boosting recall for domain-specific terminology. Compared to the existing `keywords` field:  
+
+| Feature          | `keywords`         | `keyterm`          |
+|------------------|--------------------|--------------------|
+| Recall Boost     | 15-20%             | Up to 90%          |  
+| Format           | Word:Weight        | Raw phrases        |
+| Use Case         | General vocabulary | Critical terms     |
+
+You should reserve `keyterm` for compliance-sensitive terms like medical codes while using `keywords` for proper nouns / brand names.
+
+3. **Subscription usage tracking improvements**: The `minutesUsedNextResetAt` timestamp now appears in all subscription tiers (not just enterprise), exposed at `subscription.minutesUsedNextResetAt` for predictable billing cycle integration. Combine with existing `minutesUsed` and `minutesIncluded` metrics to build custom usage dashboards, regardless of subscription tier.
+
+4. **Neuphonic voice synthesis**: You can now configure Neuphonic as a voice provider with `Assistant.voice[provider="neuphonic"]`. Handle appropriate errors with `pipeline-error-neuphonic-voice-failed`. Test latency thresholds as Neuphonic requires 200ms additional processing time compared to ElevenLabs.
+
+<Frame caption="Neuphonic Voice Synthesis">
+    <img src="../static/images/changelog/neuphonic.png" alt="Neuphonic Voice Synthesis" />
+</Frame>
+
+5. **Support for pre-transfer announcements in [ClientInboundMessageTransfer](https://api.vapi.ai/api#:~:text=ClientInboundMessageTransfer)**: The `content` field in `ClientInboundMessageTransfer` now supports pre-transfer announcements ("Connecting you to billing...") before SIP/number routing. Implement via WebSocket messages using type: "transfer" with destination object.
+
+### Deprecation Notice  
+<Warning>**OrgWithOrgUser** is now deprecated, and impacts endpoints returning organization-user composites. This has been replaced with separate [`Org`](https://api.vapi.ai/api#:~:text=Org) and [`User`](https://api.vapi.ai/api#:~:text=User) schemas for better clarity and consistency.</Warning>

fern/static/images/changelog/neuphonic.png

@@ -10,9 +10,11 @@ slug: voice-fallback-plan
 
 ## Introduction
 
-By default, if an assistant's primary voice experiences any failure, Vapi will automatically attempt to use other available voices to continue the call. While this ensures call continuity, you might want more control over which specific voices are used as fallbacks.
+Voice fallback plans give you the ability to continue your call in the event that your primary voice fails. Your assistant will sequentially fallback to only the voices you configure within your plan, in the exact order you specify. 
 
-Fallback plans give you precise control over the fallback sequence. Your assistant will sequentially fallback to only the voices you configure within your plan, in the exact order you specify. 
+<Note>
+  Without a fallback plan configured, your call will end with an error in the event that your chosen voice provider fails.
+</Note>
 
 ## How It Works
 
@@ -22,10 +24,6 @@ When a voice failure occurs, Vapi will:
   - Switch to the first fallback voice in your plan
   - Continue through your specified list if subsequent failures occur
   - Terminate only if all voices in your plan have failed
-3. If no custom fallback plan is configured:
-  - Automatically switch to other available voices
-  - Continue attempting different voices
-  - Terminate only if all available voices have failed
 
 ## Configuration
 
@@ -54,25 +52,11 @@ Add the `fallbackPlan` property to your assistant's voice configuration, and spe
 }
 ```
 
-Although **not recommended**, you may choose to disable the default fallback behavior by providing an empty list of voices in your fallback plan:
-
-```json
-{
-  "voice": {
-    "provider": "openai",
-    "voiceId": "shimmer",
-    "fallbackPlan": {
-        "voices": []
-    }
-  }
-}
-```
-
 ## Best practices
 
 - Use <b>different providers</b> for your fallback voices to protect against provider-wide outages.
 - Select voices with **similar characteristics** (tone, accent, gender) to maintain consistency in the user experience.
 
 ## How will pricing work?
 
-There is no change to the pricing of the voices. Your call will not incur any extra fees while using fallback voices, and you will be able to see the cost for each voice in your end-of-call report.
+There is no change to the pricing of the voices. Your call will not incur any extra fees while using fallback voices, and you will be able to see the cost for each voice in your end-of-call report.