What changed
For team event types, StretchSchedule offers a slot when any mapped host is free (the union of everyone's availability). Previously, when the invitee picked that slot, the host was chosen purely by load-balancing — which could hand the booking to a teammate who was not free at that exact time, causing a silent mis-assignment or double-book.
Availability-aware routing fixes this: at booking time the router first narrows the roster to the hosts who are genuinely free at the chosen slot (respecting buffers and, where connected, two-way calendar busy times), and only then applies your round-robin or weighting rules.
- Round-robin: the rotation is restricted to free hosts before a host is picked.
- Collective: the booking only proceeds if every required member is free.
- If the union offered a slot but no mapped host is actually available at book time, the invitee is asked to pick another time instead of being wrongly assigned.
What you need to do
Nothing changes in how you build event types. When this is enabled for your account, existing team event types automatically start assigning by real availability.
There is also a preview you can use to check, for a given time window, which hosts are free and who the rotation would assign — without creating a booking.
Availability
Rolling out. Availability-aware routing is released behind a feature flag and enabled per account. With it off, routing behaves exactly as before.
Was this helpful?
Help us improve this article
Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.