As soon as two people give appointments, a calendar in your head stops working. This guide shows how appointment booking for a team runs cleanly: one staff calendar for scheduling everyone, services and hours per person, roles, a fair spread of bookings, and the sick day that tips every plan over. Written for teams of two to fifteen, whether salon, practice or workshop.
One calendar per person or one shared view?
Every team asks this, and the answer is both, drawn from the same data. Each person needs their own calendar because they have their own hours, breaks and services. You need the shared view because it is the only place you can see where there is room today and who is overflowing. Two separate calendars that someone reconciles by hand are where every double booking starts.
In practice that means one system where every staff member has a column and a colour. The customer books with Lea, the appointment appears in Lea's column and in your day overview. If something changes, it changes in both places, with no notes and no group chat. A good team calendar works out free slots from the rotas itself, instead of you typing them in.
For a solo business hiring its first employee, this is the moment to leave the paper diary or the private phone calendar behind. Both work for one person. For two, they become a daily source of errors, and from three somebody asks every morning who is actually free at ten.
Pick a person or 'anyone': what customers should choose
On the booking page there are two routes. The customer picks a person first and then sees that person's free slots. Or they pick the service first and see the free slots of everyone who offers it. The second route fills the calendar better, the first keeps regulars loyal. Most businesses need both.
The answer is an 'anyone' option next to the names. Someone who has had the same stylist for years taps her name. Someone new, or just in a hurry, takes 'anyone' and gets the earliest slot in the team. With terminio.ai customers choose a specific person or 'anyone' on the booking page from the Pro plan, and the phone assistant in Pro Voice asks callers for their preferred person too.
One thing matters: 'anyone' must not always land on the same person. If the system stubbornly fills the first column, the owner has no room left at 2 pm while the new colleague sits idle. More on that in the section on load.
Services, working hours and rooms per staff member
Not everyone can do everything. The apprentice cuts but does not colour yet. The physiotherapist with the lymphatic drainage certificate is one of four. Anyone bookable for everything gets appointments they cannot do, and the rebooking lands on your desk. So every service carries the list of people who offer it. A service nobody offers should not be on the booking page at all.
Working hours belong to the person, not the business. The shop is open 9 to 7, but Jonas works Tuesday to Saturday from 10 to 6, and Marlene has Wednesdays off. A weekly rota per person, with exceptions for individual weeks, is the base from which free slots are calculated. Holiday and sickness go in as absences and disappear from the booking page at once.
Then there is the second limit: rooms, chairs, lifts. Three beauticians and two treatment rooms means at most two can work at the same time. If you do not model that limit, you overbook. The simple fix: set the room up like a person and tie the service to both. The clean fix: a system that treats rooms as a constraint of their own.
- Record per service who offers it, rather than enabling everything per person
- A weekly rota per person, in quarter hours, with exceptions for single weeks
- Buffer time per service: five to fifteen minutes for clean-up and handover
- Model rooms and chairs as a second limit whenever there are fewer than people
- Absences with from, to and reason, so the booking page is right immediately
Roles in the staff calendar: who sees and changes what
One shared login for everybody is convenient and the worst idea in this whole article. Everyone sees everything, anyone can delete anything, and when an appointment vanishes, nobody did it. Whoever leaves takes the password with them. What works is one login per person, with a role that fits their job.
In practice two roles are usually enough. Management sees everything: calendars, prices, revenue, customer records, settings. A team member sees their own day: appointments, customer name, phone number, service, time. Not the others' appointments, not the revenue. That is exactly how terminio.ai is cut: you hand out access in the app with an email and password, and after signing in the person sees only their day. When someone leaves, you pause the access with one switch.
Whether staff may move or cancel their own appointments is each business's call. In small teams, yes, or everything runs through you. From eight to ten people a reception desk that owns the calendar pays off, and the team reads along.
Balancing load and catching sick days
The biggest problem in salon team scheduling is uneven load. Regulars book the experienced staff, the new hire sits idle and learns nothing. Three levers help. First: send 'anyone' bookings preferably to the person with the most free hours. Second: actively steer new customers to new colleagues, with a line on the booking page or on the phone. Third: an honest introductory price for the colleague still settling in.
Then the sick day. The message arrives at 7 am, the first customer is at the door at 9. The order: enter the absence so nothing new gets booked. Then go through the day's appointments: what can someone else take, what has to move. For the moves you need to reach customers fast, and fast today means WhatsApp, not a call list. A short message with two alternative times settles most cases in minutes.
Doing that from your phone means you are done before the shop opens. With terminio.ai every booking, whether online, by phone or via WhatsApp, lands in the same calendar, and your team sees the change the next time they open the app, with the next appointment on the smartwatch too.
Appointment booking for teams: the most common mistakes
The mistakes repeat across every trade, from the hairdresser to the workshop. They do not cost money right away, just a little time every day and a customer every few weeks. Read the list once when setting up, and once more at the yearly tidy-up.
- One shared login for everyone, with no roles and no way to trace changes
- No buffer times, so every late arrival pushes the whole afternoon back
- Everyone bookable for every service, although only two people offer it
- Working hours equal to opening hours, although nobody is there 9 to 7
- Rooms and chairs not modelled as a limit, three appointments on two chairs
- Holiday in the group chat instead of the calendar, and the booking page knows nothing
Setting up a team calendar: the right order
Setup takes an afternoon if you do it in the right order. Services first, then people, then logins. Finish with a test: book every service with every person yourself, as a customer. Wherever the system offers a slot you could not honour, that is where the mistake lives.
- Create the services with duration, price and buffer time
- Create the people, tick their services and enter each weekly rota
- Model rooms or chairs as a second limit if you need to
- Hand out logins, one per person, each with the right role
- Test the booking page: every service, every person, once with 'anyone'
- After two weeks, check whether the load across the team is even
