Call Transfers going to incorrect Number
# support
h
Today we had a call transfer going to incorrect number. There was no call transfer instruction in that particular prompts, and that that number it went to did not exist in the prompts at all. Call ID: 92f531d3-91ba-47e9-9285-a6cc55678d1a Yesterday we had many calls on another live assistant going to our test mobile number, instead of the correct client number even though we definitely had the correct numbers published in the prompts. This is an issue as client is missing out on bookings. To resolve this, I had to republish the same prompts multiple times and reattach to the phone number. Shouldn't be happening though as prompts were already correct. Call ID: db627afd-abec-437f-b07a-f717c68837f7 Call ID: fdbaf926-6fdc-468b-9bf6-87c966553ef7 Call ID: 17f5893f-c97a-4b84-8078-fe6cb4bbd6c6 Call ID: 110169ab-e683-4d7d-ad36-3da01cf0a946 Call ID: 91dae9f0-13dd-47cc-980e-3831a1c0b714 Call ID: de5cdee3-e312-418a-9e29-b1f7de68d9cb Call ID: 0969dd01-617b-4166-986c-ddedfb26cd05 Call ID: 5fd8ba7f-7bf0-4734-b20e-31004094a577 Call ID: 89a0873c-4c50-4538-a563-fe3f0ed06ea4 Call ID: 50e0b904-a34b-47ca-983b-2542a1b29ea7 Call ID: e2c35654-aa09-44c6-9d1e-5da2daa97ee7
v
* Unintended triggers: There might be conditions that trigger the
transferCall
function unintentionally, even if you don't see explicit transfer instructions. * Knowledge base issues: A knowledge base issue could be causing user input to be misinterpreted, potentially triggering transfers. * Silent transfer configuration: Check if
assistantOverrides
are set correctly to prevent unwanted transfer messages. ## SIP Configuration * SIP REFER handling: Vapi uses SIP REFER to transfer calls. Confirm that your system is properly handling these messages. * SIP server configuration: Ensure your SIP server or PBX is configured to accept calls from Vapi's servers. Is there any specific aspect of the call transfer issue you'd like me to elaborate on further? Sources: - [Troubleshooting call transfers going to incorrect numbers in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334225751326720031) - [How prompts influence call transfers in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336989548357353524) - [Why calls are going to test mobile number instead of correct client number in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335869152535121960) - [Call routing mechanisms in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336713212233515089) - [Call routing configuration options in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339614362742165606)
Hi there! 👋 I understand you're experiencing issues with call transfers going to incorrect numbers, which is definitely frustrating especially when it's affecting client bookings. I'm unable to analyze the specific call IDs you've shared or verify the exact content of your prompts. However, I can help troubleshoot the general issue of incorrect call transfers in Vapi based on information I've found. Here are some potential causes and troubleshooting steps for your call transfer issues: ## Initial Checks and Configuration Verification * Verify the forwarding number: Ensure that the forwarding number is correctly entered and in the proper E.164 format (e.g., +15558675309). [According to troubleshooting information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335869152535121960), incorrect formatting can cause routing issues. * Check for hardcoded numbers: There might be hardcoded numbers within the application code or Twilio's TwiML Bin that could be causing the redirection. * Assistant association: Verify that the Twilio number has the VAPI inbound URL configured and that an assistant is properly associated with the phone number. ## Potential Workarounds (That Align With Your Solution) Your solution of republishing prompts and reattaching the phone number is actually a known workaround! [According to troubleshooting information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339614362742165606), these steps can help resolve call transfer issues: * Republish prompts and reattach phone number: This refreshes the configuration. * Twilio routing region: Consider changing the Twilio routing region to US. * Disable call control server message: Try disabling the call control server message on the assistant. ## Prompt and Transfer Tool Issues
h
@Shubham Bajaj we've just had the same thing happen again to the AI from yesterday Call ID: 2163dc06-e7de-467e-8e9a-a1ef992275b0
k
looking into it.
Hey Liv, I checked your calls, and your assistant is transferring to the destination, which is part of your assistant's forwarding phone number. That's why your calls are going there. Regarding you, your prompt doesn't have any search instructions. It's coming from your prompt alone. I suggest you rework your prompt and look for transfer call functions. You should remove unexpected transfer calls that originate from your assistant by your prompting/evaluation.
h
@Shubham Bajaj I have set up the call transfer tool. Initially I set up one transfer tool per department, however looks like you can only attach one call transfer tool per AI. So I then setup one call transfer tool with the multiple destination phone numbers. Unfortunately, this is not working. It is only transferring to the first phone number on the list. The AI is following the prompts, just executes the wrong phone number transfer. Tool ID: 7c371b5b-0f94-4bf1-bca6-d6e7248c2a11 Assistant ID: c171c4b6-8043-4b94-98ac-bc9a154618d5 Call IDs: b512f31a-3cb6-45a1-bdcb-73ccae2146f2 c4cfa1bc-b937-4208-b51d-ac6825216993 60773044-eac0-4332-9ce7-042d8526171b
k
Hi, checking if this is resolved/solved for you?
h
@Shubham Bajaj no this is not solved. Our understanding is that the tool does not allow for multiple phone destinations though.
k
You can have the option for multiple destinations, but you can only transfer to a single destination as of now.
2 Views