Feature Requests

You've made 90% of the job by intergrating Gladia solaria transcriber model. Let's just add some configurations parameters, especially custom vocabulary : https://docs.gladia.io/chapters/live-stt/features#custom-vocabulary Custom vocabulary is a must have to compete with Deepgram nova. Custom spelling would be a nice to have.

Add dual mode support for widgets Chat AND Voice Mode, not having to choose either of these.

Implement the same objects as the assitantOverrides JSON for when using the API to start a call with a Workflow. I need to pass metadata when using workflowOverrides, I used to do this with Assistants, but when switching to workflows it is impossible.

https://www.loom.com/share/4bf293ba6c8a42a6bd7502cbc58780a1?sid=a55af4b9-662e-4c9c-8e8b-c84cf60fe74b

The current version of @vapi-ai/client-sdk-react only supports React 18.x in its peer dependencies. When attempting to use the SDK with React 19.1.0, I encounter dependency resolution conflicts because the package's peer dependencies don't include React 19. Background Context React 19 Release: React 19 was officially released on December 5, 2024, and has been stable for several months Industry Adoption: Many frameworks like Next.js 15 are already using React 19, and the React ecosystem is rapidly adopting the new version Current Limitation: The VAPI React SDK currently restricts users to React 18.x, preventing adoption of React 19's new features and improvements I would like to request that the VAPI team: Update peer dependencies in @vapi-ai/client-sdk-react to include React 19.x support Test compatibility with React 19.1.0 to ensure all features work correctly Update documentation to reflect React 19 support once implemented Business Impact Developer Experience: Currently, developers must choose between using VAPI's excellent voice AI capabilities or upgrading to React 19 Future-Proofing: React 19 adoption is accelerating, and early support would position VAPI as a forward-thinking solution Competitive Advantage: Many other SDK providers are already updating for React 19 compatibility Compatibility Considerations Based on industry patterns, React 19 maintains backward compatibility with most React 18 code. However, I understand that proper testing would be needed to ensure full compatibility with VAPI's specific implementation. Alternative Workarounds While waiting for official support, developers currently must use --legacy-peer-deps or --force flags with npm/yarn, which is not ideal for production environments. Thank you for your time and consideration. I look forward to your response and am happy to provide any additional information or testing assistance if needed.

Transcriber is not able to transcribe few region specific names like Indian names. My name is Kamalesh. When I tell my name to AI it transcribes as Kamalish or Kamlesh, Kamalays since it is not familiar with Indian names. Though I spell the name as K A M A L E S H to AI it gets the spelling accurately but the next time it says my name again it transcribes as Kamalish or Kamalays or Camlesh. The spelling which i told the AI is not going to its memory and gives new spelling everytime. If I add my name in keywords it transcribes the spelling correct everytime. Problem here is, we have to give the keywords before the start of the call and we don't have an option to update the keywords during the call. It will be greatly helpful if this feature is added.

In the transfercall tool destinations array of objects (CreateTransferCallToolDTO, TransferDestinationNumber), the parameter callerId enables to choose between setting the customer.number or phoneNumber.number. This only works for TWILIO and not VONAGE. A calls B B forwards to C Currently C sees B number by default (phoneNumber.number), I would like this to be a choice.

Want long term conversational memory to be built in.

Call Recording documentation not working ( https://docs.vapi.ai/assistants/call-recording )