Skip to content

Commit 0ff8aca

Browse files
authored
Merge branch 'main' into structured-outputs-documentation
2 parents 78a0f5f + 7179d60 commit 0ff8aca

File tree

3 files changed

+17
-3
lines changed

3 files changed

+17
-3
lines changed

fern/changelog/2025-08-23.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
# Voicemail Detection Enhancements
2+
3+
1. **Voicemail Detection Enhancements**: You can now configure voicemail detection across providers with [`Assistant.voicemailDetection`](https://api.vapi.ai/api#:~:text=https://api.vapi.ai/api#:~:text=SessionPaginatedResponse-,Assistant,-AssistantPaginatedResponse), for example with [Vapi](https://api.vapi.ai/api#:~:text=VapiVoicemailDetectionPlan), [Google](https://api.vapi.ai/api#:~:text=GoogleVoicemailDetectionPlan), and [OpenAI](https://api.vapi.ai/api#:~:text=OpenAIVoicemailDetectionPlan).Each plan now supports a `type` property to select between:
4+
- `audio`: Native audio model detection (default)
5+
- `transcript`: ASR/transcript-based detection
6+
7+
2. **Fine-tuned control**: Under each voicemail detection plan, you can configure backoff plans and beep detection timing with [`Assistant.voicemailDetection["yourVoicemailDetectionPlan"].beepMaxAwaitSeconds`](https://api.vapi.ai/api#:~:text=https://api.vapi.ai/api#:~:text=VapiVoicemailDetectionPlan) for improved voicemail handling in automated calls.

fern/changelog/2025-08-25.mdx

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
1. **New Structured Output Endpoints**: You can now use [new APIs for structured outputs](https://docs.vapi.ai/api-reference/calls/list#:~:text=Delete%20Logs-,Structured%20Outputs,-GET) to define, extract, and manage structured data from conversations.
2+
3+
2. **Configure Structured Output Resources**: You can now define reusable structured data extraction templates, including:
4+
- **Custom JSON Schema**: Specify the exact structure and validation rules for extracted data using full JSON Schema support (objects, arrays, enums, validation constraints, and more).
5+
- **Model Selection**: Choose the LLM (OpenAI, Anthropic, Google, or custom) for extraction, or provide custom system/user prompts with Liquid templating for advanced scenarios.
6+
- **Context Linking**: Link structured outputs to specific workflows or assistants for context-aware extraction.
7+
- **Metadata**: Track creation/update timestamps, org linkage, and provide rich descriptions for each structured output.
8+
9+
3. **Assistant Transfer Improvements**: You can now include an optional `name` property to better identify and manage your transfer assistants.

fern/ivr-navigation.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,13 +18,11 @@ Some IVRs buffer audio or expect digits at a slower pace. Sending digits too qui
1818

1919
Provider-specific pause characters
2020

21-
- **Twilio / Telnyx**: Use `w` for a 0.5s pause, `W` for a 1s pause. Example: `1w2w3W4#`
21+
- **Twilio / Telny / Vapi Numbers / BYOK SIP**: Use `w` for a 0.5s pause, `W` for a 1s pause. Example: `1w2w3W4#`
2222
- **Vonage**: Use `p` for a 0.5s pause. Example: `1p2p3#`
2323

2424
Start with 0.5s pauses and increase only if digits are still missed.
2525

26-
<Warning>Vapi phone numbers and BYOK SIP do not support pause characters at this time.</Warning>
27-
2826
### 2. Give menus time to finish before responding
2927

3028
IVR menus often speak slowly and include longer silences than typical user speech. If your assistant responds too quickly, it may send tones before the IVR has finished listing options and there's a chance that is not ready to receive inputs.

0 commit comments

Comments
 (0)