A dental practice with multiple locations sharing phone numbers or managing appointment requests across different offices faces a critical operational problem: the AI receptionist must know which location a caller is trying to reach and route their appointment to the correct calendar. Zanus AI's AI Phone and AI Booking modules claim to handle appointment scheduling and call routing, but the vendor's published material does not explicitly confirm how the system identifies and enforces location-specific bookings when a practice operates more than one site. This guide walks through what a multi-location dental practice must verify before purchase, what to request in a vendor demonstration, and how to test whether Zanus AI can reliably confirm the right practice and calendar in real administrative conditions.

The Multi-Location Dentistry Problem

Dental practices grow by opening satellite offices. A single phone number may serve two or three locations to simplify marketing and patient communication. When a patient calls to book a cleaning or implant consultation, the AI receptionist must ask or infer which location the caller wants, confirm it, and then book only into that location's available slots. If the AI books a patient into the wrong practice's calendar, the patient arrives at the wrong address, the appointment is lost, and clinical and administrative workflows break.

The problem is compounded when household members call: one family member may have a standing appointment at Location A on Thursday mornings, while another member prefers Location B on Wednesday afternoons. The AI must not confuse their histories or mix their appointment slots. If the system treats all bookings as fungible across locations, conflicts arise immediately.

Zanus AI's AI Booking documentation states that the system "connects to the major online calendars" and "several providers can each keep their own calendar," which suggests multi-location support is possible. However, the vendor's public material does not detail how the practice specifies which calendar maps to which location, how the AI receptionist learns location identity from a caller's words, or what happens when a patient's stated location does not match their historical practice affiliation.

What the Vendor's Material Does and Does Not Say

The Zanus AI AI Phone page emphasizes that "the AI searches your approved knowledge base by meaning, not by keyword" and that "call routing to the right department" assigns calls by "reason and language to sales, orders, support or a named colleague." The system also mentions "departments you define" and that "each department can be AI first, operator first or AI only."

Translated to dental operations, this suggests that a practice could set up departments for Location A, Location B, and a central intake function. The AI might then route based on what a caller says. However, the vendor material does not confirm whether location identity is a first-class entity in the data model, whether it is tied to the calendar connector, or whether the AI can infer location intent from contextual clues such as a caller's previous appointment history, zip code, or insurance network.

The booking documentation states that the system "offers your services, then only the free slots of your live calendar" and supports "by service and location." The phrase "by service and location" is the closest assertion to multi-location functionality, but it does not specify how location is specified during setup, how the AI learns which location a caller prefers, or how conflicts are resolved.

Core Questions to Ask the Vendor

Before committing to Zanus AI for a multi-location dental practice, request a structured demonstration that answers these questions:

1. Calendar and Location Mapping
How does the system connect each location's calendar? Can you connect three Google Workspace calendars, one for each practice location, and configure Zanus AI to treat them as distinct entities rather than a single consolidated schedule? If Location A is booked solid for Tuesday afternoon but Location B has openings, can the AI offer only Location B's free slots when a caller says they prefer Tuesday afternoon?

2. Location Identification from Caller Input
When a caller says "I'd like to book a cleaning at your downtown office," how does the system extract "downtown office" as a location identifier and confirm it against the configured locations? If the practice has not explicitly told the AI that one office is called "downtown," does the system ask the caller to clarify, or does it guess?

3. History-Based Location Inference
If a returning patient calls, does the AI know from their customer record which location they usually visit? Can the AI say, "I see you've had your last two appointments at our Oak Street location. Would you like to book there again, or try another location?" If the patient's history shows Oak Street but they say they want downtown, which assertion wins?

4. Household Member Separation
When two family members share the same phone number or email domain, how does the system keep their appointment calendars separate? If one household member has three recurring appointments at Location A and another has one at Location B, can the AI correctly distinguish their bookings and offer only available slots for the right person and location?

5. Cross-Location Transfers
If a caller reaches the AI phone receptionist and their call is routed to a staff member, can that staff member transfer the appointment booking to a colleague at a different location if needed? Does the transfer include visibility into both calendars?

6. Fallback Behavior When Location is Ambiguous
What does the AI do if a caller says "I want to come in for a root canal but I'm not sure which office is closer to me"? Does it ask clarifying questions, request a zip code, prompt the user to choose from a list, or defer to a human receptionist?

Setting Up a Test Scenario

Request a 15-minute supervised test of the following scenario. This test assumes a sample three-location dental group with calendars connected:

LocationCalendar SourceHoursHygienist Availability
Oak Street (Location A)Google Calendar: oak-hygiene@dentalpractice.comMonday–Friday 8 AM–5 PMTwo hygienists; off Wednesdays
Riverside (Location B)Google Calendar: riverside-hygiene@dentalpractice.comMonday–Thursday 9 AM–6 PM; Saturday 9 AM–1 PMOne hygienist; off Thursdays
Downtown (Location C)Google Calendar: downtown-hygiene@dentalpractice.comTuesday–Saturday 10 AM–7 PMOne hygienist; off Sundays and Mondays

During the test, perform the following calls:

Test Call One: Unambiguous Location Request
Caller statement: "Hi, I need to book a cleaning at the Oak Street office for next Thursday afternoon."
Expected behavior: The AI confirms Oak Street, searches the oak-hygiene calendar for Thursday afternoon slots, offers available times, books the appointment, and sends a confirmation to the email or phone provided.
What to verify: The booking lands in the correct calendar (oak-hygiene@dentalpractice.com), not in a combined or wrong location calendar. The confirmation message identifies Oak Street specifically.

Test Call Two: Location Preference Conflict with Availability
Assume Oak Street hygienists are fully booked next Wednesday through Friday. Caller statement: "I'd like a cleaning this week, preferably at Oak Street. When can you fit me in?"
Expected behavior: The AI either (a) tells the caller Oak Street is full and offers other locations with available times, or (b) defers to a human receptionist to discuss options.
What to verify: The AI does not book into Oak Street if no slots exist. It does not silently shift the caller to another location without explicit consent.

Test Call Three: Returning Patient with History at One Location
Assume the system has a record for "Sarah Johnson" with three prior cleanings at Riverside. Caller (Sarah Johnson's voice): "Hi, I need to schedule another cleaning."
Expected behavior: The AI recognizes the caller (by phone number or voice if integrated), recalls Riverside as her usual location, and asks, "I see your last appointments were at Riverside. Would you like to book there again?"
What to verify: The system correctly retrieves and applies location history. If Sarah says "Yes," the booking goes to the riverside-hygiene calendar. If she says "No, I'd like to try Downtown," the AI confirms Downtown and books there instead.

Test Call Four: Household Member Confusion
Assume "Michael Johnson" (Sarah's spouse) has had one appointment at Downtown and shares the household email (m-and-s-johnson@email.com). Caller (Michael's voice, from the same home phone): "Hi, I need to book a cleaning."
Expected behavior: The AI either (a) asks which member of the household is calling, or (b) uses caller ID or voice recognition to identify Michael and recalls his Downtown history without confusing it with Sarah's Riverside bookings.
What to verify: The system maintains separate appointment records and does not book Michael's appointment into Sarah's calendar or suggest Riverside as his usual location just because another household member uses it.

Test Call Five: Location Name Ambiguity or Abbreviation
Caller statement: "I want to book at the downtown location, but is that the one on Fifth Avenue or the one near the mall?"
Expected behavior: The AI either retrieves the street address associated with "downtown" from the practice's knowledge base, or it clarifies by asking, "We have one Downtown location on Fifth Avenue. Is that the one you want?"
What to verify: The AI does not guess or default to a location. It confirms unambiguously.

Testing Wrong-Site and Cross-Site Requests

After demonstrating correct behavior, request a failure test to see how the system handles mistakes:

Wrong-Site Test One: AI Books into Incorrect Calendar
Set up the scenario so that Oak Street and Riverside both have an opening at 2 PM on Thursday, but the caller explicitly asked for Oak Street. Call in, make the booking request, and verify the confirmation. Did the appointment land in the oak-hygiene calendar or the riverside-hygiene calendar? If it landed in the wrong one, the test reveals a critical flaw.

Wrong-Site Test Two: No Confirmation of Location Change
Caller asks for Oak Street, but the AI silently offers and books Riverside instead (perhaps due to a configuration error or a misunderstanding of the caller's intent). Request the system log and call transcript. Does the log clearly show that the caller said Oak Street and that the booking was made at Riverside? If the discrepancy is not logged, the practice will not discover the error until the patient arrives at the wrong office.

Cross-Site Request Test: Transfer with Wrong Calendar Access
A caller reaches the AI receptionist and is transferred to a staff member at Location A. That staff member attempts to book a follow-up appointment for the patient at Location B. Can they access the Location B calendar? Is the booking correctly attributed to Location B? If Location B's calendar is not visible to Location A staff, or if a Location A staff member can accidentally overwrite Location B's availability, the system is not safe for multi-location operation.

Desk Ownership and Permissions

Request documentation or a demonstration of the following administrative controls:

Calendar Ownership
Which staff member "owns" each location's calendar? In the test scenario, does the oak-hygiene calendar belong to a specific hygienist, or is it shared among all Oak Street hygienists? If ownership is unclear, appointments could be missed or duplicated. Verify that each location's calendar is owned by a responsible individual or a team and that only authorized staff can edit or delete bookings for that location.

Permission Boundaries
Can a staff member at Oak Street view, edit, or delete appointments in the Riverside or Downtown calendars? Can they accidentally book a patient into the wrong location's calendar? Request a live demonstration where a Location A staff member attempts to access Location B's calendar through the AI system. The vendor should show that either the access is denied or that a clear warning appears before any edit is applied.

Audit Trail
When an appointment is booked, moved, or canceled, does the system log which calendar it affected, who made the change, and when? For a multi-location practice, this audit trail is essential for reconciling discrepancies and identifying whether a booking error was due to a user mistake, an AI misunderstanding, or a system bug.

Knowledge Base and Location Context

Zanus AI's AI Phone documentation states that the system "answers only from your knowledge pages and price list." For a multi-location practice, the knowledge base must include location-specific information. Request a sample of what the vendor expects the practice to provide:

What Should Be in the Knowledge Base?
Each location's address, phone number, hours of operation, parking or access instructions, which services are available at which locations, hygienist names and specialties, and any location-specific policies (e.g., "Riverside offers Saturday appointments; Oak Street does not"). The AI should be able to answer, "Which location has the earliest opening for an implant consultation?" and provide accurate information for all three practices.

How Often Is the Knowledge Base Updated?
If a hygienist goes on vacation or a location changes hours, how quickly can the practice update the knowledge base so that the AI's responses are accurate? Zanus AI's marketing says "Lisa sets it up by talking," but does that real-time update capability extend to location-specific facts, or must the practice submit formal updates that are processed later?

Who Maintains Location Data?
Is there a central knowledge manager who oversees all location data, or does each location maintain its own? If locations are independent, the risk of inconsistent or outdated information increases. Clarify who is responsible for keeping location data current.

Questions for a location-specific demonstration

Give the supplier a controlled request for a named practice and appointment category. Ask them to show which source establishes the location, which calendar supplies availability and which staff member owns an unresolved request. Repeat the same enquiry for a different practice without assuming that the proposed account supports a particular multi-location structure.

Ask whether the exact practice-management product and the specific read or write operation are supported in the proposed deployment. Request evidence of the configured connection and the applicable scope. Do not substitute a fictional representative’s reassurance for an answer from the actual supplier.

Then make a wrong-site request. Inspect the words presented to the caller and the record received by reception. An acceptable result follows the practice’s approved procedure and accurately distinguishes a confirmed booking from a desk callback request. Record unresolved integration or calendar questions in the acceptance register.

Acceptance Criteria for Multi-Location Deployment

Before signing a contract, establish clear acceptance criteria with the vendor. A dental practice should require the following in writing:

Criterion 1: Location Confirmation in Every Booking Call
Every appointment booking call must result in a transcript and confirmation that explicitly names the location. If a transcript says the caller asked for Oak Street and the confirmation email says Riverside, the booking must be treated as a failure, and the practice must be able to reject it or trigger a refund during the trial period.

Criterion 2: Calendar Accuracy Test
Before the go-live date, perform at least 10 test bookings across all three locations. Verify that each booking appears in the correct Google Calendar within 5 minutes. If even one booking appears in the wrong calendar or is duplicated, the deployment is not ready.

Criterion 3: Household Member Separation
Submit a test case with two family members sharing contact details. Request at least five bookings for each family member at different locations over a two-week period. Verify that the AI never confuses their histories or books one family member into the other's preferred location without explicit confirmation.

Criterion 4: Audit Trail and Logging
Every booking, edit, and cancellation must be logged with the following details: timestamp, caller phone number, stated location, booked location, calendar affected, staff member who handled any manual intervention, and confirmation status. The practice must be able to export this log at any time.

Criterion 5: Failure Mode Documentation
The vendor must provide documentation of known failure modes specific to multi-location setups. For example: "If a location name in the knowledge base is ambiguous, the AI may ask for clarification" or "If a calendar connector fails, bookings default to the first configured location." The practice must review and accept these risks before deployment.

Configuration Worksheet

Use this worksheet to document the practice's multi-location setup and share it with the Zanus AI team during onboarding:

ItemOak Street LocationRiverside LocationDowntown Location
Address and Zip Code123 Oak Street, Suite 100, Anytown 12345456 Riverside Drive, Elsewhere 67890789 Fifth Avenue, Downtown 11111
Phone Number (Local)555-0101 (for reference; calls forward to main line)555-0101 (shared)555-0101 (shared)
Google Calendar Emailoak-hygiene@dentalpractice.comriverside-hygiene@dentalpractice.comdowntown-hygiene@dentalpractice.com
Hours of OperationMon–Fri 8 AM–5 PMMon–Thu 9 AM–6 PM; Sat 9 AM–1 PMTue–Sat 10 AM–7 PM
Hygienist(s) and AvailabilityJane (all days); Bob (Mon, Tue, Thu, Fri)Alice (Mon–Fri); off ThuCarol (Tue–Sat)
Closed Days or HolidaysSunday, Monday (all)Sunday; Thursday (clinic closed)Sunday, Monday (all)
Parking or Access NotesFree parking in lot. Entrance on side street.Valet parking available. Main entrance faces river.Paid garage. Use elevator to 8th floor.
Special Policies (e.g., deposit for new patients)$25 deposit for first-time patientsNo deposit; insurance verified at visit$50 deposit; refundable if attended

Provide this worksheet to the vendor and ask them to confirm, in writing, how each detail will be represented in the Zanus AI knowledge base and how it will influence the AI's responses and booking logic.

What Changes the Purchase Decision

A practice should reconsider or delay the purchase if any of the following occur during the trial or demonstration:

Red Flag One: Location Identity Is Not Confirmed to the Caller
If the AI books an appointment without explicitly stating which location the appointment is at, or if the confirmation email is generic and does not name the location, the system is not suitable for multi-location operation. Request that this be fixed before deployment.

Red Flag Two: Calendar Integration Fails or Is Manual
If the vendor cannot automatically connect all three Google Calendars and instead requires manual export-import or a custom integration that the practice must manage, the ongoing operational burden is high. Multi-location booking must be seamless, not a manual workaround.

Red Flag Three: The Vendor Cannot Answer How Household Members Are Separated
If the vendor's response to the household member test is vague, evasive, or requires the practice to implement a custom solution, this is a significant gap. This capability is essential for dental practices where families are common patients.

Red Flag Four: No Audit Trail or Limited Logging
If the system does not log which calendar a booking was written to, who made changes, or when, the practice cannot troubleshoot errors or dispute wrongly placed appointments. This is non-negotiable for multi-location operation.

Red Flag Five: The Vendor Suggests Using a Single Consolidated Calendar
If Zanus AI recommends combining all three locations into one calendar and filtering by location afterward, this approach will not scale and will not prevent cross-location booking conflicts. Reject this suggestion and insist on separate calendars with clear location attribution.

Frequently Asked Questions

Q: Can Zanus AI handle shared phone numbers across locations?
A: Yes, the system is designed to accept calls on one number and route or book across multiple calendars. However, it must clearly identify the location the caller wants before booking. Request a demonstration of this specific scenario.

Q: Does Zanus AI integrate with my practice management software (e.g., Dentrix, Eaglesoft, Open Dental)?
A: Zanus AI connects via standard calendars (Google, Outlook) and APIs. Some practice management software supports calendar export; others may require a custom integration. Verify with your software vendor whether they offer an integration to Google Calendar or another supported platform. See Zanus AI platform integrations for current information.

Q: What happens if a patient is booked into the wrong location during the trial?
A: Document the error with the booking confirmation and transcript. Request a refund or credit during the trial period. This is a critical failure and should be grounds for terminating the trial if not resolved quickly.

Q: Can the AI learn that certain patients always prefer a specific location?
A: If Zanus AI integrates with your practice management system, it may retrieve patient history and suggest a preferred location. If not, the AI can learn over time if the practice builds this information into its knowledge base or manually tags patient records.

Q: How do we handle a patient who calls and does not specify a location?
A: The AI should ask, "Which location would you prefer?" and then list or describe the options. Alternatively, if the caller is a returning patient, the AI can suggest their usual location and ask for confirmation. If the caller is new, the AI should gather location preference before booking.

Q: Can staff at one location edit or cancel bookings made at another location?
A: This depends on permission settings. Request that the vendor configure separate accounts or roles for each location so that accidental cross-location edits are prevented. At minimum, all edits must be logged with the location and the editor's name.

Q: What if a patient shows up at the wrong location because the AI booked them incorrectly?
A: This is a service failure. The practice should have a protocol: offer to reschedule at the correct location immediately, apologize, and waive or reduce the no-show fee. Share this incident with Zanus AI support and request a review of the booking process to prevent recurrence. Consider whether the issue is a configuration error, a knowledge base gap, or a system limitation.

Final Recommendation

The purchase decision should follow the demonstrated location and calendar behaviour in the proposed deployment. Keep unresolved capability, connection and ownership questions open until the practice has usable evidence.

Official sources and related guides

This independent Sysevo guide uses the following official documentation. The workflow and trial scenarios are evaluation proposals, not reported customer results or a hands-on benchmark.

Compare the same requirements with the relevant Sysevo product, Voice Agents and CRM. Review Sysevo plans and pricing or book a demo to discuss the proposed setup. Sysevo sells its own business software and is not affiliated with the competitors discussed here.