Test call forwarding

Test call forwarding before you depend on it. Dialing a code, or flipping a switch, only proves that your phone accepted the command. It does not prove a customer will reach the right place. The check is a call from a second phone, in each situation you think you turned on, with a note about who actually answered.

Do this on a quiet hour, with the destination number written down. If that destination is an AI receptionist, call it directly first and ask it one question you know the answer to. Fix that answer before you forward anyone. The steps below are carrier behavior you can observe. They are not a promise that every network matches Verizon or AT&T. Where a sentence depends on a specific page, the page is linked, and it was read on November 8, 2026.

What you need in front of you

You need three things.

• The phone that owns the business number. This is the one you programmed.
• A second phone, on a different line. Calling yourself from the same handset hides the bug.
• The number you forwarded to, written as ten digits. If you are not sure what you dialed, turn forwarding off and set it again. Guessing during the test wastes the test.

Write down who rang, who answered, and whether voicemail started. The conditional call forwarding page is the choice between every call and only the ones you miss. The checks below assume you know which one you meant.

Five calls that catch the real failures

Stop when a step fails. A later check is noise if the first one already went to the wrong place.

1. The destination, with forwarding still off. From the second phone, call the receptionist number itself. It should answer. If it does not, forwarding cannot succeed. No carrier code fixes a destination that does not pick up.
2. Your business number, forwarding still off. Call it from the second phone. The business phone should ring. If it does not, you are debugging the line, not the forward.
3. Turn the forward on, then call again. For an all-calls forward, the business phone should not ring. The destination should. For a no-answer forward, the business phone should ring and the destination should get the call only after you refuse it. If the business phone never rings and you thought you had set no-answer, you turned on all-calls instead. Verizon's wireless pages use *72 for all calls and *71 for busy or no answer. Other carriers differ. Do not "correct" a Verizon line with a code you saw for T-Mobile.
4. Busy. Be on a call, or be dialing out if that is how your carrier defines busy, and have the second phone call in. T-Mobile describes its busy forward as a call that arrives while you are dialing out. Test that case on T-Mobile, and do not assume "already talking" was the case they wrote down.
5. Unreachable. Turn the business phone off, or use airplane mode, and call from the second phone. Write down whether the destination answered, voicemail did, or the call failed.

Then turn forwarding off with that carrier's method and repeat check 2. The business phone should ring again. If it does not, something else is still forwarding, or Do Not Disturb, call blocking, or a focus mode is swallowing the ring. Verizon's page for turning forwarding off tells you to check those if *73 did not bring calls back.

When voicemail wins

This is the failure that looks like success. The setting says forwarding is on. Customers say they got your voicemail.

Voicemail and no-answer forwarding are both waiting for you not to pick up. The shorter timer wins. If voicemail starts first, the forward never runs.

Verizon's on page says conditional forwarding should send the call after 3 to 6 rings instead of to voicemail. If a Verizon test still hits voicemail, you are not getting the behavior that page describes. Turn it off, confirm a plain call rings the phone, and set *71 again. Then count the rings on the next test.

AT&T's wireless page, updated April 2, 2025, says forwarding overrides wireless voicemail, and that a busy destination means the caller hears a busy signal. The page does not list a star code. If an AT&T test still reaches voicemail, use their device steps and test again. A busy signal can mean the destination was busy.

T-Mobile's short-code page publishes a ring delay for the no-reply forward: 5, 10, 15, or up to 30 seconds, set on the no-reply code. If voicemail is faster than the delay you chose, lower the delay or turn voicemail off for that line, then retest. Their page is the source for those seconds. It is country specific and aimed at the primary SIM.

A busy tone is not one thing

A busy signal during setup and a busy signal when a customer calls are different events. Write down which moment you heard it.

On Verizon, the FAQ says the confirmation after you dial *73 to turn forwarding off can sound like a busy signal. That can mean the off command worked. Hang up, then call the business number from the second phone. If the business phone rings, the tone was the confirmation.

The same FAQ says customers hear a busy tone when the forwarded number was dialed wrong, often because extra digits were pressed. The number is not a working destination, so the call cannot land. Dial the forward again with ten digits and the area code, then repeat check 3.

On AT&T, a busy signal when someone calls you can mean the destination you forwarded to is busy. Their page says that directly. Calling the destination by itself, from the second phone, tells you whether it is busy or broken.

If the receptionist transfers callers back to the same number you forwarded, the call loops. Use a different phone for transfers, and listen for the greeting starting twice.

What this test does not prove

Send a text to the business number after forwarding is on. It should still arrive on the business phone. Verizon's FAQ says call forwarding does not forward texts.

The test does not measure the bill. Verizon says non-unlimited plans bill a forwarded call as if you had answered it. AT&T says forwarded calls are billed for their length and may include long distance or roaming. Both refuse international destinations. And a test call that gets a wrong price means the brief is wrong. Fix the brief before you trust check 3. The receptionist should say it is an AI, answer from that brief, transfer to your team, or take a message.

Write the result in one place

Keep a few lines with the date:

• Carrier, and whether the line is a mobile or a desk system.
• Which code or menu you used, and the ten-digit destination.
• All-calls, no-answer, busy, and phone-off: who answered, and about how many rings.
• Whether a text still arrived.
• The code or menu that turned it off, and that a later call rang the business phone.

That note is the whole troubleshooting record. When forwarding "stops working" next month, you can see whether the phone, the code, or the destination changed. The guide to forwarding the business number is the setup those notes belong to. Repeat this checklist after a new phone, a new SIM, or a change to voicemail.

RingKit's current number charge and per-minute rate stay on the pricing page. Passing this checklist does not change them. Setting the receptionist up over the API, if that is how the line was created, is in the docs. The test itself is still two phones and a piece of paper.