Sahil Suman thanks for marking this as in progress. Do you have any view on the approximate timeline for deployment ? Happy to jump in a call as well if something is unclear from my prior messages 🙏

Just had a discussion with @Sahil during OH on vapi-stage. Let's clarify what is needed from the new model upgrade :

1) At this stage, GladiaTranscriber type of VAPI API does allow "languageBehaviour: manual", but does not allow to select manually multiple languages. Basically, the language parameter is only a string, not an array of strings. The new model from Galdia enables to select multiple languages manually (unlike alternatives like deepgram which sets language param to multi and might include non relevant languages, making it prone to mis-recognition). The manual selection of multiple languages is very powerful in the case of Canada (en, fr) or Belgium (fr, nl, en) for example.

Linking here Gladia documentation : https://docs.gladia.io/chapters/live-stt/features#multiple-languages-code-switching

2) The new model from Gladia also enables custom vocabulary (similar to keywords or keyterm from Deepgram). This is new so should be provided in VAPI's GladiaTranscriber

Linking again Gladia documentation : https://docs.gladia.io/chapters/live-stt/features#custom-vocabulary

We found it to work much better with multilingual

We'd really love to have this.

Custom vocabulary is also a must-have !

Thanks 🙏

Including the multi-select of languages (e.g. selecting only "fr", "nl" and "en" as languages).