refactor docs

Author: bryantanderson

fern/voice-fallback-plan.mdx

@@ -1,6 +1,6 @@
 ---
 title: Voice Fallback Plan
-subtitle: You can configure your assistants to fallback to other voices when your primary voice fails.
+subtitle: Configure fallback voices that activate automatically if your primary voice fails.
 slug: voice-fallback-plan
 ---
 
@@ -10,23 +10,28 @@ slug: voice-fallback-plan
 
 ## Introduction
 
-Prior to the addition of fallback plans, calls would terminate if an assistant's voice experienced any failure, regardless of whether the issue originated from the voice provider or Vapi.
+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.
 
-Fallback plans allow your assistant to continue the call in the scenario that your primary voice fails. Your assistant will sequentially fallback to the voices you configure within your plan, until there are no voices left. 
+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. 
 
 ## How It Works
 
 When a voice failure occurs, Vapi will:
 1. Detect the failure of the primary voice
-2. Automatically switch to the first fallback voice
-3. Continue through the list of fallback voices if subsequent failures occur
-4. Only terminate if the list of fallback voices has been exhausted, and all have failed
+2. If a custom fallback plan exists:
+  - 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
 
 Add the `fallbackPlan` property to your assistant's voice configuration, and specify the fallback voices within the `voices` property.
 - Please note that fallback voices must be valid JSON configurations, and not strings.
-- Also note that the order matters. Vapi will choose fallback voices starting from the beginning of the list.
+- The order matters. Vapi will choose fallback voices starting from the beginning of the list.
 
 ```json
 {
@@ -37,7 +42,7 @@ Add the `fallbackPlan` property to your assistant's voice configuration, and spe
         "voices": [
             {
                 "provider": "cartesia",
-                "voiceId": "248be419-c632-4f23-adf1-5324ed7dbf1d",
+                "voiceId": "248be419-c632-4f23-adf1-5324ed7dbf1d"
             },
             {
                 "provider": "playht",
@@ -49,10 +54,24 @@ 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.
+- Select voices with **similar characteristics** (tone, accent, gender) to maintain consistency in the user experience.
 
 ## How will pricing work?