Corporate should control everything an AI receptionist says on behalf of the brand: the script, the answers, what it can promise, when it hands a caller to a person and where the call data lands. Franchisees should control the local facts it works from, like hours, staff, calendar and service area.
Most franchise systems don't have that split. AI call answering shows up location by location, bought on a credit card, with a script someone wrote on a Saturday. A year later the brand has a dozen different voices answering its phones and corporate can't hear any of them.
Why this is corporate's problem
A caller doesn't know which location is franchisee-owned. To them, the phone is the brand. When an AI answers, it's the first impression, and often the only one before they decide to book or hang up.
When each franchisee picks their own tool, a few things happen at once:
- The answers drift. One location quotes a price range. Another says "we'll call you back." A third promises same-day service the location can't deliver.
- The data disappears. Calls, transcripts and leads live in the vendor's dashboard, not the CRM. Corporate can't see call volume, missed opportunities or what customers are asking.
- Nobody reviews it. The script that went live on day one is still running a year later, after the menu, the prices and the promotions changed.
- The risk is shared. If an AI makes a promise the location can't keep, the review lands on the brand's listing, not the franchisee's.
That's not a reason to ban AI answering. It's a reason to own it.
What corporate should control
Here's the line we draw. Everything on this list speaks for the brand, so corporate writes it, approves it and pushes it to every location.
- The script and the voice. The greeting, the tone, how it introduces the business and how it closes the call. Every location should sound like the same company.
- The answers. The knowledge the AI pulls from: services, policies, what's included, what isn't. One approved source, updated in one place.
- What it can promise. Can it quote prices? Give a range? Offer a discount? Guarantee a time? Most systems should keep this narrow. An AI that books an appointment is useful. An AI that negotiates is a liability.
- The handoff rules. When the call goes to a person, and how fast. Complaints, refunds, pricing exceptions and anything that commits the brand legally never stay with the AI. Neither does a caller who asks for a human.
- Disclosure and recording. What the AI says about being AI and about the call being recorded. More on this below.
- Where the data goes. Every call creates or updates a contact in the CRM, with a summary, the outcome and the location tagged.
- The reporting. Calls answered, calls handed off, appointments booked and calls that went nowhere, by location, in one view.
What franchisees should control
Corporate owns the standard. Franchisees fill in the parts only they know:
- Business hours, holiday closures and after-hours rules
- Who gets the handoff at their location, and their phone numbers
- Their calendar and appointment availability
- Their service area or delivery radius
- Local promotions, within the limits corporate sets
That's the same split we use for every location automation: corporate owns the template, franchisees switch on and fill in the local pieces, and a short list of things never gets automated at all. Our franchisee CRM and location automation page lays out the full menu.
The legal parts to check
We're not lawyers, and this isn't legal advice. But three things come up every time a franchise system rolls out AI answering, and your counsel should look at each one.
Recording consent. AI answering tools usually record or transcribe calls. Some states require every party to consent. California's Penal Code section 632 prohibits recording a confidential communication "without the consent of all parties." If you have locations in states like that, a recording disclosure at the top of the call belongs in the corporate script, not in each franchisee's judgment.
AI disclosure. States are starting to regulate this directly. Utah's 2024 AI law requires a business using generative AI with consumers to disclose, if asked, that the consumer is talking to AI and not a human. Rather than tracking it state by state at the location level, we set one rule for the whole system: if a caller asks whether it's AI, it says yes.
Outbound calls. Answering an incoming call is one thing. Having the AI call people back is another. The FCC has ruled that AI-generated voices are "artificial" under the Telephone Consumer Protection Act, which brings them under the TCPA's consent rules for artificial or prerecorded voice calls. If any location wants AI callbacks, that's a corporate decision with counsel in the room.
How to roll it out
If your locations are already answering with AI, or about to, here's the order we work in.
- Inventory what's live. Ask every franchisee what answers their phone today, and what it says. You'll find tools you didn't know about.
- Pick one approved setup. One tool or one configuration inside your CRM, so scripts, data and reporting live in one place.
- Write the corporate script. Greeting, answers, promises it can and can't make, disclosure, recording notice and handoff rules.
- Build the local fill-ins. A short form each franchisee completes: hours, staff, calendar, service area.
- Test it like a customer. Call every location. Ask the awkward questions: a complaint, a refund, a price, "is this a robot?"
- Connect it to the CRM. Every call lands as a contact with a summary and an outcome, tagged by location.
- Review it monthly. Read a sample of transcripts. Update the answers when prices, services or policies change.
Step 7 is the one that gets skipped. If nobody owns the script, it's out of date within a quarter.
From our work. When we took over the CRM for a 35-unit franchise, some locations used it every day and some had barely logged in. Franchisees weren't sure what they were even allowed to automate, so the ones who wanted help with the phones went looking on their own. Sorting out what corporate owns and what each location can switch on was one of the first things we did. The case study covers how.
If you want the bigger picture of what a franchise CRM should be doing across development and every location, start with our guide to what a franchise CRM is and why most go underused.
Frequently asked questions
Should a franchisor control the AI receptionist at each location?
Corporate should control the parts that speak for the brand: the script, the answers it gives, what it's allowed to promise, when it hands off to a person, and where the call data goes. Franchisees should control the local facts: hours, staff, calendar and service area.
Can franchisees pick their own AI answering service?
They can, and many already have. The problem is that every location then has a different script, different answers and call data that corporate never sees. A better setup is one approved tool, configured from a corporate standard, with each location filling in its own local details.
What should an AI receptionist never handle on its own?
Complaints, refunds, pricing exceptions, anything that commits the brand legally, and any caller who asks for a person. Those go to a human, fast, with the call summary attached.
Does an AI receptionist have to say it's AI?
Rules vary by state, so check with your counsel. Utah, for example, requires a business to disclose that a consumer is talking to generative AI if the consumer asks. Our default is simpler: if a caller asks, the AI says yes, every time, at every location.
Every location answering the phone its own way? We implement and run franchise CRMs for growing brands, across franchise development and every location, including AI call answering on a script corporate approves. See the location automation menu: what corporate owns, what franchisees can switch on and what should never be automated. Leave your email there and we'll send the full Franchise Automation Map when it's ready.