URGENT Issue: assistant-request Webhook Not Firing for Telephony Calls
Hello Vapi Support Team,
I'm opening a new ticket for a critical issue I'm facing with dynamic variables on my telephony agent.
What's Working: Thanks to previous help, my Twilio BYO numbers are now successfully connecting to my Vapi agent via the /inbound_call webhook. The agent answers the call correctly.
I'm opening a new ticket for a critical issue I'm facing with dynamic variables on my telephony agent.
What's Working: Thanks to previous help, my Twilio BYO numbers are now successfully connecting to my Vapi agent via the /inbound_call webhook. The agent answers the call correctly.
The Problem: The initial assistant-request webhook is not being sent from Vapi to my backend on Make.com.>
The Result: Because the webhook never fires, my Make.com scenario (which looks up business details) never runs. This causes the agent to speak the literal variable names (e.g., it says "{business_name}") instead of the dynamic data.
What I've Checked:
- I have confirmed there are no new execution logs in my Make.com scenario when a call comes in, which proves the webhook is not being sent from Vapi.
- The webhook URL for my Make.com scenario is correctly configured in my agent's Advanced > Messaging > Server URL field.
- The web-based "Talk to Assistant" feature does correctly fire this webhook, but telephony calls do not.
Could you please investigate why the assistant-request webhook is not being triggered for inbound telephony calls on my account? It seems to be the final piece needed to get my system working.
Assistant ID: 76f3b9f6-6324-4861-bfc5-5e4bef85f41b
Thank you for your help.