Guide
AI receptionist for businesses with locations: what to automate and what to keep for people
A practical rollout guide: what an AI receptionist should handle on its own, what should wait for a person, the information it needs per location, a handover rule you can copy, and the numbers to watch.
Key takeaways
- Automate the requests with a clear answer: hours, directions, availability, booking, simple changes.
- Write the handover rule before launch. What waits for a person is a business decision, not a software setting.
- An AI receptionist is only as good as the information it answers from, and that information is per location.
- Pilot two or three locations alongside your team, then roll out in groups.
- Measure speed to first reply, bookings made, conversations handed over and missed calls recovered, per location.
Start from the questions, not the software
For a business with several locations, an AI receptionist should answer the routine requests (hours, directions, availability, booking, changes) from each location's own information, and hand everything else to a named person at that location. Decide that split from a month of real calls and messages before you choose or configure any software.
If you want the definition first, read what is an AI receptionist, or the plain-English explainer on how AI receptionists work. This guide is the next step: you run several locations, calls and messages go unanswered when the desk is busy or closed, and you want to decide what to hand over.
Pull one month of calls, messages and forms for a few locations and sort them into types: opening hours, directions, price, availability, booking, change or cancel, complaint, something unusual. Most locations find that a few types make up most of the volume. Those are the ones to automate first.
What to automate, and what to keep for people
| Request | Automate? | Why |
|---|---|---|
| Hours, directions, parking | Yes | A fixed answer from the location's own data. |
| Availability and booking | Yes, with a confirmation in writing | The system can check the calendar and confirm. |
| Quote or rate for a standard service | Yes, if the rate is published | Answer only what the business has set. |
| Change or cancel a booking | Yes, within the rules you set | Define the cut-off and the fee in advance. |
| Complaint, refund, safety or medical concern | No: hand over to a person | Judgment and accountability sit with a person. |
| Anything the data does not cover | Hand over, with the conversation attached | A guess is worse than voicemail. |
- Is the answer in the location's own information?NoHand over to the named person, with the conversation attached.Yes
- Is it free of complaint, refund, safety, medical or legal content?NoHand over now. A person owns these.Yes
- Is it within the rules you set (cut-offs, fees, booking limits)?NoHand over, or offer a callback at a set time.YesAnswer, book or change it, and confirm in writing.
In healthcare, financial services and similar settings, decide with your compliance team what an automated assistant may say and collect. Keep clinical or advice questions with a person. See what an AI receptionist should never answer on its own.
The information it needs, per location
The receptionist answers from a record per location. If the record is wrong, every answer is wrong, at every hour, on every channel. Fill it in before launch and give each location an owner.
Per-location information checklist
This is the same set of facts your listings and profiles need to carry. Keeping it right once helps both. See listings management for multi-location brands.
Write the handover rule before launch
The handover rule says what the receptionist must pass to a person, to whom, how fast, and what it tells the customer meanwhile. Write it down per location type, agree it with location managers, then load it. Copy this and fill it in.
Location: {location name}
Handover owner: {role}, {hours}. Backup: {role}.
Always hand over:
- complaints, refunds, billing disputes
- safety, medical, legal or advice questions
- anything not in this location's information
- any customer who asks for a person
How: {phone transfer / message to inbox / callback request}
Target time to pick up: {e.g. 15 minutes in opening hours; next opening hour otherwise}
What the customer hears:
"Thanks, {first name}. I've passed this to {role} at {location}, who will {call / message} you by {time}. Your reference is {ref}."
Review: {owner} reads all handed-over conversations every {day}.Keep the list of "always hand over" topics short and clear. Add to it after the pilot, not before.
Roll it out in four steps
- Pick two or three locations
Choose a mix: a busy one and a quiet one. Learn before you scale.
- Load each location's information and set the handover rule
Decide what runs on its own and what waits, and who receives it.
- Run it alongside your team for a few weeks
Read the conversations. Fix gaps in the information, not in the wording.
- Extend location by location
Roll out in groups. Keep one inbox for head office so every conversation is visible.
- Week 1
Sort a month of calls and messages; write the handover rule; fill in the pilot locations' records.
- Weeks 2 to 4
Pilot runs alongside staff. Read every handed-over conversation; fix missing information.
- Weeks 5 to 6
Add channels one at a time: calls, then WhatsApp, website chat, forms and email.
- Month 2 onward
Roll out in groups of locations; review the four numbers monthly.
Channels matter. Calls are where most missed demand is, but many customers prefer to message. Add WhatsApp and website chat once the call flow is stable, and set up missed call text back so a call that goes unanswered still starts a conversation.
What to measure
Four numbers per location: the time to first reply, the number of bookings made, the number of conversations handed to a person, and the number of missed calls recovered. Speed matters: a Harvard Business Review study of online leads found that firms contacting a lead within an hour were about seven times as likely to qualify it as those that waited longer (HBR, 2011). See how fast a business should reply to a lead and lead response time.
| Metric | What it tells you | Watch for |
|---|---|---|
| Time to first reply | Whether customers wait | Locations or hours where it rises |
| Bookings made | Whether conversations turn into business | Locations with many chats but few bookings |
| Handed over | How much still needs a person | A rising share means missing information |
| Missed calls recovered | Demand saved that used to go to voicemail | Locations where staff never pick up |
Pair this with call tracking so you can see which listing or ad produced each call, per location.
Mistakes to avoid
Mistakes to avoid
- Launching on every location at once
Instead: Pilot two or three locations, fix the information gaps, then roll out in groups.
- Letting it guess when the data is missing
Instead: Hand over with the conversation attached. A wrong answer costs more than a short wait.
- One brand-wide information record
Instead: Keep a record per location: hours, services and prices differ.
- No named owner for handovers
Instead: Name a role and a backup per location, with a target pick-up time.
- Judging it by call volume alone
Instead: Track bookings, handovers and recovered missed calls per location.
Desk is the AI receptionist for every locationDesk by Locus Intelligence answers calls, WhatsApp, website chat, forms and email from each location's own information, books appointments, hands over by your rule and texts back missed calls.
Check what callers see first
Before a customer calls, they usually see the location's Google profile. If the hours or phone there are wrong, no receptionist can fix the call that never comes. The free audit scores the profile and shows the fixes that matter most.
Scores a location's profile and shows its Maps rank against the top three, with the fixes that matter most.
Comparing products? Our buyer's guide to the best AI receptionist lists what to check, and is an AI receptionist the same as an answering service explains the difference.
Free. You get a profile score, your Maps rank against the top 3, and the fixes that matter most.
Your next steps
Today
- Export last month's calls and messages for two locations.
- Run the free Google Business Profile audit for those locations.
This week
- Sort the requests into types and mark after-hours ones.
- Write the handover rule using the template above.
- Fill in the per-location information checklist for the pilot.
This month
- Run the pilot alongside staff and read every handover.
- Add missed call text back and one messaging channel.
- Review the four numbers and pick the next group of locations.
Frequently asked questions
Can an AI receptionist handle several locations at once?
Yes, if it answers each conversation from that location's own information and hands over to that location's named person.
What should an AI receptionist never handle alone?
Complaints, refunds, safety, medical, legal or advice questions, and anything not in its information. See what it should never answer on its own.
Will an AI receptionist replace my front desk staff?
It takes the routine and after-hours load. Staff keep the conversations that need judgment, and get the full history when one is handed over.
How long does a rollout take?
A pilot on two or three locations usually runs a few weeks. Rolling out to the rest goes in groups, at the pace you can fill in each location's information.
Can it book appointments?
Yes, when it is connected to a live calendar or inventory and you set the rules for cut-offs and deposits.
Never miss another customer.
Start with a free audit. See what each location is losing, and where.
Profile score, Maps rank against the top 3, and the fixes that matter most.
Or book a demo- Role-based access by region and brand
- Every action logged and reversible
- Nothing customer-facing goes live without approval