Two team-scheduling patterns: round-robin (distribute) and pooled (combine). Pick the one that matches your meeting structure.
Round-robin
Use when a meeting needs exactly one person and you want to distribute load. Example: every "Discovery call" goes to whichever rep is next in line.
Configuration: Booking page settings → "Multi-host" → Round-robin → add team members. The system rotates assignment, skipping members who are unavailable for the proposed time.
Pooled availability
Use when a meeting requires multiple specific people (e.g. solutions engineer + account executive). The booking page only shows slots where all required hosts are free.
Configuration: Booking page settings → "Multi-host" → Pooled → add required attendees. Optionally add "any one of" lists (e.g. any SE).
Failover
For round-robin, configure a fallback: if the assigned rep doesn't respond within X hours after the booking, the meeting auto-reassigns to the next rep.
Tips
- Round-robin works best with 3+ reps; with 2 the rotation feels arbitrary.
- Pooled availability tightens calendars fast — for high-velocity teams, schedule pooled meetings off the AI agent rather than from a generic booking page.
- Audit round-robin distribution monthly. If one rep is absorbing 80% of bookings, the rotation has a bug or someone is over-blocking their calendar.