plaintext - Always use the webhook response when making a call transfer. - Do not assume or generate phone numbers yourself. - Only use the data provided by the dynamicTransferHandler tool. This prevents the assistant from making up placeholders. ✅ Step 4: Test with a Simulated Webhook Response Manually trigger the webhook in Make.com using a test payload. Confirm that Vapi receives the correct response. If the assistant still uses placeholders, try adding a delay of 1-2 seconds in Make.com before sending the response. ✅ Step 5: Debugging Further in Logs Check Vapi's logs → Does the tool actually receive destination: "+1405818XXXX"? If not, Make.com might not be responding fast enough. Try reducing execution time in Make.com by optimizing unnecessary steps. 🔹 Final Fixes to Try ✔ Ensure your Make.com response exactly matches Vapi’s expected structure. ✔ Update the assistant’s prompt to enforce correct behavior. ✔ Force the assistant to use the webhook response instead of making assumptions. ✔ Add a short delay (if necessary) to ensure the response is processed correctly.