AVAILABILITY MANAGEMENT

Scheduling rules and call readiness

First-party availability rules reduce scheduling friction while maintaining a conservative v1 boundary before two-way calendar sync.

i

Availability rules are seeded. Form controls are static in this demo.

Current Rules

Tuesday Window

Active
Time 09:00 – 12:00
Timezone Europe/Berlin
Lead time 24 hours
Blackout March 18, 2026

Thursday Window

Active
Time 13:00 – 17:00
Timezone Europe/Berlin
Lead time 24 hours
Blackout None

Rule Configuration

To add new availability windows, specify day, start time, and end time. Each window inherits the default timezone and lead time above.

Blackout Dates

March 18, 2026

Blocked

Explicit blackouts prevent scheduling conflicts on dates where the expert is unavailable regardless of recurring rules. Blackout dates override any active availability window for that day.

Why rule-based first? Two-way calendar sync (Google, Microsoft) introduces OAuth complexity, token refresh, and privacy considerations. v1 captures scheduling intent through explicit rules. Calendar sync is planned for v2.

v1 vs v2 Boundary

v1 — Current

Rule-based windows Blackout dates ICS export Timezone ownership

v2 — Planned

Two-way Google/Microsoft sync Conflict detection Auto-hold slots