SavvyCal has a blocking system, but it is currently unusable for real-world unavailability (vacations, sick days, unexpected closures) because: Blocks must be set calendar by calendar Blocks must be set day by day — there is no date range selection The only alternative is to configure keyword-based detection inside each availability schedule separately, which is fragile and time-consuming The result: taking a week off requires either a long series of manual operations across every calendar and every scheduling link, or a complex setup that most users will never maintain correctly. It is not a realistic option for solo professionals. Expected behavior: A top-level "Unavailability" feature — separate from and overriding all availability schedules and calendar checks — where the host defines a date range (start date → end date) that instantly blocks all slots across all scheduling links, with no per-calendar or per-day steps required. This should work like a master off-switch: set it once, everything goes dark for that period, invitees see no available slots, and the host can leave without worrying. Current behavior: Day-by-day, calendar-by-calendar blocking, or keyword detection per availability schedule. Neither scales to even a one-week vacation. Use case: Any solo host who needs to close their schedule for a period — vacation, illness, public holidays — and wants to do it in a single action with full confidence that no slot will slip through.
