The Pooled availability algorithm - Longest idle time

The logic behind our Pooled availability algorithm is based on the longest idle time concept. 

The longest idle time refers to the amount of time that has passed since a booking was last created for each Booking page. Note: the meeting time does not matter.

The Pooled availability algorithm assigns the next booking to the Booking page with the longest idle time (i.e. the Booking page for which the the longest time has passed since a booking was last made). If there are a number of Booking pages with the same idle time, then the algorithm picks one at random. 


  • The idle time is tracked per Master page AND per Event type combination. This means that if a User receives bookings from more than one Master page, each Master page will have separate idle times. Also, if a User receives bookings from more than one Event type in a single Master page, they will have two separate counts.

  • The idle time is not considered if a Booking page has been deleted, disabled or has connection errors.

  • New Booking pages added to a Master page (this happens as soon as the User clicks Save) are considered to have the longest idle time. This means that new Booking pages will be highest priority for new bookings.

Note If you are using Pooled availability with priority and multiple Booking pages have been assigned the same priority, then longest idle time will be used to choose between them.

Was this article helpful?
Thank you for your feedback!