Vapi is the Voice AI platform for developers.

Vapi AI

1a09b245-fdde-4d14-8901-c54111630850 
It's in italian, however it doesn't seems to catch the "SI"/"YES"

<@1247423790946713693>
I understand you're experiencing issues with the voice recognition for Italian, particularly with the word "SI" or "YES." To assist you better, could you please provide more details about the context in which the issue occurs? Are you using a specific function or feature when this happens?

You can continue this conversation by mentioning me in the message.

Is not catching the single word in general 😦

<@1247423790946713693> as you have already done the first two, I suggest working on point 3rd instead of changing deepgram endpointing because deeprgram endpointing will be appleid for complete call. 

1. using default startSpeakingPlan
2. using smart-endpointing along with default-StartSpeakingPlan
3. using custom rules for startSpeakingPlan according to the calls

Try out few calls with default startSpeakingPlan and smartEndpointingEnabled set to true if works for you, else we have to figure out custom rules according to your call"s nature.

```json
  "startSpeakingPlan": {
    "smartEndpointingEnabled": true
  }
```

Do let me know if you require further help.

Hey <@458562482378768394>  To help track down this issue, could you share the following in a new <#1211483291191083018> ticket:
- 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 me figure out what went wrong!

I see another post that says to set this in the startspeakingplan

"transcriptionEndpointingPlan": {
      "onPunctuationSeconds": 0.4
    }

It's a little bit better but sometimes it still doesn't catch single words

Seems that has been fixed, is now able to catch simple "yes/no"

It still doesn't work for me, which transcriber are you using? Deepgram?

<@458562482378768394> can you create a new <#1211483291191083018> ticket and tag me over there with the following details:
- call id
- expected response
- actual response

<@458562482378768394> I did have the same issue yesterday n one call...