Every row here is a bookable service: "30-minute consultation", "in-person meeting", "intro call".
An "event" is not a date on a calendar
The name misleads. An event here is not something happening on a particular day — it is a pattern that gets booked over and over.
You define availability as days of the week — say Saturday to Wednesday, 9 to 17 — and that repeats every week. For a holiday or time off, you block the specific date separately.
So if you are looking for "next Thursday's event", that is an appointment, not an event.
Four numbers decide what a visitor sees
How long a slot is, the gap between slots, the minimum notice before a booking, and how far ahead someone may book.
When a time you expected does not appear on the site, the answer is almost always one of those four rather than something being broken. A 24-hour minimum notice, for instance, means today is not bookable at all.
Round-robin takes the choice away from the visitor
An event can belong to one person or rotate between several colleagues. When it rotates, the booking goes to whoever is next in turn and the visitor does not pick the person.
If you want visitors to choose who they see, make one event per person rather than one round-robin event.
Custom fields are asked at booking time
You can define questions to ask when someone books. The answers are stored on the appointment itself.
That means answers on past appointments do not change when you later edit or remove a field — whatever was asked stays as it was asked.
An event with appointments cannot be deleted
This is a database constraint, not a warning you can click past. While any appointment points at an event, deleting it is refused.
The right move is to deactivate it: it comes off the site while the bookings already taken, and their history, stay intact.