Forwarding takes minutes to set up, but the wrong scheme costs lost calls and irritated callers. A DID number supports four forwarding types, covering needs from one person without a second device to a team across time zones. Here is how the schemes differ, what happens to quality on each hop, and when to swap forwarding for a voice menu with a queue.

Four forwarding schemes

Unconditional forwarding sends every call onward immediately, without attempting the main number — used when the primary device is known to be unreachable, for example a vacation with all traffic going elsewhere.

Forwarding on busy triggers only when the line is already tied up: the caller does not hear empty ringing, the call moves to a backup number right away.

Forwarding on no answer is the most common scheme: the system waits a set number of seconds, then forwards the call. Set the delay deliberately — too short cuts the call before a person reaches the phone, too long keeps the caller waiting longer than they will tolerate.

Forwarding on schedule accounts for time of day and day of week: business hours go to the office number, nights and weekends to whoever is on duty — the only scheme that natively handles time-zone differences inside a team.

Mobile number versus a SIP softphone

Forwarding to a mobile number goes through the carrier's voice network: the DID number answers and immediately places a second call, as if you dialed it yourself. Convenient for one person with no special equipment, but minutes are billed separately, and the route depends on the carrier's network too.

Connecting a softphone over SIP works differently: the call travels straight over the internet to a registered device, no intermediate dial-out. Fixed cost, one voice hop instead of two, any connected device can take it — for someone online most of the time, cheaper and more stable than a mobile forward.

Quality and latency on each hop

Every forward adds a network segment, and with it, latency and a risk of degraded sound. The base route already carries its own delay; a mobile forward adds a second voice hop and setup time. Two or three forwards in a row can push combined latency past the threshold where conversation stops feeling natural — covered in call quality on a DID number. Transcoding at network boundaries matters too: each codec change along the path recompresses audio, losing tonal detail.

Why a chain of forwards eats into call time

"No answer from one, forward to another, no answer there either, forward to a third" looks reliable on paper but eats the caller's patience. If each link waits 15–20 seconds, three links in a row is almost a minute of ringing before a live person, and some callers hang up early, assuming the number does not answer. A second risk is a forwarding loop: a last link pointed back at the first, or at a dead number, drops the call with no explanation — every chain deserves a real test call, not just a check of the settings.

A voice menu and queue instead of forwarding

Once a chain grows to three or more people, a voice menu and a call queue usually work better: a single entry point sorts the call immediately, and the queue routes it to the first free agent instead of dialing down a list, so the caller waits once instead of sitting through several unanswered attempts. This setup on top of a virtual PBX is covered in virtual PBX and DID.

What to choose: one person, a shift, or a distributed team

One person with no office usually needs just forwarding on no answer to a SIP softphone with a 15–20 second delay, plus a backup forward to a mobile number for offline moments. A single shift in one time zone works better with forwarding on busy within the team, or a short queue across two or three numbers, than a long chain. A distributed team across time zones needs forwarding on schedule — the only option that does not wake the on-duty person at night; paired with a voice menu, it handles an international call flow with no physical office at all.

Frequently Asked Questions

Can several forwarding schemes be combined on one number?

Yes — busy as the first level, no answer as the second, if the first recipient also does not pick up. Test the chain with a real call so delays do not add up to an unacceptable wait.

How is forwarding to a mobile number worse than SIP?

It goes through the carrier's voice network, billed as a separate outbound call and adding a second voice hop. SIP runs directly over the internet at a fixed cost, with no second hop.

What delay should be set for forwarding on no answer?

A reasonable default is 15–20 seconds: enough to reach the phone, but not so long the caller assumes nobody answers. Test critical lines with real calls rather than leaving the default.

The right scheme can be set up right when the number is connected — the catalogue of DID numbers with flexible inbound routing is in the DID numbers section on turbon.rent.