Create a controlled branch directory
Maintain one approved record per location containing its public name, address, local time zone, opening hours, services and contact destination. Include common names callers use for the branch, such as a suburb or shopping centre name. Give each record an owner who can approve changes. Do not create branch entries for places where the business does not actually operate. If you serve a wider area from one office, describe that as service coverage rather than inventing extra offices to make the directory look more extensive.
Ask a location question when it matters
A caller may mention a suburb, a staff member or a previous appointment instead of a formal branch name. Use that information to ask a short confirmation. For example: "Is that our North office?" If the caller does not know, offer the relevant options using clear distinctions rather than reading a long list. A mobile number does not reliably establish where the person wants service. Someone may be booking near work, helping a family member or calling while travelling. Keep location selection explicit before taking a branch-specific action.
Keep services and calendars separate
Not every branch necessarily provides every service or has the same staff availability. Check the approved branch-service mapping before offering an appointment. A calendar with an available slot at the wrong office is not a valid substitute unless the caller agrees to change location. Confirm the address in the booking recap, especially where similar branch names exist. If a central team handles all booking requests, make that ownership clear in the internal message and preserve the caller preferred branch rather than silently replacing it with the default location.
Apply local hours and fallback rules
Determine availability using the branch local time and approved exceptions. A shared reception service may answer while the selected branch is closed. Explain that distinction and use the correct callback expectation. Each branch should have a backup destination or message queue, with central escalation only where agreed. Test what happens when one branch is closed and another is open. Do not transfer a caller to an available but unrelated branch simply because somebody might answer. The receiving team needs both the authority and context to help.
Prevent information leaking between branches
A branch-specific instruction should not become a general fact about the whole business. Label internal answers with their location and review who can change them. When a caller changes branches during the conversation, refresh the relevant hours, service rules and availability instead of retaining assumptions from the first choice. Check that summaries are delivered to the intended team and contain the correct branch. Avoid collecting or repeating unnecessary personal information while moving between destinations. Access to customer records should follow the business-approved process for the actual systems involved.
Test with deliberately ambiguous requests
Use internal scenarios involving two branches with similar names, a caller who changes location, a service available at only one site and a branch on different hours. Inspect the final calendar or queue as well as the spoken response. Confirm that staff at the wrong branch receive nothing they should not receive. Track misroutes and branch corrections separately from ordinary transfers after launch. When a new location opens, treat it as a fresh routing change with its own acceptance tests, not merely another name added to a greeting.