VAPI•6mo ago

customEndpointingRules regex - do nothing

We set startSpeakingPlan with waitSeconds 3.0 seconds for the entire conversation, but we would like to have the BOT to respond much faster once the User answer yes/on.
Therefore we used the customEndpointingRules feature.
We tried to use it with assistant type (and set the regex with the user message) but no impact - the bot still wait 3 seconds until it start to speak. Arthur suggest me during his OH to change the type to customer. so we changed it to customer type, and set the regex with yes|no values, but no impact as well. i changed the regex value to ^(yes|yes\.)$ hoping it could work but no impact as well. @arthur
see Call ID example: 10f9bc44-4bb7-44e9-aa34-9084544e7ff2
We really need this option to set a faster waitSeconds on specific parts of the conversation.
I sent email to Vapi support (with email title customEndpointingRules) about such issues while setting the type to assistant, see Call ID d7388e65-07ad-432c-adc3-ac51201f40a8 as such example. Kyle respond it is something Vapi team need to review.
Please help to fix customEndpointingRules to work with one of the options atleast.
Tnx

VapiAPP•7/3/25, 6:50 AM

Hey, thanks for the details. Our team will look into it and get back to you.

embarrassing-maroonOP•7/10/25, 2:39 PM

Hi, still waiting for your feedback on this important subject

VapiAPP•7/11/25, 11:20 PM

Hey Amir76! So from what I can see, the waitSeconds parameter is basically a fixed delay that gets applied before the TTS output plays for the Assistant's audio.

My guess is that your regex pattern isn't matching, which could be preventing your custom end pointing rules from kicking in properly.

Sahil's currently out at an offsite, but he should be back on Monday and can definitely help you dig into this and figure out the best way to get your setup working the way you want it to.

embarrassing-maroonOP•7/20/25, 9:31 PM

Hi, i am still waiting for a resulution on this important subject. Tnx

embarrassing-maroonOP•7/21/25, 7:04 PM

Recap extra investigation i just had with Arthur during his OH: the regex has no influence on the waitSeconds. I should try using smartEndpointingPlan or transcriptionEndpointingPlan instead.

VapiAPP•7/26/25, 1:35 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

customEndpointingRules regex - do nothing

Similar Threads

Similar Threads

Similar Threads