Rollout playbook
Implementation guide
A practical plan for rolling kailenty out to a team and then a company. Start small, prove the flow with one group, and standardise from what actually worked rather than a top-down spec. This guide is opinionated on purpose.
Before phase one, connect Microsoft 365. If you have not yet, work through the Microsoft 365 setup guide first — everything below assumes calendars are connected and consent is granted.
The plan
A phased rollout
Three phases, each with a clear goal. Do not skip the pilot — the conventions it produces are what make the later phases fast.
Pilot with one team
Goal. Prove the flow end to end with a team that books a lot of meetings.
- Connect Microsoft 365 and confirm a few real bookings land on the right calendars.
- Pick a high-volume team — sales discovery or recruiting screens are ideal first candidates.
- Set their availability, create one or two link types, and let them book live for a week.
- Collect what felt off: wrong buffers, awkward link copy, anything an invitee stumbled on.
Expand to adjacent teams
Goal. Turn what worked into a repeatable setup for the next few teams.
- Write down the conventions the pilot settled on — naming, durations, default buffers.
- Add the next teams and reuse those conventions instead of starting each from scratch.
- Introduce round-robin pools and label routing where a team shares incoming requests.
- Remove the kailenty badge and apply your branding before links go to customers.
Standardise across the company
Goal. Make kailenty the default, with light governance so it stays tidy.
- Document the standard link types and who owns each pool.
- Set role expectations: who can manage pools and labels, and who only books.
- Review unused links and stale availability on a regular cadence.
- Fold scheduling into onboarding so new hires are set up on day one.
Get the basics right
Availability, buffers, and overrides
Availability is the foundation everything else sits on. Spend time here in the pilot and the rest of the rollout gets easier.
Start with honest hours
Set working hours people will actually keep, not aspirational ones. A calendar that over-promises creates double-bookings and reschedules.
Use buffers deliberately
Add buffers before and after meetings for travel, notes, or back-to-back recovery. A short minimum-notice window stops same-minute bookings.
Override for the exceptions
Keep base availability stable and use date overrides for holidays, conferences, and crunch weeks rather than editing your standing hours each time.
kailenty offers slots from the intersection of these rules and each host’s real Microsoft 365 calendar, so the cleaner the rules, the fewer surprises invitees hit.
Share the load
Round-robin pools and label routing
Once a team shares incoming requests, pool their availability so one link books whoever is free. Round-robin distribution spreads meetings across the pool to keep the load even, and you can build multi-person panels with ranked fallbacks when a request needs a specific group rather than a single host.
Use labels to route by type — for example, sending enterprise enquiries to one group and self-serve questions to another. Define the labels and pools during phase two so the rules are settled before more teams come on. Pooling, round-robin, and label routing are Pro features.
For the full picture of how distribution and panels behave, see team scheduling.
Make it yours
Branded booking pages
Before links reach customers or candidates, make the booking page look like you. On Pro you can remove the kailenty badge and present your own branding, so the page a guest lands on feels like part of your company rather than a third-party tool.
Agree on one set of branded defaults during phase two — the same look, tone, and meeting durations — so individual hosts are not each inventing their own. Consistency here is what makes external links feel deliberate.
The Free plan includes one branded booking page with the kailenty badge; removing the badge and branding across the team is part of Pro. See pricing for the split.
If you hire
Recruiting workflows
Recruiting is one of the strongest first pilots because the pain is obvious and the win is fast. With candidate self-scheduling, you send a link and the candidate picks a time that fits the interviewers’ real availability — no back-and-forth email threads.
For panels and harder-to-align slots, ranked-time voting lets people indicate which times work best, so you can confirm the slot with the broadest agreement. Pair this with label routing to send each role’s candidates to the right interview group. The recruiting tools are part of Pro.
Help people switch
Training and adoption
Train owners first
Give pool and label owners a short walkthrough of the settings they control. They become the local experts the rest of the team asks.
Make the easy path obvious
Put the right link in email signatures, templates, and handover docs so the kailenty way is the path of least resistance.
Show, do not mandate
A two-minute demo of a real booking lands better than a policy memo. Let the pilot team tell their own story to the next group.
Build it into onboarding
Add connecting Microsoft 365 and setting availability to new-hire onboarding so people start booked-ready from day one.
Keep it clean
Governance at scale
Light governance keeps a company-wide rollout from sprawling. A little structure up front — clear roles, a tidy set of pools, and a regular review — is far easier than untangling it later.
Roles, not free-for-all
kailenty uses role-based access, and some actions — managing team pools, labels, and certain settings — are reserved for managers and admins. Decide who holds those roles before you scale.
Workspaces stay tenant-scoped
Each workspace is isolated to your Microsoft 365 tenant. Data does not leak between organisations, and access follows the identities you already manage.
EU data residency
Scheduling data is stored and processed in the EU and kailenty is built to be GDPR-compliant, which keeps procurement and security reviews shorter.
Review on a cadence
Set a recurring check to retire unused links, confirm pool membership still matches the team, and remove access for people who have moved on.
Planning a larger rollout?
We are a small team and happy to think through your rollout with you — pools, routing, or how to phase it across departments. Tell us about your teams and we will help you shape a plan.
More resources