The concurrent resolution problem you're describing is exactly what we deal with. When a staffing coordinator has 15 interviews to book across shared interviewers, confirming one cascades into others. We track pending holds, rank by urgency, and when a confirmation on one thread invalidates a proposal on another, Vela detects the conflict and re-proposes. Theres
The only other alternative is a booking link but this, slows down business, doesnt work in many many real life situations and more :)
The only other alternative is a booking link but this, slows down business, doesnt work in many many real life situations and more :)