Everything below is fictional. When this gets built for a real business, the location list, service list, and any locked pricing/policy come from the business's own published rates, the way the example below shows.
1. Client-facing request
A request, not a live booking calendar. It replaces a phone call or a shared inbox with a form that reaches every location the same way, and locks in pricing and policy before someone submits an add-on request.
2. Front-desk view, across every location
Every request lands here the moment it's submitted, grouped by location, so staff can see at a glance which site already has a full queue before saying yes to one more.
How this gets built for real
A request, not a live schedule. It doesn't know which exact times are actually free at a location unless it's connected to that location's real calendar. Staff still confirm the exact time, the same way a phone call would, just captured through one shared channel instead of a different inbox per site.
The locked price and policy shown at request time is exactly what gets echoed back on the confirmation. A real build pulls both from whatever the business has actually published, and updates in one place if either changes, so every location quotes the same thing.
The load view is a count, not a true capacity model. A real build can weight it by appointment length or staffing on a given day; this demo shows the mechanism; a shared, visible queue instead of five separate blind spots, not a finished capacity planner.
Nothing here actually sends anything. A real version would notify the relevant location's staff the moment a request comes in. This demo just shows what that request would look like once captured.
See it built for a real business: Callanan Veterinary Group, Arkansas Wedding Barn, Bellevue Berry Farm.