Calls using inbound webhooks connections are giving a busy signal. In the past when my flow has broken its because there has been changes made to the code. Is this the case? My AI receptionist is busy? --the irony. Can somone please help me understand why this could be happening. Thanks

Hey! I can help with this 👍 A busy signal on inbound webhook calls is usually not the AI being “busy.” It’s commonly caused by one of these: The webhook endpoint is failing (timeout, 5xx error, or not responding fast enough) A recent change in the flow/code broke the webhook response The provider expects a specific response (e.g. TwiML / JSON) and isn’t getting it Concurrency or rate-limit settings blocking new calls Quick question to narrow it down: Which provider are you using for the inbound calls (Twilio, Vapi, etc.), and have you checked the webhook request logs to see what response code is being returned?

Hey @Mighty Make sure your inbound webhook responds within 10 seconds with a 2xx status and a valid override_agent_id, otherwise the call will fail as busy. Also verify the number has a fallback inbound agent set and that your SIP/origination settings are correctly configured with your telephony provider.

The webhook had an automated condition that selected a specific agent. The Variable CODE was wrong therefore it was forwarding to an agent that was no longer in the system. My mistake. Thanks for the fast response. Is there a way to have a default fallback agent IF this were to happen again? @Joshua @Shehroze -Support @Retell

Yes in Retell there is an built-in fallback. If the inbound webhook fails or returns an invalid agent ID, it retries 3 times, then falls back to the inbound agent set on the number; if none is set, the call is disconnected. set a default inbound_agent_id on the number and validate the agent ID in your webhook before returning it.

perfect! thanks!