Update call-forwarding.mdx

Author: sahilsuman933

call-forwarding.mdx

@@ -158,4 +158,104 @@ Use the system prompt to guide the assistant on when to utilize each forwarding
 - Ensure you have written the function description properly to indicate where you want to forward the call
 - Test the call forwarding setup thoroughly to confirm its functionality.
 
-By following these guidelines and utilizing the `transferCall` tool, you can effectively manage call routing and provide a seamless experience for your users.
+## Call Transfers Mode
+
+Vapi supports two types of call transfers:
+
+1. **Blind Transfer** (default): Directly transfers the call to another agent without providing any prior information to the recipient.
+2. **Warm Transfer**: Transfers the call to another agent after providing context about the call. The context can be either a full transcript or a summary, based on your configuration.
+
+### Warm Transfer
+
+To implement a warm transfer, add a `transferPlan` object to the `transferCall` tool syntax and specify the transfer mode.
+
+#### Modes of Warm Transfer
+
+##### 1. Warm Transfer with Summary
+
+In this mode, Vapi provides a summary of the call to the recipient before transferring.
+
+* **Configuration:**
+   * Set the `mode` to `"warm-transfer-with-summary"`.
+   * Define a `summaryPlan` specifying how the summary should be generated.
+   * Use the `{{transcript}}` variable to include the call transcript.
+
+* **Example:**
+
+```json
+"transferPlan": {
+  "mode": "warm-transfer-with-summary",
+  "summaryPlan": {
+    "enabled": true,
+    "messages": [
+      {
+        "role": "system",
+        "content": "Please provide a summary of the call."
+      },
+      {
+        "role": "user",
+        "content": "Here is the transcript:\n\n{{transcript}}\n\n"
+      }
+    ]
+  }
+}
+```
+
+##### 2. Warm Transfer with Message
+
+In this mode, Vapi delivers a custom static message to the recipient before transferring the call.
+
+* **Configuration:**
+   * Set the `mode` to `"warm-transfer-with-message"`.
+   * Provide the custom message in the `message` property.
+   * Note that the `{{transcript}}` variable is not available in this mode.
+
+* **Example:**
+
+```json
+"transferPlan": {
+  "mode": "warm-transfer-with-message",
+  "message": "Hey, this call has been forwarded through Vapi."
+}
+```
+
+#### Complete Example
+
+Here is a full example of a `transferCall` payload using the warm transfer with summary mode:
+
+```json
+{
+  "type": "transferCall",
+  "messages": [
+    {
+      "type": "request-start",
+      "content": "I'll transfer you to someone who can help."
+    }
+  ],
+  "destinations": [
+    {
+      "type": "number",
+      "number": "+918936850777",
+      "description": "Transfer the call",
+      "transferPlan": {
+        "mode": "warm-transfer-with-summary",
+        "summaryPlan": {
+          "enabled": true,
+          "messages": [
+            {
+              "role": "system",
+              "content": "Please provide a summary of the call."
+            },
+            {
+              "role": "user",
+              "content": "Here is the transcript:\n\n{{transcript}}\n\n"
+            }
+          ]
+        }
+      }
+    }
+  ]
+}
+```
+
+**Note:** In all warm transfer modes, the `{{transcript}}` variable contains the full transcript of the call and can be used within the `summaryPlan`.