The call never rang
The record says the call never rang, which is a different fact from nobody picking up. Something before the ring failed: the dial at the carrier, the dispatch that should have put a worker on the call, or the worker itself. No lead is created from it and no conclusion should be drawn about the person called — this is an operational failure, not a signal about them.
What it looks like#
The contact reports no missed call. The call record exists with a short or zero duration and an outcome saying the caller was not reached. Nothing was said, so there is no transcript, and the follow-up that prompted the call — if there was one — is still outstanding.
| Record | Meaning | What it says about the contact | What to do |
|---|---|---|---|
| Nobody answered | It rang; nobody picked up | They are reachable and were busy or unavailable | Try again later; this is normal |
| Never reached | It never rang at all | Nothing whatsoever | Fix the path; retrying without a fix produces the same result |
What it means#
Connect gives these two outcomes separate words because they need different responses, and because a lead invented from a call that never connected is worse than no lead at all. Neither produces one. A call that was never a conversation is recorded as exactly that, so the number of attempts and the number of conversations never quietly merge into one figure.
Causes, most likely first#
- The dial was refused or timed out at the carrier. A timeout is dialled once more, once only, so a persistent carrier problem shows as a run of these.
- No worker was available. Admission refuses before a record exists in that case, so if you have a record, the refusal came later than admission — but a fleet that came and went during a deploy can produce both.
- The model identifier was rejected. A malformed identifier, or one written as a path for the wrong platform, is refused as a bad model rather than attempted. One test call rang the line and then died for exactly this reason.
- The leg was answered at the carrier but never joined. It is written off after a fixed timeout rather than waited on indefinitely, and the record shows the same outcome.
- The number was never routed to the application or the trunk. Common immediately after a setup change, and it fails identically every time rather than intermittently.
What Connect completed#
- Passed every gate the call had to pass — consent, autonomy, hours, budget — before attempting anything.
- Attempted the dial, and retried it once if the carrier answered with a timeout.
- Recorded the attempt with an outcome that says precisely which kind of non-conversation it was.
- Kept the originating follow-up outstanding rather than closing it against an attempt that reached nobody.
What Connect did not complete#
- The person was not reached, and did not see a missed call.
- No conversation, transcript or summary exists.
- No lead was captured, on purpose — a non-conversation is not evidence of interest.
- Nothing was learned about the contact. Their record should not be marked unreachable on the strength of this.
What you can do#
Check whether it is one call or a run of them.
Result One is usually a carrier hiccup. A run in the same window is a path failure and retrying will not help.
Try the number from an ordinary phone.
Result If it rings, the contact is fine and the problem is entirely on the Connect side, which narrows it immediately.
Place a test call from the workspace to a number you control.
Result A test that also never rings confirms the path rather than the contact.
Leave the follow-up in place rather than closing it.
Result It stays due and is retried, and is only surrendered to a person after the late cut-off.
What an administrator can do#
- Confirm the model identifier configured for the line is a valid one, not a path form for another platform.
- Confirm a worker was live at the time of the attempts; a deploy window produces exactly this shape.
- Confirm the number is routed to the intended application or trunk after any setup change.
- Compare the carrier's log with the workspace's calls — an attempt the carrier never saw and an attempt it saw and failed have different fixes.
When to escalate#
Escalate when more than a handful of calls in one period were never reached, when it began right after a release or a setup change, or when inbound calls are affected too — inbound and outbound failing together points at routing rather than at dialling. Bring the time range, the count of affected calls, and whether an ordinary phone can reach the same numbers.
Questions#
Should the contact be marked as unreachable?
No. Never-reached says nothing about the person; it says the call did not leave. Marking a contact on the strength of it puts a permanent, wrong fact on a record that other decisions will be made from.
Why was no lead created?
Because there was no conversation. Lead capture ignores both kinds of non-conversation, which is what keeps a week of failed dials from becoming a pipeline of people who have never heard of the business.
Will the promised call-back be attempted again?
Yes, while it is still worth keeping. Past the late cut-off it stops being placed and becomes a decision for a person, with the reason attached — a call-back a day late reads worse than none.