The Agent uses the Content in the Request Response Delayed field the same way in every language. This message needs to be changed in every language. How can I do this?

To customize the "Request Response Delayed" message for each language, use the workflow-based multilingual support approach and set a language-specific message in each conversation node. For example:

json
{
  "name": "english_support",
  "type": "conversation",
  "prompt": "Request is delayed. Please wait a moment.",
  ...
},
{
  "name": "spanish_support",
  "type": "conversation",
  "prompt": "La solicitud está retrasada. Por favor, espere un momento.",
  ...
},
{
  "name": "french_support",
  "type": "conversation",
  "prompt": "La demande est retardée. Veuillez patienter un instant.",
  ...
}

This way, each language path displays a custom delayed message. See the [workflow-based multilingual support guide](https://docs.vapi.ai/workflows/examples/multilingual-support) for more details. Sources: - [Multilingual support agent](https://docs.vapi.ai/assistants/examples/multilingual-agent) - [Workflow-based multilingual support](https://docs.vapi.ai/workflows/examples/multilingual-support)

I think you didn't understand what I said, I'm talking about Request Response Delayed Content in Custom Tool. https://cdn.discordapp.com/attachments/1438495925151469699/1438496861118795826/CleanShot_2025-11-13_at_12.51.442x.png?ex=69171819&is=6915c699&hm=9dc0cdff085555b2ec898359405c8643a1defe35de56d8e7bd94057f867e7b26&

I can help you update the Request Response Delayed message across all languages so it’s consistent and customized. We can either set a new default message or define language-specific versions if needed. Just to clarify, are you looking for a single universal message for all languages, or do you want different messages per language? @Gokhan

@Manja manna A single universal message for all languages ​​would be better. I understand that this message will be pronounced appropriately in every language.

I can definitely help you handle that. The way to approach it is to set a global default message and then create language-specific overrides so the agent automatically speaks the right version in any language. This keeps everything consistent while giving full control over customization. If you’d like, we can discuss the details privately and jump on a quick call so I can guide you or set it up directly for you. @Gokhan

I overcame this issue with custom API requests. If you want to update the contents of the custom tool you use via the server URL, use this structure. Custom Tool Content Update https://docs.google.com/document/d/14wywWdZzjNdERvumL1xp6dYqol4oyCgTskaRMy1guHY/edit?usp=sharing To update the Handoff Tool contents, you only need to send the messages fields. Handoff Tool Content Update https://docs.google.com/document/d/1Bd5cBGGxRlO_eL7ZfboUzaYEZS_QRjInIpGqIe1a6kk/edit?usp=sharing