Inbound Not Connected · Assistable.ai

Inbound Not Connected

I’m running into an issue where any inbound call to some of my assistant’s numbers (not all of them) immediately disconnects without ever ringing. In the Call List, the status shows “Not_connected.” (see screenshot)

Here’s what I’ve checked so far:

I verified that the number is active and routed to the assistant.
I tested with different callers/devices to rule out caller-side issues.

Could someone from the community help me debug this? Here are a few questions I have:

Are there default timeouts or “silence detection” parameters that could cause an immediate disconnect?
Is there a way to view call logs or diagnostics to see exactly why the call shows “Not_connected”?
Could there be a mis-routing or configuration issue on the number itself rather than in the workflow?
Are there known incompatibilities with certain regions, numbers, or carriers that might cause this?
What’s the best way to test whether this is a system bug or a configuration problem?

Thanks in advance for any pointers — I’m hoping I can isolate the root cause and get inbound calls connecting properly again.

2 comments