https://vapi.ai/ logo
Join Discord
Powered by
URGENT | Request to Enable warm-transfer-say-summa...
# support
m
Hi Vapi Team, We’re building an inbound virtual receptionist that requires native warm transfer using: 
transferPlan.mode = warm-transfer-say-summary
When attempting to configure a transferCall tool with:
Copy code
"type": "transferCall",
  "destinations": [
    { "type": "number", "number": "+15093061243" }
  ],
  "transferPlan": {
    "mode": "warm-transfer-say-summary",
    "summaryPlan": {
      "enabled": true
    }
  }
}
we receive the following API error: 
property transferPlan should not exist
When creating a persistent transferCall tool When embedding the tool inline under assistant.model.tools When attempting partial_update on the assistant It appears our organization schema does not currently expose transferPlan support on transferCall. Could you please enable native warm transfer (warm-transfer-say-summary) for our organization? This feature is required for a professional inbound call screening workflow where the sales representative receives a spoken summary before the caller is bridged. Thank you.
c
Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team
v
To resolve the error, place the 
transferPlan
inside the destination object and use the correct mode name. Here’s an example configuration for a warm transfer with summary:
Copy code
json
{
  "type": "transferCall",
  "destinations": [
    {
      "type": "number",
      "number": "+15093061243",
      "transferPlan": {
        "mode": "warm-transfer-with-summary",
        "summaryPlan": {
          "enabled": true
        }
      }
    }
  ]
}
This should enable the spoken summary before bridging the call, provided your account supports this feature. For more details, see the [Vapi call forwarding documentation](https://docs.vapi.ai/call-forwarding). Source: - [Vapi Call Forwarding Documentation](https://docs.vapi.ai/call-forwarding)
j
It looks like your org hasn’t been enabled for transferPlan yet, which is why the API keeps rejecting it and blocking your warm handoff with summary. I’ve seen this before it usually needs a backend feature flag activated plus confirmation your assistant model supports pre-bridge summaries. Once that’s live, we can fine-tune the summary so reps get a clean 10–15 second context before pickup. Are you on a shared or dedicated Vapi environment right now? @mos
c
HI Please correct:
Copy code
json
{
  "type": "transferCall",
  "destinations": [
    {
      "type": "number",
      "number": "+15093061243",
      "transferPlan": {
        "mode": "warm-transfer-say-summary",
        "summaryPlan": {
          "enabled": true
        }
      }
    }
  ]
}
The only change: move 
transferPlan
inside the destination object, as a sibling of 
type
and 
number
. This makes sense architecturally; each destination can have its own transfer plan (e.g., you might warm-transfer to one number but blind-transfer to another). available transfer modes for reference: • 
blind-transfer
(default) • 
blind-transfer-add-summary-to-sip-header
• 
warm-transfer-say-message
• 
warm-transfer-say-summary
← what you want • 
warm-transfer-twiml
• 
warm-transfer-wait-for-operator-to-speak-first-and-then-say-message
• 
warm-transfer-wait-for-operator-to-speak-first-and-then-say-summary
PreviousNext
Powered by