Multiple locations, one booking conversation: a service-business playbook

Start with the branch decision

Consider an illustrative repair business with two branches and different specialist services. “Can I come tomorrow?” sounds like a simple booking request, but the right answer depends on location, the type of repair and which team can handle it. The conversation should surface those choices before offering an appointment.

UChat documents a Cal.com integration for scheduling journeys. It describes both booking-link and in-conversation approaches. This gives a project team options; it does not mean every business should replace its existing scheduling experience with a fully conversational one.

Official references: UChat: appointment setting with Cal.com

Build a service-and-location map

Ask each branch manager to approve a short map of services, eligibility questions, appointment length and preparation instructions. Identify services that require staff review before a slot is offered. Keep this map understandable to the people maintaining it, rather than burying business rules inside a long AI instruction.

A customer who chooses the wrong branch should be able to change it without starting again. Preserve the description of their need, then re-evaluate the available service choices. If a transfer between branches needs staff approval, say so before inviting the customer to travel.

Choose the simplest reliable booking experience

A guided booking link may suit a business whose existing calendar already explains location and service choices well. A conversation can first narrow the request and then send the appropriate page. Direct chat booking may be useful when customers need more guidance, but it introduces more states for the team to support.

For either approach, define what the customer sees before confirmation: branch address, service, local date and time, preparation requirements and any relevant charge. Ask staff to read this final summary as if they were a first-time customer. Ambiguous location names are easy to miss internally.

Plan for changes and unavailable slots

Write explicit responses for fully booked days, branch closures and requests outside normal services. Offer an alternative only when it is genuinely available; otherwise collect the preference for a human follow-up. A conversation ending with a clear pending request is better than a false confirmation.

Give the team a way to recognise an existing request when the customer returns through another channel. Treat a reschedule as a change to the original appointment, with a clear final record, rather than leaving staff to reconcile two separate conversations manually.

Pilot at one branch, then compare

Run staff rehearsals before customer release: the wrong location, an unclear service, a closed day, a changed preference and a failed confirmation. During the pilot, review misrouted requests, staff corrections and customers arriving without the right preparation. These measures show where conversation design needs attention.

uchat.bot can scope the booking journey, agree the branch rules and configure the UChat workflow around your scheduling system. Once one branch can operate and maintain it comfortably, the pattern can be adapted for the next location.