Set the shape of a service
A length, a gap after it, and whether it confirms itself or waits for the provider.
Booking with payment and delivery
Most booking tools assume one calendar and one kind of appointment. Real services vary in length, need a gap after each one, and have money riding on whether they happen.
Named by what it does, not who it was for. The screens below are illustrations we drew — never customer software.
Each provider runs their own booking page. Services carry a length and a gap, hours and holidays are built in, and every booking is tracked from reserved to paid, delivered and settled.
A length, a gap after it, and whether it confirms itself or waits for the provider.
The calendar already leaves out holidays, closed hours and each booking’s gap.
Self-confirming services confirm on booking; the rest wait for the provider.
Payment is due before the slot, attendance is detected from the call, and payout follows.
Contact
Email what you are trying to fix. We will say whether a product covers it, whether it needs a build, or whether we should step aside.