Hello,
Thank you for your previous advice. I am writing to report that I have followed your instructions exactly, but the system is still failing with a critical error.
Here is a summary of the steps I have taken based on your guidance:
I have confirmed that no assistant is assigned to my phone number in the Vapi dashboard's "Inbound Settings".
My Tradie Agent (Main) has its Server URL (Advanced > Messaging) correctly pointing to my Make.com webhook.
My Make.com scenario is correctly configured to listen for the assistant-request and respond with the required JSON, including the correct assistantId and the override.variableValues.
The Result: When I call my Twilio number now, the call connects, but I hear an automated Vapi error message that says: "Couldn't Get Assistant. Either Set The Assistant I D On The Phone Number. Or, To Debug Your Assistant Request, Check The Debugging Artifacts That Were Just Sent To Your Server."
I have checked my Make.com scenario logs immediately after the call, and it confirms that no request was received from Vapi. The scenario was not triggered.
Conclusion: This definitively proves that even with the assistant un-assigned, Vapi's platform is failing to send the assistant-request webhook to the Server URL configured in my agent's settings. Because the webhook never fires, my backend cannot provide the assistantId, and the system fails.
We have now tried every possible user-side configuration. This appears to be a platform-level bug. Could you please escalate this to an engineer to investigate why the assistant-request webhook is not being sent for my account's telephony calls?
Here are the details for the latest failed call:
Vapi Assistant ID: r0OD73nMrg74ALdXpHu8
Twilio Phone Number: +6498867324
Failed Twilio Call SID: CA18672cbd82973b30238fde4bd07a1d2e
Thank you for your urgent attention to this matter.