Skip to content
Workshop Wrench

Capacity · CX · car count

Live

Online booking that becomes a real job — not a contact form

Missed calls and voicemail are silent car-count killers. A public book URL (and optional iframe) captures intent when the shop is under a car — then check-in converts the appointment into board WIP.

Primary persona: Customer + service advisor

The problem

What breaks without this process

Many “booking” tools only email the shop. Capacity is still managed in someone’s head, and check-in re-types everything.

Why it matters

Rationale — profit, risk, and shop floor truth

  1. 01

    Every booked slot that becomes a real Booking object can trigger reminders and diary visibility.

  2. 02

    Check-in → RO is the handoff from calendar to shop floor; without it, Thursday overbooks stay invisible.

  3. 03

    Website embed keeps brand experience on the shop site while the system of record stays operational.

  4. 04

    Public path is PLG-friendly: prospects can book the demo shop before they ever talk sales.

Proof from the live demo

Real UI — not a pitch mockup

Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.

live demo capture
Workshop bookings diary
Bookings — diary, check-in, ICS export path
live demo capture
Public online booking page for demo garage
Public book URL — website embed and demo-shop booking

Stage sequence

Step-by-step use case

Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.

  1. 01

    Share or embed book URL

    Action

    Publish tenant slug URL (app /book/[slug]) or iframe on WordPress/Squarespace/custom site.

    Why this stage

    Customers book without calling during peak bay hours — protects car count.

    Surface: Public bookOutcome: Booking channel live
  2. 02

    Customer submits appointment

    Action

    Select service intent, slot preference, contact, and rego; API creates Booking.

    Why this stage

    Real domain object — not a mailto form that dies in spam.

    Surface: /book/{slug}Outcome: Booking REQUESTED/CONFIRMED
  3. 03

    Advisor manages diary

    Action

    Review day list, confirm or adjust, send reminder events via comms adapters.

    Why this stage

    Capacity decisions stay with the shop; software makes WIP and no-shows visible.

    Surface: BookingsOutcome: Day plan trusted
  4. 04

    Check-in creates RO

    Action

    On arrival, check-in links vehicle and opens repair order on the board.

    Why this stage

    Calendar time converts to productive WIP without re-keying customer/vehicle.

    Surface: Bookings → BoardOutcome: RO on board

Related search intent

  • auto shop online booking widget
  • workshop booking software
  • public booking embed garage

Run this flow in Workshop Wrench

Start a trial or open the seeded multi-tenant demo — same processes, real data.