How to Set Up Call Forwarding for Your Trade Business

A customer calls your main number at 6:14 p.m. after a failed furnace start. The office is closed, the technician is driving, and the caller reaches voicemail. By the time someone returns the call, the customer may already have hired another company.

That's the situation call forwarding is meant to prevent. The setup looks simple, but trade businesses often lose calls because the forward is active at the wrong carrier level, attached to the wrong SIM, pointed at a badly formatted number, or never tested beyond the initial confirmation tone. The reliable approach is to verify the complete chain, from the customer's dial tone to the person or AI receptionist that answers.

Table of Contents

• Why Call Forwarding Is the Fastest Path to 24/7 Call Answering
• Activating Call Forwarding on Your Line
  • Carrier lines
  • iPhone
  • Android and hosted systems
• Testing the Forward End to End
  • The practical test sequence
  • Test the failure conditions
• Setting Time-of-Day and After-Hours Rules
  • Match the rule to the operating problem
  • Build the schedule around call urgency
• Troubleshooting Silent Forwarding Failures
  • When the phone looks normal but calls still divert
  • When the wrong device answers
  • When the destination rejects the call
• Verifying Full Integration with Mercateer

Why Call Forwarding Is the Fastest Path to 24/7 Call Answering

A plumbing company usually doesn't need a new phone number to improve coverage. Customers already have the shop's existing number saved, printed on invoices, and associated with the local service area. Replacing that number creates unnecessary disruption. Forwarding lets the business keep the number customers recognize while sending calls to an available destination.

Call forwarding has been a standardized North American telephony feature for a long time. On many carrier lines, *72 activates forwarding for all calls and *73 cancels it, as documented in the history and operation of call forwarding. The practical advantage is that the network redirects the call before the original handset rings, so the business can use an existing carrier line, VoIP number, office phone, or cell phone without adding hardware.

Consider an HVAC owner who wants daytime calls to ring the dispatcher but needs after-hours calls handled when the dispatcher leaves. The owner can forward the published number to a reception service at closing, then restore the daytime route in the morning. The customer still dials the same number, while the receiving system can collect the issue, apply the company's pricing rules, and place the job on the calendar.

That no-new-hardware bridge is why call forwarding remains useful even in modern VoIP environments. Older PBX and carrier systems used forwarding rules long before cloud phone platforms, and enterprise systems can retain forwarding targets and timestamps in call-history records. For a trade business, the value isn't the code itself. It's the ability to connect a trusted number to an answering service for contractors without porting the number or rebuilding the daytime phone setup.

Practical rule: Forward the number customers already know, then test the destination as if you were a new customer with an urgent problem.

Activating Call Forwarding on Your Line

Start by identifying where the number is controlled. A mobile handset may display a forwarding setting, but the carrier switch can still control the actual route. A VoIP number usually depends on a web portal, while a digital PBX may apply rules to an extension, hunt group, or main line.

Carrier lines

For many North American carrier lines, the common unconditional-forwarding process is:

1. Pick up the business phone and dial *72.
2. Enter the destination as the full 10-digit number.
3. Wait for the confirmation tone or message before hanging up.
4. Call the main number from another line and confirm that the destination rings.

The confirmation matters because dialing the code alone doesn't prove that the forward reached the carrier switch. To cancel the rule, dial *73 where your carrier supports that pattern. Some providers use different codes or require forwarding to be enabled on the account, so a failed confirmation should lead to a carrier check rather than repeated guessing.

iPhone

On an iPhone, open Settings, select Phone, then choose Call Forwarding. Turn the feature on and enter the destination number. This device path commonly controls unconditional forwarding, meaning every incoming call is sent away from the iPhone instead of ringing the handset first.

If the option is missing or unavailable, the carrier may not expose the feature through the iPhone interface. In that case, use the carrier's supported code or account portal.

Android and hosted systems

Android menus vary by manufacturer. Open the Phone app, enter Settings, and look for Calling accounts, Supplementary services, or Call forwarding. Choose the relevant SIM, select the forwarding mode, enter the destination, and save it. Don't configure the wrong SIM on a dual-SIM phone, because the business line may continue routing normally while a personal line carries the rule.

For a VoIP portal, sign in to the administrator dashboard and open the call features, call handling, or forwarding area. Enter the target number exactly as requested, often as digits only with no spaces or special characters, then save the rule. A digital PBX typically uses a similar path through the admin panel, where you select an extension or main route and define destinations for always, busy, or unanswered calls.

The system is only activated when the rule is saved at the level that receives the inbound call. A handset setting won't fix a PBX rule, and a PBX rule won't fix a carrier route that's still forwarding elsewhere.

Testing the Forward End to End

Activation is not verification. The most common field failure is a setup that produces a confirmation tone but doesn't deliver a usable customer experience. The destination might ring too late, show the wrong caller ID, reach voicemail, or route to a different line entirely.

Use a separate phone for the test. Calling the business number from the same handset can hide routing problems because the device may treat the call as an internal event or fail to reproduce the external carrier path.

The practical test sequence

1. Call the published business number from a second mobile phone or landline.
2. Listen to the ringback and destination behavior. Confirm that the call leaves the original line and reaches the forwarding target.
3. Answer at the receiving system. Check that the greeting sounds like the business, not a generic carrier announcement.
4. Speak a realistic request. Use an actual scenario, such as a leaking water heater, a no-heat call, or a panel that has lost power.
5. Check the resulting record. Confirm that the receiving platform creates the expected summary, transcript, booking, or technician notification.

For an AI receptionist connected through forwarding, the test should continue past “someone answered.” Confirm that the agent identifies the business, gathers the service address and job details, follows the company's price-book rules, and offers the correct scheduling path. A call that technically connects but produces no usable record still leaves the office with manual recovery work.

Test the failure conditions

Conditional rules need their own tests. Let the line ring without answering, place the line on another call, and test with the business phone unavailable. Each scenario should reach the destination assigned to that rule. A forwarding setup that handles an unanswered call can still fail when the line is busy or unreachable.

Test messaging separately if the service includes missed-call text-back. Send a message to the configured number or create a missed call, then verify that the response reaches the customer and that the interaction appears in the same operational record. The point is to validate the whole customer path, not just the phone switch.

Setting Time-of-Day and After-Hours Rules

Always-forward is appropriate when the office is fully remote or the published line should go directly to an answering system. Most trade shops need more control. The dispatcher should answer routine calls during working hours, while unanswered, busy, and after-hours calls should follow a defined backup route.

Match the rule to the operating problem

Always forward sends every call to the destination. Use it for a closed office, a temporary relocation, or a number that should operate remotely throughout the day.

Forward on busy catches calls when the primary line is already occupied. It's useful for a small plumbing office where one person is taking a customer's payment while another caller needs immediate help.

Forward on no answer waits for the configured ring threshold, then redirects the call. This suits a shop where the dispatcher should have the first opportunity to answer but shouldn't force every caller into voicemail when the desk is unattended.

Forward when unreachable handles conditions such as a switched-off device, lost signal, or another carrier-defined failure state. It can provide a separate safety net for a mobile-based business line.

Build the schedule around call urgency

An HVAC company handling a no-heat call during a cold evening may want the after-hours route to answer immediately, qualify the emergency, quote the applicable after-hours rate, and escalate according to the on-call policy. A plumber dealing with a burst pipe needs a similar path, but the agent should distinguish an active emergency from a routine faucet repair that can wait for the next available appointment.

During daytime hours, use busy and no-answer rules as overflow protection. At closing, switch to an always-forward rule or a scheduled after-hours route. A service such as after-hours answering for trade businesses can sit behind that route, while the office's existing number remains unchanged.

Pay close attention to the ring threshold. If the rule waits too long, callers may abandon the call before the backup answers. If it forwards immediately, the dispatcher loses the chance to handle simple requests directly. Save the threshold explicitly in the portal, then test it with a stopwatch and a second phone.

Microsoft's reporting model shows why this configuration needs review rather than a one-time setup. Teams PSTN and SMS usage reports can be viewed over 7 days, 28 days, or a custom date range, with activity visibility potentially delayed by 24 to 48 hours according to Microsoft's PSTN usage report documentation. Microsoft Graph call-record queries also use a maximum 90-day range, so export or review the relevant call history before older routing patterns disappear from the query window.

Troubleshooting Silent Forwarding Failures

The handset is not always the source of truth. A carrier-level forward can remain active at the network switch even when the phone's settings appear disabled. That's why a customer may still be redirected while the owner sees no obvious forwarding icon.

When the phone looks normal but calls still divert

Clear the forwarding rule using the carrier's supported cancellation method, then reapply the intended destination. Place a test call after each change. If the old target continues receiving calls, ask the provider to inspect or reset the switch-level configuration, as Bell's forwarding troubleshooting guidance notes that carrier-side settings may require provider intervention.

When the wrong device answers

Dual-SIM phones store forwarding rules per line. Select the SIM attached to the business number before activating or editing the rule. Then check the destination itself for blocking, voicemail interception, or another forwarding rule that could redirect the call a second time.

On newer iPhones, Live Voicemail can interfere with the expected path by answering locally before the forwarded destination receives the call. Disable or adjust that feature during testing, then repeat the call from a separate phone.

When the destination rejects the call

Check the destination number's format, including any required country code. Hosted PBX portals may reject spaces, punctuation, or an internal extension entered where a full external number is required. If the number is valid but the forward still fails, confirm that the receiving line accepts calls from the carrier and that the destination has an active calling plan.

The reliable fix is isolation: remove every existing rule, apply one destination, test it, and add conditional logic only after the basic route works.

Verifying Full Integration with Mercateer

A forwarded call is only successful when the complete workflow works. Confirm that the AI receptionist answers, creates a conversation summary and searchable transcript, follows the shop's actual price-book rules, and writes bookings to the calendar. For paper schedules, verify that the booking details and summary reach the responsible technician by text.

Review answer rate, jobs booked, and after-hours volume during the first operating period. Compare the reception dashboard with carrier call history. The carrier record shows whether the call reached the destination, while the dashboard shows what happened after pickup. Allow for reporting latency before judging recent activity.

Test the rest of the chain, too. Place a missed call and confirm that text-back recovery fires, then check whether the follow-up conversation remains attached to the customer record. Run a weather-spike scenario, an urgent no-heat request, and a routine booking. Each should produce the intended triage outcome.

Mercateer's trade-business reception platform supports forwarding from existing carrier, VoIP, and cell-phone setups, with call handling, quoting, booking, summaries, and transcripts. Verify the route from the customer's dial tone through the carrier, destination device, AI receptionist, and final calendar or technician notification. A call that rings correctly but fails to create the next record is still an incomplete setup.