How to forward a business phone to an AI receptionist
Set up conditional forwarding on the client's existing line so the shop phone rings first and the AI answers when nobody does. Here are the codes, the setup order, and where forwarding falls short.
Lumina··8 min read
Set up conditional call forwarding on the client's existing business line, point it at the number the AI receptionist answers on, and test it with the client in the room. Conditional means the forward only fires when the line is busy, unanswered or unreachable. That keeps the number on the vans, keeps the phone ringing at the shop first, and puts the AI behind the humans instead of in front of them. It takes about ten minutes on a mobile line. It can take a few days when the client's phone service is a landline or a hosted VoIP system.
This is the step agency owners underplan most. The build can be perfect and still never answer a call because nobody finished the carrier side. Here is how I would handle it, what the codes look like, and where forwarding falls short.
AI agency software for sales and fulfillment
Custom fulfillment from our engineering team, live AI demos, and a client portal, all 100% white-labeled.
What are the three ways to route calls to an AI receptionist?
You have three choices, and they trade risk for control.
Conditional forwarding. The business phone rings first. If nobody picks up, the line is busy, or the phone is off, the carrier sends the call to the receptionist. This is where I start nearly every time. Nothing about the client's setup breaks if you switch it off.
Unconditional forwarding. Every call goes to the receptionist and the client's phone never rings. Good for a closed office, a holiday, or a client who wants the AI to screen everything. Bad as a default, because the owner loses the ability to grab a call they want.
Porting. The client's number moves to the platform and the AI answers it natively. You get the cleanest result and the most risk. We covered why a main line is usually the wrong first move in what happens after your client signs.
Start with conditional. Prove it on real calls for a couple of weeks. Then decide whether the client needs anything heavier.
What are the codes for conditional forwarding?
On most US mobile lines you dial a short code from the phone, and the carrier does the rest. ElevenLabs documents the standard set in its receptionist call handling guide, with the receptionist's number in place of the placeholder:
Unanswered calls: **61*<number>#
Busy line: **67*<number>#
Phone off or unreachable: **62*<number>#
Every call: **21*<number>#
Turn forwarding off: ##002#
Verizon is the exception. The same guide says Verizon uses *71 for busy or unanswered calls and *72 for all calls. A separate rundown from Quo on conditional forwarding lists *73 as the Verizon cancel code and notes that T-Mobile wants a leading 1 before the number. It also says AT&T does not publish wireless codes of its own and appears to use the standard ones above. I would treat any code table as a starting point and confirm on the client's actual phone, because carriers and the budget resellers that ride on them sometimes remap things.
One more catch from the Quo piece. The iPhone's built-in forwarding setting only does unconditional forwarding. To forward only on no answer, you still dial a carrier code.
How do you set it up without breaking the client's phone?
Here is the order I follow on go-live day.
1. Get the destination number first. Before anyone touches a carrier setting, you need the number the receptionist answers on. The build has to be finished and tested on that number. If you forward a real line to something half built, you will find out from an angry caller.
2. Ask who controls the phone service. Is it a mobile plan, an office landline, or a hosted system like a cloud PBX? The answer decides everything in the next three steps. This is a question for the discovery call, not for the morning you plan to flip the switch. It sits in the same bucket as the items in the client intake checklist.
3. Dial the code from the business phone, with the client present. Do not do this by remote description. Have them dial it on their own handset so you both see the confirmation tone or message.
4. Test all three conditions. Call the line while it is busy. Call it and let it ring out. Call it with the phone off or in airplane mode. A forward that works on no-answer and fails on busy is common.
5. Time the rings. Quo says no-answer forwarding typically waits three to six rings. ElevenLabs says the carrier decides the count. Call it yourself and count. If the shop's voicemail greeting picks up before the forward fires, the AI never gets the call, and you need to shorten the client's voicemail ring time or turn voicemail off.
6. Run the full test pass. Use the same fixed set of calls from testing before going live, and read the logs after each one, not just your memory of how it sounded.
7. Write down how to turn it off. Put the cancel code in the client's portal notes or in your handoff email. If the owner gets nervous at 4pm on a Friday, they should be able to kill the forward in ten seconds without calling you.
What if the client has a landline or a VoIP phone system?
The codes above do not apply. ElevenLabs is direct about it: landlines and internet phone systems are configured through your provider's settings, not by dialing a code.
In practice that means a login to the client's phone provider, or a call to their support line. Some hosted systems have a "no answer destination" or "after hours routing" field where you paste the receptionist's number. Some carriers charge for forwarded calls, which ElevenLabs flags too. Others make you open a ticket.
Plan for an extra day or two, and ask the client for the account owner's contact up front. In small offices the person who set up the phone service left three years ago and the login is on a sticky note somewhere.
What can forwarding not do?
Here is where I would be honest with the client before they sign off.
Forwarding is a workaround. The call still lands on their carrier first, and you inherit whatever that carrier does. Three limits matter.
You cannot schedule it on a plain mobile plan. Quo notes that forwarding cannot be scheduled on those lines, so "evenings and weekends only" means someone turning it on and off by hand, or a hosted phone system that supports business-hours rules. Many owners forget to flip it back and wonder why the shop phone stopped ringing.
Texts do not follow the call. Quo says texts do not follow the forwarding rule. If the client expects missed-call text-back to work off a forwarded mobile line, check how the build actually handles it before you promise it, and keep in mind the carrier registration queue that sits behind any texting feature.
And the ring delay is a real cost. A caller who hears five rings, then a handoff, may already be gone. A roofer with a burst pipe call does not wait. If that matters for the client's trade, shorten the ring count where the carrier allows it.
If a client needs the AI on every call with no ring delay, forwarding is the wrong tool. That is a porting conversation.
When does porting make sense?
When the client wants the AI to answer natively and is willing to wait. Twilio's support page on US ports says a port typically lasts from 5 to 15 days, but it can take up to 4 weeks or longer because of carrier rejections, and that a rejection can add another two to four weeks after it is resolved. It also requires proof of ownership, such as a utility bill, and a signed letter of authorization from the account's authorized representative.
That is the whole reason I do not start there. During a port the number can sit in limbo, and a small business that runs on one phone line cannot afford that. Run forwarding first, collect a month of real calls, and port later only if the data says you need to.
FAQ
Does the client have to keep paying for their phone line?
Yes, with forwarding. The line stays with their carrier, and the carrier may charge for forwarded minutes. Check the plan before you promise the owner nothing changes on the bill.
Will callers know the call was forwarded?
Usually the caller just hears ringing and then the receptionist greeting. What they hear in between depends on the carrier. Test it on your own phone so you know what the owner's customers hear.
Can I use forwarding on my own demo?
Your demo site needs no forwarding at all. Prospects call the receptionist from the page, in a sandbox. Forwarding only matters once you deliver a build for a client.
What if the forward stops working a month later?
Someone changed the phone plan, replaced the handset, or reset the settings. Keep the cancel code and the activate code in the handoff notes, and put a quick test call in your monthly check-in.
What to do next
Add one question to your close call: "Who pays the phone bill for the line customers call, and is it a mobile plan, a landline or a hosted system?" Write the answer on the order before you book the pricing call on the fulfillment platform. If you have not started yet, open an agency workspace and run your first prospect through the demo before you worry about carrier codes.