Everything in the products post assumed one of you. One calendar, one price list, one person the receptionist books for.
Most service businesses are not one person.
A salon has stylists. A clinic has practitioners. A law firm has partners who each handle different work.
And the moment there is more than one of you, the customer's question changes shape. It stops being "when are you free?" and becomes "who does vivid colour, and when is she free?"
This post, the last in the series, is about the suite that answers that question. It is the same records-not-code idea from the products post, applied to people.
Structured data, one more time
Recall the split from the knowledge post: unstructured data is prose you explain, structured data is records you list. The two are handled differently because they fail differently.
A bio that is slightly loose is fine.
A price, a duration, or a booking link that is slightly loose is a customer standing in the wrong place at the wrong time.
Your team is structured data of the strictest kind:
- Every employee has the same fields.
- Every service has an exact price and an exact duration.
- Every booking must land on exactly one person's calendar.
So the team suite follows the same rule products did: records through dedicated endpoints, never prose, never code.
Employee records
Alongside the product catalogue sits a second set of records: your team.
Each employee record holds two kinds of information:
- What a customer wants to know: name, job title, bio, photo, expertise, languages, location, timezone.
- What the system needs to know: their own calendar link, their status, their display order.
Five endpoints manage the full lifecycle:
- Add an employee.
- Fetch a single record.
- List the active team.
- Update a record.
- Remove someone.
The same pattern as products, and the same consequence: the team section on this website, and every individual profile page with its booking embed, renders from these records live.
A stylist joins. A bio changes. Someone leaves.
The website reflects it without a code change, and so does the receptionist, because both read the same records.
Services belong to specialists
Here is where it gets richer than products. In a team business, services are not a flat list; they belong to people, at that person's prices and durations.
A real example, from a salon running this today. Three stylists.
- The lead stylist's menu runs from a $15 bang trim to $450 extension installations, about forty services in all.
- The head colourist carries the vivid and fantasy colour work the others do not.
- The third stylist is the one you book for men's cuts and shape-ups.
Some services overlap. Many do not. And two stylists can charge different durations for the same treatment.
Each specialist's services come straight from their own Calendly. Calendly Teams is Calendly's multi-person tier: every team member has their own event types, their own prices, their own real availability. The employee record links to the Calendly member, and from there the receptionist can see, per person, exactly what they offer.
So the conversation the customer actually wants becomes possible.
"I want balayage and a keratin treatment" is matched to the specialists who do those services, quoted at their real prices, and booked into the right person's calendar at a time that person is genuinely free.
Not a generic slot on a shared calendar. The right chair, the right hands.
The setup is an agent, not a form
Now the honest part. Wiring this up is the most involved operation in the whole system:
- Import every team member from the Calendly organisation.
- Create or verify each person's event types.
- Decide which services are publicly bookable and which are not.
- Teach the receptionist the whole roster: who does what, at what price, with which booking rules, written into its system prompt.
That is not a settings page you click through. So it is not sold as one.
The team upgrade ships as a dedicated setup agent. You talk to it, and it runs the whole sequence with you step by step: discovery, employee import, event type setup, verification, then the booking flow and the receptionist's updated instructions.
You answer questions. It does the operation.
This is also why the team suite is not part of the $550 bundle. The bundle covers everything a solo operator needs, and for a solo operator this entire post is machinery you would pay for and never switch on. Teams are a genuinely different, heavier setup, so it is priced separately, and it comes with the agent that does the heavy part for you.
Where this leaves you
One roster, three readers: the website's team pages, the receptionist's matching, and each specialist's own calendar.
Change the roster and all three agree, which by now you will recognise as the theme of the whole series.
And that is the series, complete.
If your business is at the size where this post is the one that mattered, you are past the self-serve stage, and the right next step is a conversation rather than a checkout. Book a call, tell us how your team works, and we will map the setup with you.