Issue with Elliot Voice — Suddenly robotic and unnatural after May 14
Hi team, I’m experiencing a sudden issue with the Elliot voice that started just recently — around May 14–15.
Until then, the voice sounded natural, clear, and smooth, and I was very happy with how it performed. But now, using the exact same prompt and assistantOverrides, the voice output has drastically worsened:
It sounds robotic, rushed, and flat
The intonation is unnatural, and
In some cases it even reads text formatting like the word "asterisk" out loud (!)
This is extremely important to us, as we run live real estate calls through Vapi. Voice quality was a major factor in choosing your platform.
We noticed that most of our calls made around this period became affected, which is impacting production use.
Can you please help clarify:
Was anything recently changed or updated in the Elliot voice model or backend?
Is this a known issue? If yes — is there a planned fix or rollback?
What would you recommend to restore the previous natural behavior?
I’ve included one problematic call below for reference:
vbnet
Копировать
Редактировать
Call ID: e1991a77-0f94-4f43-97a5-fdd56ed0b49c
Timestamp: May 15, 2025 – 3:31 PM (New York time)
Expected: Human-like, clear and fluid voice
Actual: Robotic pacing, broken intonation, reads “asterisk” as literal text
We truly want to keep using Vapi — but this recent change makes the voice hard to use in professional calls. Your support and clarification would be very appreciated.
Thanks in advance
Until then, the voice sounded natural, clear, and smooth, and I was very happy with how it performed. But now, using the exact same prompt and assistantOverrides, the voice output has drastically worsened:
It sounds robotic, rushed, and flat
The intonation is unnatural, and
In some cases it even reads text formatting like the word "asterisk" out loud (!)
This is extremely important to us, as we run live real estate calls through Vapi. Voice quality was a major factor in choosing your platform.
We noticed that most of our calls made around this period became affected, which is impacting production use.
Can you please help clarify:
Was anything recently changed or updated in the Elliot voice model or backend?
Is this a known issue? If yes — is there a planned fix or rollback?
What would you recommend to restore the previous natural behavior?
I’ve included one problematic call below for reference:
vbnet
Копировать
Редактировать
Call ID: e1991a77-0f94-4f43-97a5-fdd56ed0b49c
Timestamp: May 15, 2025 – 3:31 PM (New York time)
Expected: Human-like, clear and fluid voice
Actual: Robotic pacing, broken intonation, reads “asterisk” as literal text
We truly want to keep using Vapi — but this recent change makes the voice hard to use in professional calls. Your support and clarification would be very appreciated.
Thanks in advance
