VAPI•6mo ago

Speech to text and text to speech issue.

Speech to Text: Transcribe service not working properly (used Deepgram's Nova 3)
Text to Speech: It is sometimes missing to produce parts of voice and also the numbers coming is the text response is not properly hanled while converting it to speech

extreme-purple•7/11/25, 6:49 AM

Add 0.5–1 sec of silence at the start of audio before using Deepgram Nova-3 for better transcription, and for vapi TTS, switch to the Aura-2 voice, format numbers using SSML, and add slight playback delays to avoid speech cutoffs..

verbal-limeOP•7/11/25, 9:31 AM

And any idea as why is this happening with model set to sonar-pro in perplexity.

It is abruptly stopping

verbal-limeOP•7/11/25, 9:31 AM

@Kings_big

verbal-limeOP•7/11/25, 9:41 AM

I see the model being hit (the number of api calls to the model increased) but the response in not correctly received, neither on chat not on voice.

KyleAPP•7/13/25, 12:11 AM

Hey Ska,

Thank you for reaching out. Please note that our team does not operate over the weekend. We'll be back in the office on Monday and will dive straight into your issue then to determine the best way forward.

Vverbal-lime And any idea as why is this happening with model set to sonar-pro in perplexity....

extreme-purple•7/13/25, 6:47 AM

We truly apologize for the inconvenience you’ve faced. To help you resolve this issue quickly, please share your call_id with us. Thank you for your understanding..

verbal-limeOP•7/14/25, 5:20 AM

Hi @Kings_big

I have sent you the chat id in your dm

verbal-limeOP•7/14/25, 5:22 AM

I was able to fix this using my custom endpoint integration for LLM changing the data handling format

Vverbal-lime Hi @Kings_big💫 I have sent you the chat id in your dm

extreme-purple•7/14/25, 10:44 AM

Marketing this ticket as solved

verbal-limeOP•7/15/25, 10:54 AM

Not yet solved @Kings_big

verbal-limeOP•7/15/25, 10:54 AM

verbal-limeOP•7/15/25, 10:54 AM

Let me know if you want to know about the fix

verbal-limeOP•7/15/25, 10:56 AM

The same thing I solved using using my custom endpoint chnaging the response body

verbal-limeOP•7/15/25, 11:00 AM

The chat id was already shared with you in DM

Vverbal-lime Hi @Kings_big💫 I have sent you the chat id in your dm

extreme-purple•7/15/25, 6:32 PM

Thank you for sharing your information! I’ll keep you posted as I work on resolving your issue. Your patience is truly appreciated..

verbal-limeOP•7/17/25, 1:20 PM

Any update here @Kings_big

verbal-limeOP•7/17/25, 1:21 PM

I am kind of sure that no one is looking into it

verbal-limeOP•7/17/25, 1:21 PM

As an issue of this size, it must already be solved by now

Vverbal-lime I am kind of sure that no one is looking into it

extreme-purple•7/18/25, 3:46 PM

Hey, could you please share a few more chat IDs? We looked into the shared chat IDs, but we are unable to reproduce this. Sharing a few more chat IDs will help us reproduce this and eventually get it fixed for you..

verbal-limeOP•7/18/25, 6:50 PM

Shared with you in your DM

extreme-purple•7/18/25, 6:51 PM

Seen looking into it

verbal-limeOP•7/18/25, 6:53 PM

The error can be reproduced by selecting perplexity in the provider

Vverbal-lime The error can be reproduced by selecting perplexity in the provider

extreme-purple•7/18/25, 6:58 PM

Hey, thanks for sharing the chat_ids. I've forwarded this to the executives, and I'll get back to you once I receive the response from them..

verbal-limeOP•7/18/25, 7:04 PM

We are trying to launch some things on prod soon with mjor portion of our backend dependent on VAPI, hence would appreciate if this could be solved soon.

verbal-limeOP•7/18/25, 7:04 PM

Been getting this issue since more than a week now

KyleAPP•7/19/25, 6:10 PM

Hey Ska,

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!

verbal-limeOP•7/21/25, 10:37 AM

Any update on this @Shubham Bajaj and @Kings_big

extreme-purple•7/21/25, 10:24 PM

Hi @Ska ,

We've confirmed there's might be an issue that's causing responses to cut off mid-generation.

Switch to OpenAI GPT-4o for production. This will resolve the truncation issues immediately.

Let's connect in DMs to reproduce the issue and schedule a call to discuss how we can fix this. For now, the immediate solution is switching to another model.

Don't delay your launch - OpenAI models will give you reliable performance without these issues.

Thanks for the chat_Ids that helped us identify this.

verbal-limeOP•7/22/25, 6:01 AM

@Kings_big

I am aware that with other models this abrupt behaviour is not observed. But it won't be solving my issue.

verbal-limeOP•7/22/25, 6:02 AM

I specifically required the model from perplexity for which you provided the integration (one of the main reasons of me moving to Vapi)

verbal-limeOP•7/22/25, 6:03 AM

And this is the reason why I am asking you guys since more than a week about this issue hoping to get this fixed

verbal-limeOP•7/23/25, 4:59 AM

@Vapi It's useless reminding to you guys everyday since more than 10 days now for an issue.

I think its better if I move out of @Vapi .

verbal-limeOP•7/23/25, 4:59 AM

Thanks

KyleAPP•7/26/25, 1:42 PM

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

Speech to text and text to speech issue.

Similar Threads

Similar Threads

Similar Threads