VHey gravitygod,
I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility.
Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you.
The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!
I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility.
Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you.
The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!
NThanks for the heads up mate 
NI appreciate it!
VHey, here are some steps to troubleshoot the issue:
- Test with a simpler mode (warm-transfer-say-summary).
- Change the SIP verb from refer to dial.
- Add a timeout and fallback plan.
- Verify that the destination number can receive calls.
- Check Twilio call logs for specific error details.
- Monitor the call status in real-time using the monitor URLs.
