Assistant interrupts the conversation very unnatur...
# support
f
when the assistant interrupts the conversation, it stops mid-word, which seems very unnatural and makes people realize it's a robot. How can I make / instruct the vapi Assistant to complete the word or sentence before interrupting and then listen?
v
Hi there! 👋 I understand how frustrating it can be when the assistant interrupts mid-word - it definitely breaks the natural flow of conversation. I can't provide specific code examples for all methods, but I can definitely help you with several configuration options to make your Vapi Assistant complete sentences before interrupting. Here are the key settings you can adjust: ### 1. Adjust Interruption Parameters You can modify
numWordsToInterruptAssistant
and
maxDurationSeconds
to give more time before interruptions: - Set
numWordsToInterruptAssistant
to 3-5 words - Set
maxDurationSeconds
to 5-10 seconds According to [Discord conversations](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334027136305991750), these settings can be adjusted in your VAPI dashboard where you manage call flows or scripts. ### 2. Use Maximum Duration Override Setting
assistantOverrides.maxDurationSeconds
to a higher value (like 120 seconds) will prevent the assistant from interrupting for that duration, as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335807780287676456). ### 3. Configure Custom Endpointing Rules You can use custom endpointing rules with REGEX to ensure the system waits for complete sentences. Documentation for this is available at [this gist](https://gist.github.com/bajajcodes/cd664c81344ef9f27a4d304de43bd313). ### 4. Utilize Punctuation Boundaries The
assistant.voice.inputPunctuationBoundaries
setting helps determine the end of a complete message, making interruptions more natural, as noted in [Discord threads](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336360452208332831). ### 5. Adjust Speaking Plan Configuration Configure the
startSpeakingPlan
with: -
smartEndpointingEnabled: true
-
waitSeconds: 0.8
This helps control when the assistant starts speaking, as referenced in [Discord conversations](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331035264751112202). ### 6. Enable Smart Endpointing Vapi uses a custom fusion audio-text model to determine when a user has completed their turn. According to [Vapi documentation](https://docs.vapi.ai/how-vapi-works), this helps ensure the user isn't interrupted mid-thought while still providing quick response times. Is there a specific configuration from this list you'd like me to explain in more detail? Sources: - [Discord conversations](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334027136305991750) - [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335807780287676456) - [Discord threads](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336360452208332831) - [Vapi documentation](https://docs.vapi.ai/how-vapi-works) - [Discord conversations](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331035264751112202)
f
These settings are only for the moment when the assistant must stop talking. But none of the above settings tell the assistant to finish the word they just started or the phrase they began and only then stop. The lack of such a setting causes the assistant to stop mid-word, which is very unnatural. And robotic. Many customers they immediately realize they are talking to a robot. A human does not stop mid-word. They finish their word completely. Nowhere in the VAPI settings do I find where and how to tell the assistant this. Any idea is welcome!
p
So have you tried setting number of words to like 3? When interruption happens, assistant should say 3 words before shutting up
oh, no sorry, these are words customer needs to say to interrupt ai
k
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!