When creating outbound calls inside make.com, when using the Vapi-Paige voice the first message's voice is a man's voice, and after the first message was spoken, then the real Paige voice starts speaking (woman). It is some type of bug i think. In web calls it works perfectly fine, but when calling an http module inside make.com the first message is spoken by a man. I really like this voice so I would like to get this fixed as soon as possible.

To ensure the Paige voice is used consistently, explicitly set the voice provider and voiceId in your assistant configuration when making the HTTP request from Make.com. For example:

json
"voice": {
  "provider": "vapi",
  "voiceId": "paige"
}

This should help prevent fallback to a different (male) voice for the first message. If the issue persists, consider reaching out to [Vapi support](support@vapi.ai) with your payload details for further assistance. Sources: - [Vapi Voices Documentation](https://docs.vapi.ai/providers/voice/vapi-voices) - [Vapi API Reference Create Assistant](https://docs.vapi.ai/api-reference/assistants/create) - [Vapi Support](https://docs.vapi.ai/support)

not solved

Hey! To help track down this issue, could you share: \- The call ID \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!