Call forwarding is the oldest trick in business telephony and still one of the most useful. It is also the feature most often left switched on by somebody who left the company two years ago.
This guide covers the four types, where forwarding actually happens, what it does well, and the point at which a business has outgrown it and needs something that routes rather than simply redirects.
What call forwarding is
Call forwarding sends an incoming call to a different destination instead of ringing where it was dialled. The caller dials one number; the phone rings somewhere else entirely.
That redirection happens before anyone answers, and that detail separates it from transferring a live conversation. Nobody picks up and passes the call along; the network or the platform decides by itself.
The destination can be almost anything: another desk, a mobile, a colleague, a mailbox, a switchboard service or a queue inside contact center software.
Two properties make it useful. It requires no action from anybody at the moment a call arrives, which is exactly what you want when nobody is there to act. It also works on ordinary telephone numbers, so the caller needs no app, no account and no knowledge of how any of it is arranged.
The feature predates almost everything else in this field, and its longevity says something. A mechanism that survived the move from mechanical exchanges through digital switching to cloud platforms is solving a problem that has not changed.
The four types
Most systems offer the same four conditions, and knowing which is which prevents a surprising amount of confusion.
Unconditional forwarding
Every call goes straight to the destination without ringing the original number at all. Useful during leave, office closures or a permanent change of responsibility.
This is the type most often forgotten about. Because the original line never rings, nobody notices it remains active, and it usually comes to light when a customer mentions reaching somebody unexpected.
Forwarding on busy
Calls redirect only when the line is already occupied. Everything else rings normally.
For a single-line business the difference is stark: a second caller either hears a busy tone or reaches somebody who can help. Larger setups use it as a first overflow step before anything more involved.
Forwarding on no answer
After a set number of rings, an unanswered call moves elsewhere. The ring count matters more than people expect, since too few feels abrupt and too many leaves callers waiting.
Four or five rings suits most situations, though a team frequently away from desks may want fewer. Count in seconds when comparing systems, since ring duration varies between networks and the caller experiences time, not repetitions.
Forwarding when unreachable
Calls redirect when a device is switched off, out of coverage or disconnected. This one applies mainly to mobiles and acts as a quiet safety net for field staff.
Conditions can be combined, and most usefully are. A common arrangement rings a desk, passes to a handset after four rings, then falls back to a mailbox if that is unreachable. Each condition handles a different failure, so configuring only one leaves gaps.
Where forwarding happens
The same feature exists at two different layers, and which one you use changes what you can do with it.
At the carrier or network level
Your operator holds the rule. Configuration usually happens through device menus or dial codes, and it functions with no software running at all.
Simplicity is the advantage, along with reliability: nothing needs to be running for it to work. The limitation is intelligence, since the network recognises those four states and nothing beyond them. It cannot consider the hour, the caller, the language needed or who is actually available.
Visibility is the second limitation. The operator knows a call was redirected; your business generally does not, which makes measurement close to impossible.
At the platform level
A cloud phone system or contact center platform applies its own logic before deciding where a call goes. That opens up conditions the network cannot reach.
Time of day, day of week, the language a caller selects, which advertised number they dialled, how long the queue is, and whether anybody is actually signed in all become usable inputs.
Changes also happen centrally and instantly. Somebody adjusts a rule in a browser and every affected line follows, which beats asking six people to update their handsets.
Most organisations end up using both layers. Carrier forwarding acts as the backstop that survives an internet outage; platform logic handles everything requiring judgement.
How to set it up
On a mobile or handset
Both routes work. Device menus expose all four under call settings, while dial codes achieve the same result where a menu is missing or awkward.
The codes follow a widely used convention across mobile networks, with separate sequences for activating each condition, cancelling it, and checking what is currently set. Your operator lists these, and keeping them to hand beats searching during an incident.
Desk phones and older systems vary more. Some expose forwarding through a dedicated button, others through a menu, and a few only through the system administrator. Check which applies before promising anybody they can set it themselves.
One practical warning about dial codes: they take effect immediately and confirm with a brief message that is easy to miss. Verify afterwards with the interrogation code rather than assuming it worked.
In a business phone system
Here forwarding stops being a single setting and becomes part of a configuration. Administrators build rules centrally, apply them per extension or per group, and change them without touching any device.
Tools such as Flow Builder exist so operations staff can design those paths themselves, which matters because rules nobody can amend quickly stop matching how the business runs.
Version history is the underrated benefit. Where a system records who changed what and when, working out why calls started behaving oddly on Tuesday takes minutes instead of a morning.
Forwarding, transfer and routing
Three terms get used interchangeably and mean quite different things.
Against call transfer
Transfer moves a conversation already in progress, with a person deciding where it goes. Forwarding acts before anybody answers, without human involvement.
Both have their place. A receptionist passing a caller to accounts is transferring; a line that rings somebody’s handset after six o’clock is forwarding.
Transfer types are worth knowing too. A blind transfer hands the call over and disconnects; an attended transfer lets the first person speak to the second before releasing. Customers notice the difference, since one produces a warm handover and the other feels like being passed around.
Against call routing
Routing is the broader discipline, and forwarding is one primitive inside it. A routing system considers skills, languages, queue depth, customer history and business rules, then chooses a destination accordingly.
Forwarding answers one question: if this condition is true, send the call there. Our note on call routing covers what sits above that.
Neither term is a marketing upgrade of the other. Plenty of businesses need forwarding and nothing more, and buying routing for a five-person office adds cost without adding anything anybody uses.
Business use cases
Out-of-hours cover
The commonest use by far. Calls arriving after closing move to an answering service, a duty mobile or a mailbox somebody genuinely checks.
Public holidays deserve their own rule rather than relying on whoever remembers to set one. Regionally this is more work than elsewhere, since Islamic holidays move each year and announcements sometimes come days in advance.
Field and mobile staff
Sales people, engineers and property agents rarely sit at desks. Sending the published extension through to a mobile keeps them reachable without handing out a personal number.
Such an arrangement protects the business as much as the individual. When somebody leaves, the relationship stays with the company rather than departing on their handset.
Continuity during absence
Leave, illness and departures all leave a line ringing at an empty desk. Redirecting it takes seconds and prevents a caller reaching a dead end.
Make it part of the leaving process rather than something remembered later. A short checklist covering forwarding, mailbox access and directory entries costs nothing and prevents months of lost enquiries.
Overflow protection
Where one line gets busy, forwarding on busy passes the next caller to a colleague rather than a tone. For small teams it is among the cheapest improvements available.
Aggregator-fed businesses use it differently. Insurance and property operations here take enquiries from several comparison platforms, and forwarding each published line into one destination works until somebody asks which platform produced which enquiry. At that point attribution becomes the real requirement.
Where forwarding falls short
It has no memory and no visibility
A forwarded call carries nothing with it. The person answering knows only that a phone rang, not which number the customer dialled, what they wanted, or whether they called twice already.
Reporting is thinner still. Forwarding leaves little trace, so nobody can say how many reached the mobile, how many were answered, or how long people waited.
That is the wall businesses hit. Rules multiply, each sensible when it was created, until nobody can describe what happens to an arriving call without drawing a diagram. A routing platform replaces that sprawl with logic somebody can read.
Recording is the other gap. Conversations landing on a personal mobile are not captured, and that counts where quality review or regulatory obligations apply, and nobody notices until somebody requests a recording that does not exist.
Availability is the third. Forwarding pushes calls onward whether or not anybody is there, since it has no concept of who is signed in or already occupied. A queue knows; a forwarding rule never will.
Costs and things that catch people out
What it can cost
Operators sometimes provide it free and sometimes charge for it as an outbound call from your line to wherever it goes. Pointing a landline at an international handset has produced some memorable invoices.
Check how your operator charges before setting anything up, particularly where the destination sits in another country. Business tariffs sometimes differ from consumer ones here, so ask specifically.
Platform forwarding usually behaves differently, since the call is already inside a system you licence. Onward legs to outside numbers may still carry per-minute charges, and confirming that beats finding out on an invoice.
Then there is the forgotten rule, which is the commonest problem of all. Somebody forwards a line during a busy week, forgets, and calls quietly land somewhere nobody monitors for months. Audit active forwarding quarterly, and check it whenever anybody leaves.
Loops deserve a mention too. Forward A to B while B forwards to A and calls disappear into a circle, which most systems detect and some do not.
Two further traps recur. Caller identity sometimes changes along the way, so whoever answers sees your own line instead of the customer, which makes calling back impossible. And emergency calling behaves differently once forwarding is active, and that difference matters before anyone relies on it for safety.
The Gulf angle
Local considerations
Both UAE operators support the standard conditions, and dial codes work as they do elsewhere. What differs is context rather than capability.
Language is the first consideration. Running Arabic and English through one queue is ordinary practice regionally, and carrier-level forwarding cannot tell which a caller needs, so anything language-aware has to happen at the platform layer.
The working week complicates out-of-hours rules. Where the federal schedule, private-sector hours and an offshore team’s roster all differ, a single rule based on one calendar will be wrong for somebody. Ramadan complicates this further, shortening hours and moving contact volume later into the day.
One regulatory point is worth noting for anyone forwarding outbound activity. Marketing calls are governed separately, and Cabinet Resolution No. 56 of 2024 requires them to originate from local phone numbers issued by telecommunications companies licensed in the State and registered under the calling company’s commercial licence. Forwarding arrangements do not change which number you are entitled to present.
Doing it well
A short checklist
Six things separate a forwarding setup that helps from one that creates problems:
- Write down every rule. What forwards where, on what trigger, and who decided.
- Name an owner. Somebody must be responsible for reviewing it.
- Set a review date. Quarterly is enough for most businesses.
- Check on departure. Anybody leaving may have rules pointing at their mobile.
- Test the destination. A rule pointing at a disconnected number fails silently.
- Decide what happens if nobody answers there either. Forwarding to an unanswered phone solves nothing.
This is where most setups quietly fail. A chain ending at a device nobody answers has relocated the problem rather than solving it.
Test from outside your own network as well. Calling an internal extension from a desk beside it proves very little about what an external customer experiences, and the two paths can behave differently.
One habit is worth building regardless of which layer you use. Keep a single sheet listing every published number, where it currently points, what triggers the rule, and who asked for it. Estates grow quietly, people move on, and an hour spent documenting this saves considerably more later.
Where to go next
For a small team wanting calls to reach somebody after hours, carrier forwarding is entirely adequate and costs almost nothing. Use it, write it down, and review it occasionally.
Once you need to know how many calls arrived, who answered them, what they concerned and how long each person waited, forwarding has run out of road. That is a routing and reporting question, and omnichannel handling with live reporting is what replaces it.
Worth being clear about scope. TabaTalk sells cloud contact center technology rather than carrier services, so network-level forwarding sits with your operator. The platform holds no network and does not act as a carrier, and BYOC exists so a business can keep its existing operator and numbers while changing the software above them.
Frequently asked questions
What does the *#21# code do?
It checks whether unconditional forwarding is currently active on a mobile and shows the destination if so. Dialling it displays the current status rather than changing anything, so it is safe to use at any time, which makes it the quickest way to confirm whether calls are being redirected without your knowledge. Codes vary slightly between operators, so check yours. Checking periodically is sensible on shared or company-issued devices where several people have had access.
How do I turn call forwarding off?
Through the same route you turned it on: the handset menu, or the cancellation dial code your operator supplies. Each condition cancels separately, so switching off unconditional forwarding leaves any busy or no-answer rules running. That catches people out constantly, and a line can appear normal while a no-answer rule quietly persists. Check every condition, since assuming one action cleared them all is how rules survive, then confirm with the status code first.
What happens to a call that gets forwarded?
The caller hears normal ringing and usually has no indication the call moved, though some networks insert a short tone before it connects. The receiving phone rings as it would for any other call, and depending on the operator it may display the original caller’s number or the forwarding line’s. That inconsistency affects anyone who calls back, so check which your setup displays before assuming agents will see the customer’s number.
Does call forwarding cost anything?
Sometimes, and it depends entirely on your operator and destination. Several treat the redirected leg as outbound traffic, which means a landline redirected to an international mobile bills accordingly for every call. Others include it within a plan. Confirm the arrangement before setting up anything pointing abroad or running continuously, since these charges accumulate quietly and rarely appear as a distinct line on a bill.
Getting forwarding right is mostly administrative rather than technical. Write the rules down, give somebody responsibility, and check them on a schedule.
If you are working out whether your situation needs simple redirection or proper routing, speak to sales or book a demo. Bring a list of what currently forwards where, since that conversation usually answers the question by itself.
