A branch calendar is ready to roll out when the customer can select a deliverable appointment, reception can see the same commitment, and both parties get consistent information when the booking changes. Ask vendors to demonstrate these outcomes with two branches and a shared resource. A screen full of available times tells you very little about how the system handles the last slot, a reassigned appointment, or a closure.
This guide is for operations and procurement teams that already know their appointment types and are choosing how to roll out online booking across locations. Start with the service scheduling rules guide if you still need to define durations and buffers. The checks below describe acceptance criteria to discuss with a vendor. Verify which configurations are supported in the proposed deployment.
Choose a pair of branches that can expose a conflict
Pick one branch with a dedicated team and one that shares a specialist, room or equipment. Use two services with different delivery requirements, such as a remote consultation and an on-site assessment. Write down who is allowed to take each appointment and whether reception and customers draw from the same availability. Where the business uses a separate system for staff absences, specify how an absence reaches the booking calendar and who owns exceptions.
For a GCC rollout, include at least one Arabic customer journey and one English journey. Use branch names customers recognise and explicitly check the local time for branches in different countries. If the booking is remote, the confirmation should explain how to join. If it is in person, check that the address and any arrival instructions match the selected branch.
Run the scenario table before opening bookings
| Illustrative scenario | Action to demonstrate | Acceptance criterion |
|---|---|---|
| Last slot at a repair centre | Reception and a customer try to confirm the same slot | Only one gets confirmation and the other sees an available alternative |
| Consultant shared across branches | Reserve the consultant at branch A and inspect branch B | Branch B excludes the appointment and agreed travel allowance |
| Training room unavailable | Select a service while the trainer is free but the room is occupied | The customer cannot confirm the appointment without an eligible room |
| Cross-branch reschedule | Move a confirmed appointment from A to B | Staff and customer see the new branch and time, and the old slot is released |
| Temporary branch closure | Block a half-day that already contains bookings | New bookings are blocked and existing appointments are surfaced for follow-up |
Collect the confirmation shown to the customer and the branch record for every scenario. Record who handled it and what happened to any capacity that was held. Use fictitious people and a sandbox. A buyer can review screenshots and event records without exposing real customer data or occupying production slots.
Decide how changes should behave when they fail
A reschedule is a good way to expose gaps between two calendars. Suppose a professional services team moves a confirmed assessment from its original office to another. The replacement time disappears while reception is reviewing the move. Agree whether the original appointment should remain confirmed, who sees the conflict and whether a message is sent. Test that outcome before buying. The customer should never have to infer which confirmation is still valid from two contradictory emails.
Likewise, a temporary closure should make it possible to identify affected appointments and assign follow-up. Establish who can change a branch calendar and whether a central operations user can support several branches without exposing unnecessary customer information. Record the final authority for disputed bookings in the rollout plan.
What should procurement ask the vendor to price?
Request a proposal based on the rules you actually need. Separate subscription costs from setup, staff training and support for changes. Ask how pricing changes if a specialist works in multiple branches, if one branch needs its own scheduling page, or if confirmation and reminders require additional services. Where the vendor cannot show a requirement, record it as unverified and decide whether a manual exception is workable.
A separate calendar per branch may fit teams with independent staff and equipment. A shared model becomes more valuable when a central desk moves bookings across branches or when the same resource is used in several locations. Judge the approach by how it handles these operating cases and who can fix an exception during the working day.
Reconcile existing appointments before the cutover
Export the upcoming appointments by location and separate confirmed commitments from requests that still need a response. Give the migration owner a way to match each record to its original reference, location, service, local time and status. Investigate ambiguous records with the branch that owns the booking. A matching customer name and time can be a clue, but a customer may legitimately have reserved two places for colleagues.
Choose a clear cutoff for entering new appointments in the old calendar. For example, reception stops adding confirmed commitments there at 4 p.m., an operator reconciles the late changes, and a second person compares the branch totals and reviews the exceptions. Pay particular attention to moved and cancelled appointments that had already generated a confirmation. Ask who can still read the old calendar, how long it will be needed, and how you will prevent a team member from accidentally confirming new appointments there.
Write a decision record for each cross-branch exception
List the source of availability, the team that owns the change, and the person who can resolve an exception. A branch manager might be able to block a room, while the central desk can reassign a shared consultant across locations. Define who should receive a notification after a change and what the customer can see. In a provider demonstration, have a branch user and a central user show what each can view and edit.
For example, a training business may offer a consultation centrally but reserve an on-site room locally. If the branch cannot deliver the appointment, reception can offer an alternative location or a remote conversation. The decision record should say who offers the choice, when the old reservation can be released, and what the final confirmation must contain. Capture these rules before adding more branches with different staff and facilities.
Rehearse the temporary operating process
If availability stops updating, decide which entry points should stop promising immediate confirmation. One practical response is to take callback requests in a shared queue with timestamps and branch labels, then reconcile them against existing commitments. Set a named owner for checking which customers received confirmation during the incident. Once the calendar is reliable again, validate those commitments before reopening the public link. If a customer has two incompatible messages, contact that customer directly with the valid details.
Use pilot evidence to decide whether to expand
Keep operational defects separate from performance metrics. Log each confirmed double booking, incorrect address and failed transfer, with the case owner and resolution. Then measure adoption and outcomes using counts with denominators: confirmed appointments by channel, attendance out of confirmed appointments eligible for the reporting period, and manual corrections out of reviewed appointments. Record the branch, period and any gaps in channel coverage. A busy location can generate more incidents without having a higher error rate, and a quiet branch can still expose a serious defect.
Set the go-live decision at the start of the pilot. A material exception should have a tested recovery path and an owner before expansion. A minor wording change may be tracked for the next revision. When evaluating a new branch, run the applicable scenarios again with its real rules and fictitious bookings in the review environment.
Buyer questions
Can one booking page cover several locations? It can be a suitable entry point if the platform preserves the customer's branch selection through the availability view, confirmation and later changes. A branch-specific entry point may be clearer when visitors start from a branch landing page.
What should stop a pilot from expanding? Examples include double confirmation, incorrect addresses, or a reschedule that loses the original appointment without confirming a replacement. Name an owner for each failed scenario and rerun the affected checks before adding branches.
How do we measure the pilot? Compare confirmed, attended, cancelled and moved appointments using agreed definitions. Record conflict and correction incidents separately. Include the dates, services and participating branches so the results can be interpreted in context.
Bring your two branches, two services and one exception to a Solvarex demo. Use the calendar and appointment scheduling product page to review the offer, then ask the team to demonstrate the configuration required for your rollout.
References for comparison
Microsoft Bookings documentation describes configurable staff and service settings. Square’s multi-location overview illustrates how another platform presents branch and resource availability.
