Route Clients to the Right Location and Staff Automatically
With several locations, the hard part is making sure a client only sees the right site, the right service and a provider who actually works there that day. This playbook sets up SchedulingKit so that routing happens through the booking flow itself.
Start This PlaybookOverview
With several locations, the hard part is making sure a client only sees the right site, the right service and a provider who actually works there that day. This playbook sets up SchedulingKit so that routing happens through the booking flow itself.
Clients pick a location, see only the services offered there, and only the staff assigned to that service and location are offered, with Round Robin (Pro and above) sharing bookings where several providers qualify. SchedulingKit doesn't suggest locations from an address, reassign bookings automatically when someone is off sick, or report per location, so those steps stay manual.
Step-by-Step Workflow
6 steps · 3 hours
Set up location profiles and service menus
Turn on locations and add each site with its address, phone, time zone and hours. Choose which services each location offers; not every site needs every service.
Your booking site has a page per location, so you can link each area's marketing straight to its location page.
Assign staff to locations
Assign each staff member to the locations they work at and set their hours per location, for example Monday to Wednesday downtown and Thursday to Friday at the second site. Each staff member connects their calendar so personal commitments block their time everywhere.
If someone moves between sites on the same day, leave a gap in their hours for travel, because buffers are set per service, not per location change.
Assign services to qualified providers
SchedulingKit doesn't have skill tags or routing rules; instead, assign each specialized service only to the staff qualified to deliver it, and set their hours by location. Clients booking that service are only shown those providers. For general services, assign everyone who offers them at each location.
Share bookings evenly with Round Robin
On Pro and Business, set services that several providers offer to Round Robin so bookings are assigned automatically. Choose Equal Distribution (spread bookings evenly) or Random. There are no revenue-based or weighted options.
Start with Equal Distribution and review each provider's bookings after 30 days to see whether anyone is consistently over- or under-booked.
Check the client-facing booking flow
Book a test appointment: choose a location, then a service, then a time. Confirm that only that location's services and staff appear, and that the booking lands in the right provider's calendar.
Handle absences and review regularly
When a provider is off, add a day off so no new bookings land on them, and reschedule their existing bookings yourself. Review bookings by staff member each month; SchedulingKit doesn't produce per-location reports, so use the API (Pro and above) if you need them.
Reschedule from the dashboard so clients get the updated time automatically.
Expected Outcomes
Tools Needed
Who This Is For
- Multi-location service businesses (salons, clinics, studios)
- Businesses with staff who split their week between sites
- Owners opening a second or third location
- Teams that want one client list across locations
Prerequisites
- A SchedulingKit account (Pro or above for Round Robin)
- Staff schedules and location assignments written down
- A list of which staff can deliver each service
- All staff calendars connected
Was this article helpful?
Frequently Asked Questions
Playbooks
Continue with these related playbooks
Zero No-Show Playbook
No-shows waste slots you could have filled, and most businesses rely on a single reminder to prevent them. This playbook stacks four layers that SchedulingKit can run for you: reminders at several points before the appointment, a deposit at booking, reschedule and cancel links with a cancellation deadline so clients move a booking instead of skipping it, and a follow-up message for clients who missed. It's built from features that exist today: reminders and SMS (Standard and above), Require Payment with deposits (Standard and above), manage-booking links and Workflows. No tool eliminates no-shows entirely, and results vary by business, so track your own no-show rate before and after.
Client Intake Automation
Chasing new clients for their details before a first appointment eats time you could spend with clients. This playbook moves intake into the booking itself and automates the welcome email. In SchedulingKit, intake questions are part of the booking form, so answers arrive with the booking. The client record is created or updated automatically from the booking email, and a Workflow (Standard and above) sends a welcome email with what to expect a set time before the first appointment. On Pro and above, Zapier can copy the new client into an external CRM. There are no file uploads, e-signatures or conditional questions, and SchedulingKit is not HIPAA compliant, so health histories and signed forms belong in a dedicated tool.
Sales Demo Booking Pipeline
Demo scheduling by email is slow, and interested leads cool off while you trade messages. This playbook sets up a pipeline that runs on its own once it's configured: a visitor answers a few qualifying questions while booking, the demo is assigned to an available rep, reminders and follow-ups go out automatically, and the booking lands in your CRM. It uses SchedulingKit booking questions, Round Robin (Pro and above), Workflows (Standard and above) and Zapier (Pro and above). SchedulingKit doesn't score leads, run conditional forms or manage deal stages; those stay in your CRM.
Ready to Get Started?
Sign up for SchedulingKit and implement this automation workflow today. Every tool you need is included.
Free forever plan available • No credit card required
When this isn't for you
This is not for you if your processes are too custom for off-the-shelf automation, the playbook gives you the 80% case. Skip if your workflow needs custom integration code.