Multi-location XBert: separate knowledge bases per location

Tips & Tricks

A caller dialing your downtown office expects downtown hours, directions, and parking info, not your suburban location's details. Multi-location businesses need location-specific AI responses, and the setup is more involved than flipping a switch.

Configuration approach

Separate knowledge base entries per location: address, hours, parking, services specific to that location. Number-based routing: In the call flow builder, each location's number routes to the XBert context for that location. Business hours per location: Configure separately if locations have different hours.

Call each location number from an outside phone. Ask location-specific questions.

"What are your hours?"
"Where are you located?"
"Do you have parking?"

Confirm each number returns correct location-specific answers before going live.

Industry reality check

If you deploy AI on the front line, define escalation rules before you tune the greeting: what counts as urgent, what data the human needs on screen, and how you log outcomes so you can review transcripts against real bookings and complaints.

If the advice feels generic, pressure-test it against your busiest real week—not the average Tuesday.

Full multi-location XBert setup covers the configuration in detail. How many locations are you managing?

Posted Jun 3, 2026, 1:45 AM UTC

10
Loading comments…