Here's how webhooks work in Vaani (no code needed)
A webhook is just Vaani sending your app a message when something happens on a call.
You pick the events you care about: call_started, call_ringing, user_picked_up_at, call_rejected, call_no_answer, call_failed, call_ended.
You give us a URL. When a call ends, we send it a message, and you can drop the result in a Google Sheet, ping Slack or update your CRM.
we already run our reasoning in a langgraph pipeline. can vaani handle just the voice and telephony around it?
@heeraa_ananthan Yeah absolutely, its a modular platform, you can bring your own models, plug it in and get going with all your use cases!
@heeraa_ananthan @chandrashekran_y How about node based pipeline? What are the type of models you guys support
Congrats on the launch, Chandra! Starting with languages where data is scarce really resonates. We just localized our app into 14 languages and learned how different "translated" and "sounds local" are.
To your question: the first agent I'd build is a Turkish booking assistant for a small café or studio. What I'd expect to break it: people switching between Turkish and English mid-sentence ("rezervasyonu cancel edebilir miyiz?"), and Turkish suffixes stacking onto names and dates. Curious how it handles code-switching like that.
Fellow maker launching today, good luck to the whole team! 🚀
@erenasiroglu Hey Eren, the use case of Turkish booking assistant for a small café or studio is the perfect case we have tested our platform against, do try it and let us know how it went, can wait to hear back from you, also share the platform amongst your connections for them to check it out, its many months of efforts we have put into this product!