01Split what is the same from what is local
Start with two lists. The shared list holds what every location says the same way: the services you offer, the rules on cancellations and refunds, the tone of voice, the answers that do not depend on a place. The local list holds what changes from one location to the next: address and parking, opening hours and holiday closures, phone numbers, prices where they differ, who works there, which slots are free. The rule that keeps the assistant honest is simple. Any answer that contains a local fact is read from that location's record and never typed into the shared text. Mix the two, and the assistant will give a customer in one town the Saturday hours of another.
- Shared: services, policies, tone, answers that do not depend on a place
- Local: address, hours, closures, phone, prices, staff, free slots
- A local fact is always read from that location's record
- One answer for the wrong location costs more trust than an honest 'I will check' (our view)
02Make it find out which location the customer means
A chat widget on a location's own page already knows where the visitor is. A message to a brand-wide Instagram account or an email to a general address does not. In that case the first job is to ask which of your locations the customer means, before any hours, price or slot is quoted. A customer who writes 'what time do you close' has asked a question with no answer until the location is known. Once the customer names one, the assistant keeps it for the rest of the conversation and repeats it when it matters, so a mistake shows up early. When someone says 'the nearest one', the assistant asks for a town or a postcode instead of guessing.
- Widget on a location page: the location is known from the page
- Brand-wide DM or email: ask which location before any local fact
- Repeat the location back when quoting hours, prices or slots
- 'The nearest one' needs a town or a postcode, not a guess
03Give every location an owner for its facts
The assistant is only as right as the record behind it. With one location, the owner remembers to change the holiday hours. With five, nobody does unless it is somebody's job. Name one person per location who owns that location's record, and decide how they report a change: hours, a closed day, a price, a new member of staff. Then use the weekly review. PROOF48's AI assistant page describes a weekly look at every conversation, sorted into answered, escalated and unanswered. With several locations, sort them by location too. A pile of unanswered questions from one place usually means, in our view, that the place's record has a gap.
- One named person per location owns its record
- Decide how changes are reported: hours, closures, prices, staff
- Weekly review: answered, escalated, unanswered, and by location
- Many unanswered questions from one place point to a gap in its record (our view)
04Send the handoff to the right person at the right location
Some conversations should never be answered by the assistant: a complaint, a refund, a request outside the usual pattern. With several locations, a shared inbox is the wrong place for them. A complaint about one location should reach that location's manager with the conversation attached, so the customer does not have to repeat everything. PROOF48's AI assistant page gives topic, time of day and client value as examples of what can trigger a handoff, and says the owner decides the triggers before launch. Who receives the handoff at each location is settled in the same conversation, before anything goes live.
- Complaints and refunds go to a person at that location, with the conversation attached
- Decide the receiver per location before launch
- Decide who sees an overnight handoff the next morning
- The owner sets the triggers: topic, time of day, client value
05Where PROOF48 is the wrong choice
AUTOMATE costs 2,997 EUR a month and lists an AI website chatbot that qualifies and books, AI DM and email auto-responders, booking automation, a CRM and everything in GROWTH. Its feature list does not mention locations, and we have no published case with several. Whether one setup covers yours is settled in a first conversation, not assumed. It is the wrong choice in a few situations. You have two locations that rarely get questions: a clear page for each and a fast human reply cost far less. Customers reach you mostly by WhatsApp or phone: AUTOMATE covers neither, and a standalone assistant for them is a custom build, priced on request. Each location uses a different booking tool: that is an integration question to settle before anything is promised. You have no site yet: the plans page says to start with a website, 500 to 2,500 EUR, paid after the preview.
- AUTOMATE, 2,997 EUR a month: site chat, DM and email auto-responders, booking automation, CRM
- No multi-location case is published, and the feature list does not mention locations
- WhatsApp and phone are outside AUTOMATE: custom build, priced on request
- Two quiet locations: a clear page each and a fast human reply cost less
Many separate businesses on one system, but not an assistant
FreshBatch is a marketplace with more than 19 businesses on one platform, each producer with its own storefront, and nearby customers notified when a batch goes live. It is not an AI assistant, and the case study records no assistant, no support chat and no multi-location setup, so it proves nothing about the question in this article. We do not publish its transaction volume. It shows only that one product can hold many separate profiles with their own details, which is the shape the shared and local lists above describe.
See the build: FreshBatchQuestions, answered
Can one assistant give each location its own hours and prices?
In principle yes: keep a separate record per location and make the assistant read the one the customer means. Whether PROOF48's AUTOMATE does that for your setup is settled before anything is quoted, because no multi-location case is published.
What if a customer does not say which location they mean?
The assistant should ask before it quotes hours, a price or a slot. Guessing the wrong location is worse than one extra question.
Does AUTOMATE cover WhatsApp or phone for each location?
No. AUTOMATE covers site chat, DM and email auto-responders, booking automation and a CRM. A WhatsApp or phone assistant is a custom build, priced on request.
Is the price per location?
The plans page lists one monthly price for AUTOMATE, 2,997 EUR, and no per-location price. Whether several locations fit inside it is settled before anything is quoted.
Where PROOF48 fits
One assistant can serve several locations when the shared rules live in one place, each location has its own record of hours, prices and slots, the customer's location is confirmed before any local fact is given, and complaints go to a person at that location. PROOF48's AUTOMATE, 2,997 EUR a month, covers site chat, DM and email auto-responders, booking automation and a CRM. No multi-location case is published, so ask first.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.