Give each store a one-page card of its own facts, keep one shared library of reply patterns by situation, and let AI draft from both while a person approves every reply. Route anything involving safety, staff conduct, refunds or legal threats to a named escalation contact, never to an automatic reply.
A franchisor's review platform may handle listings and dashboards, but the store-level routine is yours: who replies, in what voice, with whose facts, and when to stop writing and pick up the phone. That routine is the part AI can speed up without putting words in the brand's mouth.
Settle access and permissions before drafting anything
Replying needs the right role on each profile. On Google Business Profile, owners and managers can both respond to reviews, a profile has only one primary owner, and managers cannot add or remove users (Google's own help pages). In a franchise, the franchisor or an agency may be the primary owner, so check that you hold at least a manager role for every site you run, and ask for it if not.
Then settle the rules with the franchisor. These five questions, answered in writing, save weeks of awkwardness:
- May franchisees reply directly, or does a central team post replies?
- Are brand reply templates mandatory, and is there a required sign-off line?
- What response time does the brand expect for each star rating?
- Who is the escalation contact for safety, legal or media issues, and how do you reach them out of hours?
- May you use AI tools to draft replies, and with what settings?
Keep Google's own mechanics in mind when you set the response targets. Replies are public, the reviewer is notified when you reply, and they can change their review afterwards. A reply goes through a review before it appears: Google's help page says this usually takes up to 10 minutes but sometimes up to 30 days, so don't assume a reply is live because you posted it. The page is Google's guide to reading and replying to reviews.
Store cards: the facts each site's replies may use
The mistake that makes AI replies dangerous at several sites is borrowing facts. A draft for site 2 uses site 1's manager, or promises a policy the group doesn't have. The remedy is a store card, one per site, and a rule that a reply may state only what is on the card. Here is an illustrative card for a childcare nursery group's second site.
STORE CARD: [Site 2 name]
Manager (first name only in replies): [first name]
Complaints contact: [phone] and [email], answered Monday to Friday
Hours: Monday to Friday, 7:30 to 18:00; closed on public holidays
Rooms: baby room, toddler room, pre-school room; settling-in sessions for new families
Fees: set out in the parent handbook; changes announced in writing four weeks ahead
Staff who may be named in replies: none unless the reviewer names them and the manager agrees
Never mention: building work until [date]; staff changes; any individual child or family
Sign-off: "[Manager first name], [Site 2 name]"On a free ChatGPT plan, a project can hold five files, which is exactly one rules file, one library file and three store cards, so a three-site group fits (limits change, so check the current figure on OpenAI's pages). Claude Projects and Gemini Gems work the same way; Gems are becoming skills from November 2026. Keep the files plain text, name them clearly, and update the card whenever the manager, hours or policy changes, with the date at the top.
Two items on the card are easy to underrate. "Never mention" gives the assistant the topics to avoid, such as a dispute with a neighbour or staff turnover. And "first name only in replies" shows that the brand's sign-off is a rule, not a taste. If the franchisor sets a house style for sign-offs, such as a role instead of a name, put theirs first.
The reply library: twelve situations and the pattern for each
A library does not hold finished replies. It holds a pattern per situation: what to acknowledge, what to include, what never to say, and who approves. The assistant combines the pattern with the review and the store card. These twelve are a starting set for a nursery group; a shop or restaurant would swap a few rows but keep the structure.
| Situation | Pattern | Never include | Approver |
|---|---|---|---|
| 5 stars, general praise | Thank, echo one specific thing they said, sign off. 25 to 40 words | Details about their family; offers | Site manager |
| 5 stars naming a team member | Thank, say you will pass it on, sign off | The member's surname or role details not on the card | Site manager |
| 4 stars with a small gripe | Thank, acknowledge the point, say what you will look at, sign off | Excuses; promises not on the card | Site manager |
| 3 stars, mixed | Thank, acknowledge both halves, invite a conversation with the manager | Defensiveness about the criticism | Site manager and franchisee |
| 1 to 2 stars, service or communication | Acknowledge, apologise for the experience (not for specific fault), give the complaints contact | Admissions of fault; detail of what happened | Franchisee |
| Fees or billing complaint | Acknowledge, point to where fees are set out, invite contact | Amounts, refunds, credits, exceptions | Franchisee |
| Complaint about a named member of staff | Acknowledge, say it will be looked at properly, invite private contact | The staff member's name or any comment on their conduct | Franchisee; escalate if conduct is alleged |
| Safety, welfare or injury allegation | Holding reply only; do not discuss the case publicly | Any detail, defence or blame | Escalation contact before anything is posted |
| Reviewer names a child or another family | Reply to the substance without repeating any name | Names, ages, rooms, dates | Franchisee |
| Reviewer may not be a customer, or looks fake | Report through the platform; reply neutrally or not at all | Accusations; asking whether they are a customer | Franchisee |
| Legal threat, media or regulator mention | No reply until the escalation contact has advised | Everything | Escalation contact |
| Praise with an outdated or wrong detail | Thank and correct gently using the store card | Correcting in a way that embarrasses them | Site manager |
Two of those rows come from rules Google sets and are worth reading in the original. Google's contribution policy bars a business from offering incentives in exchange for a review, or for revising or removing a negative one. So a reply never says "come back and we'll give you a month free if you update your review". Nor should a reply hint that you would rather hear only good news, since the same policy bars discouraging negative reviews or selectively asking happy customers for positive ones. The policy is on Google's contribution policy page. For the wider picture of replying well to bad reviews, how to reply to negative reviews with AI, with examples and pitfalls has more samples.
Notice that the library says nothing about discounts, refunds or compensation. That is deliberate. Money, exceptions and anything that sounds like an admission are decisions for the franchisee, made in private, and the reply's only job is to start that conversation.
Escalation rules: when the reply stops being a writing task
An escalation rule says who takes over, how fast, and what goes online meanwhile. Write them before the first heated review arrives.
| Trigger | Who takes it | Acknowledge within | Public reply |
|---|---|---|---|
| Safety, welfare or injury allegation | Franchisee and the franchisor's escalation contact | Same working day | Holding reply only, after the contact agrees the wording |
| Allegation about a named staff member | Franchisee | Same working day | Holding reply |
| Discrimination or harassment claim | Franchisee, with advice | Same working day | Holding reply after advice |
| Legal threat, press or regulator | Franchisee, franchisor and a solicitor | Same working day | None until advised |
| Refund or fee dispute | Franchisee | Two working days | Neutral reply inviting contact |
| Personal data posted in a review | Franchisee | Same working day | Report to the platform; no reply repeating the data |
The times are the group's own targets, not anyone's requirement, so set them at a level your managers can actually meet. A holding reply for a welfare concern might read, in illustrative wording:
Thank you for telling us. We take concerns like this very seriously, and we can't discuss individual children or families in a public reply. [Manager first name] would like to speak with you directly on [phone] so we can look into this properly. [Manager first name], [Site name]
Note what it leaves out: no defence, no detail, no promise, and no confirmation that the person is a parent here. If the review is truly alarming, the real work happens off the page, with the people the franchisor names for it.
The drafting prompt, and what a good output looks like
With the rules file, the library and the store cards in a project, the prompt itself can be short. Its main job is to force a classification, a facts trail and a set of flags, so the person approving can check a reply in seconds.
You draft replies to online reviews for [brand], site [site name]. Use only (1) the brand
reply rules, (2) the library pattern for the situation, (3) this site's store card.
For each review I paste, return:
SITUATION: the library row it fits
ESCALATE: yes or no, and which trigger
DRAFT: 40 to 70 words (25 to 40 for 5 stars)
FACTS USED: each fact in the draft and the store-card line it came from
FLAGS: anything a person should check (names, dates, numbers, promises)
Rules: never confirm someone is a customer; never repeat a child's name or details; no
refunds, compensation or admission of fault; no offers tied to changing a review; use the
manager's first name and the complaints contact from the card. If the review alleges a
safety, welfare, conduct or legal matter, set ESCALATE: yes and write only the holding reply.
If a reply needs a fact that isn't on the card, write [NOT ON CARD] instead of guessing.
Review: [first name], [stars], [text]Take an illustrative three-star review at site 2: "The staff are lovely and my little one has settled well, but the fee increase came with hardly any warning. Would have liked more notice." A first draft from a bare instruction ("reply to this review") might read: "Thank you for your feedback! We always give at least two months' notice of fee changes, and the toddler room got the same letter as every other room. Please contact us for a refund of the difference." It fails three tests. "Two months" isn't on the card, which says four weeks. A refund is a promise only the franchisee can make. And naming the toddler room tells every reader which room the reviewer's child is in, a detail the reviewer never gave. With the prompt above, the output is:
SITUATION: Fees or billing complaint (3 stars, mixed). ESCALATE: No.
DRAFT: Thank you for taking the time to write, and for the kind words about the team. Fee changes are announced in writing four weeks ahead, and we understand that can still feel short. [Manager first name] would be glad to talk it through on [phone]. [Manager first name], [Site 2 name]
FACTS USED: four weeks (store card, Fees); manager and phone (store card); sign-off (store card).
FLAGS: Check that notice for this increase did go out four weeks ahead before the manager calls.
The flag does the most valuable work. The reply states the policy, not that the policy was followed this time. If the manager finds notice went out late, the reply must change to acknowledge it, and it is the person, not the assistant, who knows. Approval then takes the manager under a minute: read the draft, read the flag, confirm the facts against the card, post.
One more habit: paste only the reviewer's first name, the stars and the text. Order numbers, phone numbers and anything from your own records belong in the private conversation, not in a chat with an assistant. A general introduction to the AI side, with more samples, is in how to use AI to respond to Google reviews, and the case for keeping a person in the loop is made in whether to let AI auto-post replies to Google reviews.
Five-star replies that don't all sound the same
Most reviews are good ones, and that is where boilerplate creeps in. Add one line to the drafting prompt: "Echo one specific phrase from the review, and don't start two replies in a row with the same word." Here is what that produces for three illustrative five-star reviews at one site.
| Review (illustrative) | Reply drafted from the library pattern |
|---|---|
| "Everyone is so friendly. Five stars." | That friendly welcome is what the team works hardest at, so thank you for noticing it, [first name]. [Manager first name], [Site 2 name] |
| "Our daughter's key person, [staff first name], has been wonderful through settling in." | I'll pass this on to [staff first name] today, and thank you for taking the time to say it. Kind words like these make the team's week. [Manager first name], [Site 2 name] |
| "Clean, calm and well run. Would recommend to anyone." | Calm is what we aim for every day, so thank you, and thank you for the recommendation, [first name]. The team will be glad to hear it. [Manager first name], [Site 2 name] |
Each reply echoes a phrase from its review, none repeats anything about the child, and none promises anything. The staff first name appears only because the reviewer used it and the manager agreed, which is the rule on the store card. The replies are short on purpose. A long reply to a short review reads as effort spent on the wrong thing.
Test the setup on ten old reviews before it goes live
Setting up takes about half a day: an hour for the rules file, an hour for the library, half an hour for three store cards, and an hour of testing. Test by running the last ten reviews at each site through the project and comparing the drafts with what was actually posted. Ask three questions of each draft. Is any fact not on the card? Would the escalation have been triggered when it should have been? Does it sound like the brand? Every miss is a fix to the library or the card, not to the draft, because fixing the source fixes every later reply.
A month across three sites: 36 reviews
Here is the routine in use for a group of three nurseries, with illustrative figures. In one month the sites received 36 reviews.
| Site | Reviews | 5 stars | 4 stars | 3 stars | 1 to 2 stars | Escalated | Reported |
|---|---|---|---|---|---|---|---|
| Site 1 | 14 | 10 | 2 | 1 | 1 | 0 | 0 |
| Site 2 | 12 | 8 | 1 | 2 | 1 | 0 | 0 |
| Site 3 | 10 | 6 | 1 | 0 | 3 | 2 | 1 |
| Total | 36 | 24 | 4 | 3 | 5 | 2 | 1 |
The two escalations were a welfare allegation and a complaint alleging a named member of staff's conduct. Both got a holding reply only after the escalation contact agreed the wording, and the real conversation moved offline. The reported review was a one-star with no detail from someone the manager could not match to any family; the reply was neutral and the review was reported through the platform instead of answered with a challenge.
The time difference is the number owners notice. Before, the three managers wrote each reply from scratch, at about eight minutes each: 36 reviews, 4.8 hours. With the library and cards, 33 standard replies took about three minutes each, for 99 minutes, and the three special cases took about 20 minutes each, for 60. That is about 2.7 hours, a saving of roughly two hours a month. The bigger gain is that all three sites now sound like the same brand and none of them promised anything it shouldn't.
Once a month, the franchisee turns the pile into a pattern. Paste the month's reviews, tagged by site and library row, with names removed, and ask:
Here are this month's reviews for three sites, with stars, site and library category.
List: (1) themes per site with counts; (2) themes that appear at more than one site;
(3) any site where 4 or 5 star reviews mention the same weakness; (4) the median time
between review and reply per site. Quote short phrases as evidence. Don't speculate about
causes; list questions I should ask each manager. Data: [paste]In the illustration, the answer showed fee-notice comments in three reviews (one at site 1, two at site 2), nine reviews praising named staff (four, three and two by site), and five praising the settling-in sessions. The fee comments were the useful finding. A question for the two managers revealed that site 1 sent fee letters by email and site 2 handed them out at pick-up, which explains why notice felt shorter there. The group moved both sites to the email route, a process fix that no reply could have made. For a wider look across sites, one weekly AI summary across locations for a multi-unit franchisee shows how to fold reviews into a regular report.
A Monday-to-Friday reply rhythm and the tracker behind it
Once it is running, the routine takes about 40 minutes a week across the three sites, most of it the managers' approvals.
- Monday: paste the week's new reviews (first name, stars, text) into the project, and let the assistant classify and draft. Escalations are flagged the same day.
- Within one working day: site managers approve and post the straightforward replies. The franchisee reads every reply for 1 to 3 stars and anything flagged, and nothing from the escalation rows goes out without the named contact's agreement.
- Friday: update the tracker, with one row per review.
- Each quarter: read ten consecutive replies aloud, update the library and the cards, and rerun the ten-old-reviews test.
The tracker needs only a handful of columns: review date, site, stars, library row, escalated (yes or no), approver, date posted and days to reply. It lets the monthly prompt compute response times, and it gives the franchisor something concrete if they ask how reviews are handled. It also records who approved what, which matters if a reply is ever questioned.
Six ways a multi-site reply routine breaks
- One site's facts at another. A reply at site 3 is signed by site 2's manager. Fix: one project per brand, one card per site, and the site name in the prompt; check the signature before posting.
- Invented policy. "We always give two months' notice." It shows up in the FACTS USED line as a fact with no card line. The [NOT ON CARD] rule prevents it.
- An apology that admits fault. "We're sorry we failed to look after your child." Apologise for the experience, not for a specific fault, and leave the facts to the private conversation.
- Replying fast to a heated review. Draft the same day, post after a manager reads it. A reply that appears within minutes of an angry post can inflame it, and a few hours' pause rarely costs anything.
- Ignoring the good reviews. The 24 five-star reviews are the group's best marketing, and a short, specific thank-you is cheap. Skipping them leaves the page looking like a place that only responds to complaints.
- Template drift. After a few months, fifty replies begin "Thank you for your feedback". The pattern should vary its opening and echo something specific from each review; read ten consecutive replies aloud each quarter to check.
If your franchisor already runs a platform with suggested replies, keep the same discipline inside it: the card for the facts, the library for the pattern, a person for the approval. For automating the alerts, while keeping that approval step, replying to Google reviews with a Make scenario that includes an approval step shows the plumbing.
Questions about replying to reviews across several stores
Can I reuse the same reply across my stores?
Reuse the structure, never the text. A library gives each situation a pattern, and the store card supplies the facts for that site: manager, hours, contact. Identical wording under reviews at several locations reads as boilerplate to customers, and one site's facts can be wrong at another.
Should AI post replies automatically?
No. Reviews carry allegations, complaints and personal details, and replies are public. Let AI draft and classify, and have a person approve and post. Automations that post on their own are one error away from a public promise or an admission nobody authorised.
What if my franchisor's platform handles replies?
Ask whether you may reply yourself, whether their templates are mandatory, and who answers escalations. Your workflow still fits underneath: use the library and store card to draft, then enter the approved reply into their platform, or send it to whoever posts.
Can I confirm in a reply that the reviewer is a customer?
Avoid it. Confirming someone is a customer can reveal information about them, especially where you serve families or other sensitive clients. Respond to what they wrote, thank them, and invite them to contact the manager so that details are discussed in private rather than in public.
Further reads
- Patient Reviews and AI Replies: Staying Within Confidentiality — Reply to reviews without confirming who is a patient or client.
- Franchise Local Marketing With AI: Staying Inside the Brand Rules — Keep local marketing inside brand rules, with an approval log.
- Franchise Audit Checklist: Prepare for a Brand Inspection With AI — Prepare for brand inspections with a weekly self-audit.
- How to Get More Google Reviews With Automated Review Requests — Ask for more reviews without breaking review rules.
- Responding to Dealership Reviews With AI: Samples and Rules — Another worked set of reply samples and rules.
- What Your Franchise Agreement Allows Before You Add AI Tools — Six contract checks, a scored example and a ready-to-send email help a franchisee decide which AI tools need the franchisor's approval first. Not legal advice.
- AI Restaurant Reputation Management: What to Automate and What Not — Which review jobs a restaurant can hand to AI, which replies the owner must write personally, and how one month of reviews splits between the two.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Google's Business Profile help pages on replying to reviews and on user roles, and Google's contribution policy on incentives and review gating (checked October 2026). The nursery group, reviews, replies and figures are illustrative.