With Cartesia, i have an assistant that has "assistant talks first" with a predefined first message. Since today the assistant does not say the first message (you should have an issue) and thus i had hundred of calls where the assistant would not talk ... This was particularly a problem as I had setup no interruption during first message .. Here is an example: f79f2ae7-6b3a-4530-9678-ce9d9eb068af

hello @pierreh we have the same issue

Same issue here with

assistant-speaks-first

glad it helped darling!

Nice work! Glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue

It seems like a bug on vapi's end, might be worth flagging to make sure what's going on. It broke all of a sudden with no code changes on our end.

Hey pierreh, I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility. Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you. The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!

Yes it was solved after settings the experimental contral field!

Will close this ticket. Thank you for providing that information

@User Kyle, I don't think this is quite resolved, as the docs show that

experimental control speed

is optional: https://docs.vapi.ai/api-reference/webhooks/server-message#request.body.message.AssistantRequest.assistant.voice.CartesiaVoice.experimentalControls

experimentalControls
object
Optional
Experimental controls for Cartesia voice generation

Hide 2 properties
speed
enum or double
Optional

So are the docs incorrect or is there a bug? Given that the behaviour changed all of a sudden, I'm still inclined to think that it's the latter.

Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team

Thanks @Vapi @User , Just confirming, someone on the team has seen this, and it does seem like it would be impacting others as well

You are correct that the field is optional, however this is the current workaround for this specific issue as we continue to work on improving various functions