Hey Vapi team! I have an issue with the customization of the message that is announced to the user before transferring the call. - I'm using a dynamic assistant and I'm including the 'transfer-destination-request' into 'serverMessages' when responding to the 'assistant-request' message - I'm providing a placeholder 'transferCall' tool when configuring the assistant - I'm responding with the destination config to the 'transfer-destination-request' message - All other destination config fields are applied correctly except of the 'message' field - I have 'number', 'callerId', 'transferPlan' working as expected. but the 'message' field is ignored (both custom message and empty string). The assistant just says the default 'Transferring the call now' phrase here are several call ids: c2de90d0-f226-4940-88dd-959033e749a7 25977fac-d29c-4ba1-a1c8-5582c2ab317a 6949badf-6724-476e-9445-ed93031623a5 7de30ba1-0a7e-43da-b3ce-81933aad6d91 assistant config looks like this:

{
  "name": "Outbound phone call",
  "model": {
    "url": "https://***/webhooks/vapi/custom-llm",
    "model": "gpt-4o",
    "tools": [
      {
        "type": "transferCall",
        "function": {
          "name": "transferCall"
        },
        "destinations": []
      },
      {
        "type": "endCall",
        "function": {
          "name": "endCall"
        }
      }
    ],
    "provider": "custom-llm",
    "maxTokens": 250,
    "temperature": 0.7,
    "urlRequestMetadataEnabled": true
  },
  "voice": {
    "voiceId": "joseph",
    "provider": "11labs"
  },
  "serverMessages": [
    "end-of-call-report",
    "hang",
    "status-update",
    "speech-update",
    "conversation-update",
    "tool-calls",
    "transfer-destination-request"
  ]
}

And here is my response to the 'transfer-destination-request' message:

{
  "destination": {
    "type": "number",
    "number": "+*******",
    "message": "",
    "caller_id": "{{customer.number}}"
  }
}

HeyDmitry Til Thank you for creating the ticket! A member of our team will reach out to you shortly.

@Dmitry Til Hello! Thank you for reaching out with the details of the issue you're experiencing. It seems like you've done a thorough job setting up your dynamic assistant and specifying the configuration for the transfer call functionality. However, the 'message' field not being applied as expected is indeed unusual. Given the information you've provided, it appears that everything is configured correctly. The issue might be related to a bug or an unexpected behavior in the system that is causing the 'message' field to be ignored. To assist you further, I would recommend the following steps: 1. Double-check the documentation to ensure that there are no additional requirements or configurations needed for the 'message' field to work as expected. 2. Review any recent changes or updates to the system that might have affected the behavior of the 'message' field. 3. If possible, test with different 'message' content to see if the issue persists with various strings. 4. Check the logs associated with the call IDs you've provided to see if there are any errors or warnings that could give a clue as to why the 'message' field is not being applied. If after these steps the issue remains unresolved, it would be best to escalate this to our support team for a more in-depth investigation. They can look into the system's backend and check if there's an issue with how the 'message' field is being processed during the call transfer. Would you like me to initiate a support ticket for you to get this issue resolved?

@Dmitry Til

logs

🔵 12:07:09:581 Got Tool Messages "request-start". Messages: [ { "type": "request-start", "contents": [], "content": "Transferring the call now", "conditions": [] } ] You have to set the request-start message to empty string else the default message is used for your tool and for the destination you can use either of message type according to your requirement instead of custom-message. Do let me know your usage around custom-message then I can help you better.

I have tried everything under the sun to have the bot say a message different then the default one. Where should this request start object be? I tried everything. I've added it in the message object in the destination object like in the docs and tried with custom-message, request-start, request-complete - it just completely ignores it. Can you provide a valid response to a transfer-destination-request request, where we have the user say something mentioned in the request? The whole request which I can just paste and hear the bot say the response, it would be so easy. For example, this response does not make the assistant say the words in the message string but does the forward:

{
  "destination": {
    "type": "number",
    "message": "Connecting you to our support line.",
    "number": "+14155552671",
    "numberE164CheckEnabled": true,
    "callerId": "+14155551234",
    "extension": "101"
  }
}

Hey Dmitry, it is a bug from our end and we are aware about it. We will get this fixed soon.