Booking 2.0 closure

Från lead till bokning med synlig recovery när något skaver

Booking ska inte bara skapa en tid. Den ska visa konflikt, ombokning, avbokning, reminders, staff-routing och nästa återhämtningssteg utan att kunden eller teamet tappar förtroende.

Booking hubReliabilityRecoveryConnector matrixExport checklist

Current decision

88% klar, kalender- och multi-staff proof kvar

Flow har booking/recovery-ramverket. För 100% behöver vi externa Google/Outlook-credentials, riktig multi-staff proof och arkiverad conflict recovery.

4

proof lanes

6

checks

4

live proof

Booking proof lanes

Det som gör booking redo för riktig drift

Green with provider proof pending

Conflict handling

Flow exposes conflict states and recovery copy before a booking is confirmed.

  • calendar conflict
  • slot unavailable
  • manual override
  • provider reconciliation

Green

Cancel and reschedule policy

Cancel/reschedule states have customer-safe language, policy outcome and next action.

  • cancel policy
  • reschedule window
  • customer notice
  • audit event

Green

Reminder orchestration

Reminder status is visible with owner, channel and fallback when delivery is uncertain.

  • email/SMS lane
  • retry state
  • delivery uncertainty
  • missed reminder recovery

Baseline green

Multi-staff routing

Booking can route by staff, service, fallback owner and recovery slot.

  • staff assignment
  • service duration
  • fallback staff
  • recovery slot

Acceptance

Go-live checks

  • A lead can become a booking without duplicate booking state.
  • Conflict, cancel, reschedule and fallback states are visible to ops and customer-facing copy.
  • Reminder delivery has retry and recovery visibility.
  • Multi-staff routing never hides who owns the booking.
  • Google/Outlook proof is archived before production-grade calendar claims.
  • Recovery flow tells the team exactly what to do next.

Remaining external proof

Det som kräver riktig kalenderdrift

  • Run live Google Calendar sync proof with tenant-owned credentials.
  • Run live Outlook sync proof with tenant-owned credentials.
  • Archive multi-staff booking proof with two real staff calendars.
  • Capture one conflict recovery and one reschedule recovery from real flow.