You run several branches, or you sell the right to run them. Each one answers the phone a little differently. Some are brilliant. Some miss calls at the busiest hour, and a customer who rang one branch gets a different answer from the next.
That inconsistency is where AI can genuinely help. It is also where it can quietly damage a brand if it’s rolled out carelessly. Here is how I’d think about it.
Where does AI actually help a franchise?
AI helps most with the repeated, predictable work that every branch does every day. In a franchise, that work is nearly identical from branch to branch, which makes it a good fit.
- Answering calls and messages when staff are busy, closed or with a customer.
- Taking and changing bookings against each branch’s real availability.
- Giving the same answer everywhere on opening hours, services, policies and how things work.
- Passing the right message to the right branch so nothing sits in a shared inbox.
What it doesn’t do well is judgement. Complaints, refunds, anything clinical or legal, and anything that needs a person to read the room should go to a person.
Can one AI assistant answer for every branch?
Yes, one assistant can answer for every branch, as long as it knows which branch the customer means and what’s different about it. The brand voice and core answers stay the same. The local details change.
Before you build anything, write down what is shared and what is local:
- Shared: the brand’s tone, services, standard policies, how bookings work.
- Local: address, parking, opening hours, staff names, which services that branch actually offers.
If a customer rings a single number, the assistant should ask which branch, or work it out from what they say, then answer from that branch’s details. If each branch has its own number, it can greet the caller as that branch from the first word.
When I built Zeena, I gave her a database that remembers every person she speaks to and a workflow engine with 43 automatic steps, of which one run fires 39. That’s the kind of plumbing a multi-branch setup needs: the conversation is the easy part; routing the right information to the right place afterwards is where the work is.
What should stay with people?
Anything where a wrong answer costs trust, money or safety should stay with a person. The AI’s job is to recognise those moments and hand over cleanly.
I’d keep these with your team:
- Complaints and anything a customer is upset about.
- Refunds, disputes and pricing exceptions.
- Health questions of any kind. If your franchise is in healthcare, aesthetics or fitness, the assistant should say it’s an AI, never give medical advice, and pass clinical questions to a qualified person.
- Anything a franchisee has agreed locally that isn’t in the shared playbook.
A good handover tells the customer what happens next and who will call them back, then sends the branch a clear summary so nobody has to ask the customer to repeat themselves.
Who should own it: the franchisor or the franchisees?
In most cases the franchisor should own the assistant and the shared answers, and each franchisee should own their local details. That keeps the brand consistent without making head office the bottleneck for every change to opening hours.
Agree these points in writing before rollout:
- Who can change the shared answers, and who signs off.
- Who can change local details, and how quickly.
- Who sees the call records and customer data for each branch.
- What happens to that data if a franchisee leaves the network.
Data is the one to take seriously. Customer details collected by the assistant are likely to count as personal data, and the franchise agreement may already say who controls what. Check your position with the ICO and your own legal adviser rather than assuming. If you’re in a regulated sector, check with your regulator too, whether that’s the CQC, GPhC or GDC.
What should I ask before rolling it out across branches?
Ask questions that test how it behaves on a bad day, not a good one. Whoever builds it, these are worth getting straight answers to:
- Can I hear it answer as my business before I commit? You should be able to hear it, not just read a script.
- What does it do when it doesn’t know? The right answer is that it says so and hands over.
- How does a branch update its own details? If every change needs a developer, it won’t stay accurate.
- Where does each conversation end up? A clear summary in the right branch’s inbox or system, not a shared pile.
- Can we pilot it in one or two branches first? You want to find the gaps before every franchisee does.
Start with the branch that misses the most calls. You’ll learn more there in a week than in a month of planning.
If you’d like to see what this looks like in practice, my page on the AI receptionist explains how I build them, you can hear one answer as your own business, and my page for service franchises sets out what I’d build for a network.
If you want it done for you
I build websites, apps and AI assistants myself, every layer, and once a build starts you see it working within two working days. If you’d like to start somewhere simpler, I’ll design a free preview of your new homepage within two working days, with a short video walking you through it. Or just tell me what your branches need and we’ll take it from there.

