One AI Assistant for Several Locations: How to Set It Up Without Confusing Customers

A business with more than one location has a specific problem: customers do not ask 'what are your hours?', they ask 'what are your hours in the Northfield shop?'. A single generic answer is wrong for most of them. Some questions apply to the whole business, such as your brand promise or your return policy, while others belong to one branch: the address, the opening times, who works there, which services are offered and how to book. If an AI assistant mixes these up, it can send a customer to the wrong address or promise a service the nearest branch does not offer. This guide explains the two ways to set up chat for several locations, how to structure the information so the assistant gets it right, how to route conversations and bookings, how to keep the brand voice consistent and how to test before going live. It also explains what Crescelo does and does not do, so you can choose the right structure.

The two structures

Neither is universally better. One assistant is simpler to maintain and keeps the brand consistent. Separate assistants keep each branch's information clean and let each team manage its own content. Many businesses start with one and split later.

Approach 1: one assistant, many locations

The key is that every location's facts are labelled with the location's name in the text itself. Retrieval works on passages of text, so a passage reading 'Opening hours: Monday to Friday, 9 to 5' cannot be attributed to a branch unless the branch is named in it.

• Create one short document per location, starting with its name, address and area.
• Repeat the location name in each section: 'Northfield: opening hours', 'Northfield: parking', 'Northfield: services'.
• Put shared policies, such as refunds and privacy, in a separate company-wide document.
• Add a short instruction: 'If the visitor has not said which location they mean, ask them before giving hours, addresses or availability.'
• List which services each location offers, so the assistant does not promise treatments the branch lacks.

Approach 2: one assistant per location

1. Create an assistant for each branch and give it its own name, welcome message and colours if you want each to feel local.
2. Load a knowledge base containing the shared company documents plus that branch's own documents.
3. Install each widget on the matching page of your website, or give each branch its own hosted page or link.
4. Set each branch's opening hours and booking settings in its own assistant.
5. Assign a person at each branch to review the unanswered questions weekly.

Plans limit how many assistants and hosted pages you can have; Crescelo's Starter, Growth and Agency plans allow one, three and seven hosted pages respectively, so check that your plan covers your number of branches. See pricing.

Routing visitors to the right branch

• Ask early: 'Which location are you interested in?', with the branch names as quick-reply suggestions.
• Where a page belongs to a branch, install the branch's assistant on that page so no question is needed.
• For enquiries that cross branches, for example 'Which of your shops is nearest to me?', include a list of areas each branch serves; see service area verification.
• Capture the preferred branch with each lead so the right team follows up.
• Make it easy to switch: 'Would you like information for another location?'

Booking across locations

Crescelo's built-in booking uses one set of opening hours and one slot length per assistant, and it hides slots that are taken. It does not assign staff or handle several rooms. For several locations, the cleanest pattern is a separate assistant and booking calendar for each branch, so hours and availability are never mixed. Alternatively, link each location to its own Calendly or Cal.com page. Whichever you choose, make sure the confirmation email names the location and address, because that is the detail customers most often get wrong.

Keep the brand consistent

• Write the tone instructions once and reuse them for every assistant.
• Use the same core documents for policies and company facts, updated in one master copy.
• Agree on wording for common situations such as complaints and refunds.
• Review each assistant's conversations against the brand guidelines each quarter.
• Decide who can change instructions and documents; see securing your account with roles.

See making the assistant sound like your business for a tone guide.

Handling local differences

Test before you launch

1. Ask the same question for each location and check that the answer names the right one.
2. Ask without naming a location and confirm the assistant asks which one.
3. Ask about a service only one branch offers, at another branch.
4. Ask for directions and parking at every location.
5. Try a booking at each location and check the confirmation email.

Repeat after every change, and keep the question list as a regression test.

Common mistakes

• Putting all hours into one paragraph without location names.
• Forgetting to update one branch's document when something changes.
• Letting each branch write its own tone.
• Not capturing which branch a lead wanted.
• Using one booking calendar for locations with different hours.
• Never asking staff at each branch to review answers.

Frequently asked questions

Try a multi-location document set in the playground, see the knowledge base feature and read governing AI chat across many locations.

Further reading

• Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.