AI · 9 min read
Why your AI receptionist should live inside your phone system, not beside it
Most AI receptionists never connect to your phone system. They answer from the outside, which is why so many offices try one for two weeks and turn it off, and why we install Arthur differently for SW Washington businesses.
Real integration means the AI receptionist is an extension on the phone system you already own. That is how we install Arthur, and it is how he answers our own phone at (360) 515-2500.
What does "inside the phone system" mean?
It means the AI is an extension on your PBX with a number of its own, the same as every phone in the building. The PBX is the box that runs your office phones, whether that is a Cisco router in the server closet, a 3CX install on a server, or an Avaya that has been humming along since 2009. It decides how calls get routed, transferred, parked and sent to voicemail. (Our PBX post covers the box itself; this one is about what plugs into it.)
Say the AI is extension 100. Your staff dial 100 to hand it a call, exactly the way they transfer to any other phone in the office. It dials their extensions to send calls back. It parks calls, queues them and does warm transfers, which means it briefs your team member before connecting the caller. As far as your business phone system is concerned, Arthur is one more phone on the system.
An AI that lives beside the PBX touches none of that. Calls forward out to the vendor's number, the bot takes a message or tries to redirect the caller, and your phone system never knows anything happened. The only thing joining the two is call forwarding.
The call-forwarding trap
Most AI phone answering vendors call forwarding their "integration." You set your PBX to send unanswered calls to their number. That sounds fine until you list what you give up.
The first thing you lose is real transfers. The bot cannot transfer a caller to extension 205 because it has no idea what extension 205 is. The best it can do is dial someone's direct line or cell as a brand new call. The caller sits on hold while it dials out, and if nobody picks up, the caller is stuck.
Call parking goes too. Parking puts a call on a shared hold slot so any phone in the office can pick it up. The receptionist at a busy Olympia law office does this dozens of times a day, and an AI outside the PBX has no access to your park slots.
So does three-digit dialing. Staff cannot dial 100 to send a caller to the AI. They need an app or a separate number instead, and anything that adds steps at a ringing front desk does not get used.
And the caller's context is gone. An AI on the PBX can say, "Hi Sarah, I have John on the line about last month's invoice, connecting you now." An AI on a separate number loses that somewhere between the two systems, and Sarah answers cold.
Why do office managers pull the plug on an AI receptionist?
Because the AI turned out to be a message-taker. We have talked with plenty of office managers who tried an AI answering service, ran it for a couple of weeks and turned it off. The reason is always some version of "it couldn't do what our receptionist does."
A person at the front desk transfers to any extension, parks calls, checks who is free and gives the caller a warm handoff. An AI outside the phone system can answer and take a message, and that is about it.
Most callers will not leave a voicemail anyway. They hang up and call the next name on the list, and a friendly voice does not change that. What keeps them on the line is getting through, whether that is a transfer to the right person, a parked call until someone is free, or a straight answer about the business. All of that needs the tools the human receptionist has, which is why the AI has to be inside the system.
Do you have to replace your phone system to get AI?
No. That is usually the first question from an owner in Centralia or Chehalis who has a perfectly good Cisco or 3CX system and no appetite for ripping it out.
Some cloud phone vendors are starting to build AI features in. Those features only work on that vendor's system, though, and you get whatever they decide to ship. If you run Cisco, 3CX, FreePBX, Avaya or analog lines, their receptionist needs their phone system, and the path to it is a full migration.
The businesses that get the most from an AI on the phones are the ones already running an on-premise PBX. A dental practice, law firm or auto shop with 10 to 75 people has enough call volume that missed calls cost real money, and not enough budget for a live person on the phones from 7am to 9pm. Those businesses need an AI that works with what is already installed, and that is how we build every phone system we sell and manage.
How the on-site gateway puts Arthur on your PBX
A gateway is a small device that sits next to your PBX and connects to the internet. It is how AI gets onto a phone system that was never designed for it. It bridges whatever your phone system speaks (the internet-based SIP lines modern systems use, or the older analog and PRI phone lines) to the cloud AI that handles the actual conversation.
Once the gateway is in place, Arthur registers as an extension on the PBX and becomes a native part of the system. The groups of phones that ring together can include him. Overflow rules can send calls to him after four rings at the front desk. Staff transfer to him with three digits, and he transfers back with the caller's name and reason for calling.
The PBX does not know or care that it is talking to AI. A fifteen-year-old Cisco system in a Longview clinic sees the same thing a brand-new 3CX install sees: another extension picking up calls and making transfers.
Setup is telecom engineering. There is no setup screen to click through. Our Cisco-certified engineers connect the gateway to your phone lines, register Arthur as an extension and build the call flows (who he transfers to, and when calls roll over to him). Arthur himself comes from Arthur Igloo, our AI arm. Most installs are live in about a week, and setup is included with a new Wallaby plan.
Five questions to ask any AI receptionist vendor
If you are comparing options, these questions separate real integration from marketing copy.
- Does it register as an extension on my PBX? If the answer is "no, but you can forward calls to our number," you are looking at call forwarding with a new name.
- Can my staff transfer to it by dialing three digits? If they need an app or a separate number, adoption will be low. The AI should work the way the phone system already works.
- Does it park calls and do warm transfers? This is what separates a receptionist from a message-taker.
- Which phone systems is it running on today? A vendor that says "works with any phone system" has not answered. Ask them to name platforms: Cisco, 3CX, Avaya, FreePBX, analog lines.
- Who does the installation? PBX integration is specialized work. The answer you want is "our own telecom engineers." If it is "you'll get a setup guide," you are the installer.
Arthur runs as an extension on our own Cisco system today and works with 3CX, Avaya, FreePBX/Asterisk and analog lines. The fastest way to check the rest is to call him.
What this means in SW Washington
Most businesses that ask us about an AI receptionist, in Olympia, Centralia or anywhere else in SW Washington, want to keep the person at the front desk. What they want covered is the gaps around that person: the 4:55pm call when the desk is already packing up, the lunch hour when nobody is there, the vacation week, the Monday rush. One dealer group's call data showed where those calls tend to end up: on a direct line to one person's desk, where they die unanswered.
An AI receptionist inside the phone system fills those gaps the way a second receptionist would. He answers, transfers, parks, takes a message and knows the business. He also texts or emails a summary of every call, so nothing sits in a voicemail box. An AI beside the phone system fills them the way voicemail would.
Arthur also rides on your phone system, which rides on your network, which sits behind your firewall. We run all three. Andrew Igloo, our AI network administrator, watches every layer around the clock from The Igloo in Tenino, so if the gateway drops or the PBX loses its line, we usually know before you do. A vendor that only sells the AI cannot see any of that.
The easiest way to judge any of this is to hear it. Arthur answers our phone at (360) 515-2500 around the clock, trained on our real business. Ask him about our services, ask to be transferred, or leave a message and hear how he handles it. If it sounds like something your front desk could use, book a free on-site assessment and we will map out how he would sit inside your phone system.
Questions, answered
What do SW Washington business owners ask about this?
What is the difference between an AI receptionist and an AI answering service?
An AI answering service usually takes calls on a separate number that you forward to, then takes a message and sends it on. An AI receptionist that lives inside your phone system, like Arthur from Wallaby Networks, is a native extension: it transfers calls to your staff, parks them, queues them and briefs your team before connecting. The first takes messages. The second does the job a receptionist does, 24/7, for offices across SW Washington.
Will an AI receptionist work with my existing Cisco, 3CX or Avaya phone system?
Yes. Arthur connects through a small on-site gateway that bridges your PBX to the AI, so he registers as an ordinary extension. He works with Cisco, 3CX, Avaya, FreePBX and Asterisk systems, and with analog and legacy lines. Your phones and extensions stay as they are, and we add Arthur to your existing ring groups and overflow rules. Most installs in SW Washington are live in about a week, and the setup is included with a new Wallaby plan.
Can I hear an AI receptionist before I buy one?
Yes, and we would rather you did. Arthur answers Wallaby Networks' own phone at (360) 515-2500 around the clock, so you can hear an AI receptionist that lives inside a phone system for yourself. Treat the call like a real one: ask a specific question, ask for a person, or leave a message. Listen for what a bolted-on bot cannot do: hand you to someone, and answer from real knowledge of the business. Offices anywhere in SW Washington can then book a free on-site assessment.
Does an AI receptionist replace my front desk staff?
Usually not, and for most SW Washington offices that is not the goal. Arthur covers the gaps a single receptionist cannot: after hours, lunch, sick days, vacation weeks and the Monday morning rush when every line lights up. Because he is an extension on the phone system, your receptionist can also hand him a call with three digits when the desk is swamped. Your team keeps doing the work that needs a person.
How long does it take to set up an AI receptionist inside a phone system?
Most installs are live in about a week. Our engineers place the gateway beside your PBX and register Arthur as an extension. Then they build the call flows (who he transfers to, when overflow routes to him, what he says after hours) and train him on your business. Setup is included with a new Wallaby plan, and our team keeps an eye on the gateway after go-live.