Per-booking cancellation policy
The cancellation policy is captured at booking time as part of the record. When a no-show fee fires, you can see exactly what policy applied — never disputable.
Vertical pack · Coaches
Recurring sessions and cancellation policies that enforce themselves.
Built for coaching, therapy, and consulting practices. Recurring booking logic, per-client cancellation policies, and a defendable record for every session — so when a client disputes a no-show fee, you've got the receipt.
What we hear from coaches
The scheduling problems that compound.
- Clients disputing no-show fees with no record to back up the policy.
- Recurring weekly sessions getting silently double-booked when the client also walks in.
- Cancellation rules that drift across team members because they're enforced in spreadsheets.
- Calendar conflicts when the coach edits in Google but the booking system doesn't reflect it.
Where the deterministic engine pays off
Built for how coaches actually run.
No duplicate recurring bookings
Recurring weekly sessions are created with a stable identifier. Even if the system retries, the same booking is never created twice. The database itself enforces this.
Two-way calendar sync
Google Calendar and Outlook sync in both directions. If a client double-books in their personal calendar, Schediq sees it. Conflicts resolve in a way that's recorded — no silent overwrites.
Records back you up on disputes
When a client says 'I never agreed to that', you click the booking. You see exactly what they selected, when, and what policy applied. Disputes resolve in minutes.
The flow
From customer intent to audit-grade decision in seconds.
- 1
Client schedules session
Public booking page with the cancellation policy required at booking time.
- 2
Schediq matches client to coach
Client's needs matched to the right coach by specialty fit. The reasoning is recorded.
- 3
Calendar sync out
Booking pushed to the coach's Google or Outlook calendar.
- 4
Recurring sessions generated
Future weekly sessions created safely — no duplicates, even under retries.
- 5
Records kept forever
Every booking, override, and policy enforcement saved. Disputes resolve by reading the record, not by memory.