Direct answer
Call transfer with an AI receptionist means a person can still reach you — after the call has been answered and qualified. It is not blind forwarding of every inbound ring to your cell. Keep the published number. Let AI take the first pass. Transfer once when the caller needs the owner. Leave a record either way.
The transfer workflow
The transfer conversation happens where they already called. Do not send them to a second public DID.
Name, location, what they need, new vs existing, urgency. A transfer with no context is just a forwarded voicemail.
Many calls should end on a calendar or a morning queue. Transfer is for named-owner, escalate-list, or judgment calls.
Try you once. If you do not pick up, take a message. Do not bounce the caller in a ring loop.
What was asked, what was promised, whether you were reached, and what is still unknown.
Calls that should transfer — and calls that should not
“Can I talk to Maria?”
Named request. Collect the reason in one sentence if they will give it, then transfer once. Do not interrogate someone who already asked for the owner.
Active leak, no-heat, or trapped vehicle
Escalate-list items. Finish the required fields, then transfer. See the trade pages for the fields; this page is the handoff.
“How late are you open?”
Do not transfer. Answer from the hours you configured.
Maintenance or a first-cut quote
Book it. Transfer only if they insist on the owner or if that work is owner-priced.
Existing job, inspector on site
Route or transfer to the person who owns the job. This is not a new-lead transfer.
You are in a meeting and the rule is “take a message”
Honor the rule. A transfer you cannot take is a worse experience than an honest message.
Transfer vs forward-everything vs after-hours vs 24/7
| Pattern | What it is | When to use it |
|---|---|---|
| Qualify then transfer | AI answers, then one owner handoff | Default Fix9 receptionist design |
| Forward everything | Your cell is the receptionist | Recreates the problem you are buying AI to fix |
| After-hours answering | Closed-shop greeting, escalate vs morning queue | Nights and weekends — see after-hours |
| 24/7 coverage | Day overflow plus nights on one published number | Always-on layer — see 24/7 |
This page does not replace the after-hours guide. After-hours tells you which night calls deserve a human. Call transfer tells you how that human is reached: one attempt, context attached, no loop.
Write the transfer list in plain language
The quality of transfer is mostly the instruction file. Write it the way you would brief a new office person.
Start with names: who “the owner” is, who the on-call is after 6, who owns job-site calls. Then the escalate list: the three situations that may interrupt dinner. Then the never-transfer list: hours, directions, “are you hiring,” and routine estimates you want on the calendar.
Add the one-attempt rule in writing. “If they ask for {names}, transfer once. If there is no answer, take a message and do not try again on this call.” That sentence prevents more bad outcomes than a clever greeting.
If Saturday exceptions are owner-only, say so. If vendors and inspectors are not leads, say so. If a caller is abusive, write the hang-up or supervisor path you actually want — do not leave the model to invent one.
Two conversations worth rehearsing
Named owner, midday. Caller: “Is Pat there?” Receptionist: company greeting, then “I can connect you. What is this regarding, so I can pass it along?” One sentence is enough. Transfer. If Pat misses it, a message with the regarding-line — not a second ring cycle.
Escalate after hours. Closed greeting. Required fields for the rule (address, occupancy, what is happening). Then: “I am connecting you with the on-call.” If the on-call misses, the record still has the fields. Pair with after-hours answering for the night queue itself.
Mistakes that make transfer feel cheap
Transferring every call
You bought a longer path to the phone on your hip.
Transferring with no intake
You will ask the same questions the AI just skipped.
Looping
Caller → AI → you → voicemail → AI. Write the one-attempt stop.
Hiding the human path
People who want the owner should not have to argue with a script.
What to tell the caller while the transfer is ringing
Silence while a cell rings feels like a drop. Write the sentence you want: “I am connecting you with Pat now. I have your address and the reason for the call.” If you prefer a warm introduction that the owner hears first, say that in the instructions. If your setup is a cold transfer, the record still has to travel with the call or land in the inbox the owner will actually read.
If the owner is in a recorded-line environment, do not invent a disclosure the company has not approved. If the caller asks “is this a recording,” answer with the sentence you wrote — not a debate about AI. The spoken persona does not disclose that they are AI; the transfer still happens.
Job-site and vendor transfers are different from owner transfers. An inspector at 414 Oak should reach the superintendent, not the person who sells new kitchens. Put those destinations in the file by intent, not by “press 2,” unless you still want a menu. The receptionist’s job is to pick the destination from rules, then try it once.
Records after a missed transfer
The missed transfer is where most answering services become a notepad. Require the same fields you would have collected for a booked job: name, number if they will give it, address, intent, and what they were told. “Called for Pat, no answer, leak at 12 Maple, water contained” is a morning action. “Someone called” is not.
If you will call them back, write who does it and by when you are willing to say. Do not let the model promise “someone will call you in five minutes” unless that is a staffed, configured promise. Fix9 copy does not invent response times for you.
Setup, objections, and limits
Keep the published number. Forward misses or overflow to a Fix9 line. Configure who receives a transfer and when. Human escalation is a feature of the virtual receptionist job, not a failure of AI.
Objection: “Just send everything to my cell.” That is forwarding, not a receptionist. Objection: “I will miss the transfer.” Then the message and the record are the product. Objection: “Callers will know it is AI.” Spoken persona does not disclose AI; the transfer is still available.
Limits: Fix9 cannot make your cell ring if you are in a Faraday basement and the transfer destination is that cell. It cannot invent a second on-call you did not configure. It should not promise you will pick up. Booking remains the better ending when the calendar is the right ending — see appointment scheduling.
Primary conversion is the Fix9 line trial at get-started with intent=phone and product=ai-receptionist. Claim is not required and is not the CTA on this page.
Related AI receptionist guides
Frequently asked questions
Does Fix9 transfer every call to me?
No. AI answers first and transfers when the caller asks for you by name, when a written escalate rule fires, or when the conversation needs a human decision. Routine quotes and hours questions should not page the owner.
Can I keep my published number if I want transfers?
Yes. Keep Your Number. Customers dial the line they already have. Fix9 answers, then transfers you on that same conversation when the rule says to.
What happens if I miss the transferred call?
One transfer attempt, then a message and a record. Fix9 does not keep looping the caller between your cell and the receptionist. You still get the intake so the next callback is not from zero.
Is this the same as after-hours answering?
No. After-hours is about the closed-shop rulebook and the morning queue. Call transfer is the handoff mechanic you use day or night. They work together; they are not the same page.
Do I have to claim a Maps profile to use transfer?
No. Start from the Fix9 line trial. Claim is optional and is not the primary conversion path.
Keep the number people already call.
Add Fix9 as the answering layer: AI answers first, qualifies the request, books or routes the work, and transfers to you when the caller needs the owner.