Online repair booking that respects your bench.

Every shop has seen it. A sunny week in April, the booking link is wide open, and by Saturday noon there are nine bikes on the floor: two flat fixes, a brake bleed, four tune-ups and two full overhauls that each need most of a day. Nothing about the booking tool knew that an overhaul and a flat fix are not the same size.

The Service plan treats booking as a question of bench time, not calendar time. Each bookable service will carry a duration and a price. A basic tune-up might be an hour of bench time, a full overhaul four, a hydraulic brake bleed forty-five minutes per end. When a rider picks a drop-off day, Service will only offer it if there is enough mechanic time left that day for the service they picked.

That is the difference between booking appointments and booking work. A drop-off slot is really a promise about when the bike will be done, and the only way to keep that promise is to book against capacity.

You will set up a list of bookable services with a price, a duration and a description riders can understand: 'Standard tune-up, includes brake and gear adjustment, wheel true, safety check.' You choose which mechanics can take each service, and Service will assign an available one automatically. An e-bike motor diagnostic might only be bookable against the two people who hold the Bosch and Shimano certifications.

Booking rules come straight from the Service plan: a minimum lead time so nobody books a same-hour overhaul, buffer time between jobs, a visibility window so the calendar does not show slots three months out, and business hours that block booking when the shop is closed. For a mobile van, the same rules add a service area and a maximum drive time.

Each booking can be a job or an assessment. A drop-off for a known service is a job. 'It makes a noise and I don't know why' is an assessment: the rider books a short look, a mechanic writes a quote, and the quote converts into the job once it is approved.

Not every job fits a booking slot. Fleet managers want to send twelve bikes at once, and some riders just want a call back. The plan includes multiple request forms with your own intake questions, built on the same question types as the checklist builder, with address autocomplete, duplicate detection and your brand colors.

The request half of this is already running. A checklist template can be published to a public link, optionally behind an emailed code, with spam protection that refuses submissions until it is configured. Each submission raises a numbered request in the Requests inbox, carrying the rider's own description of the problem, and the counter triages it to a site, writes a quote and converts the approved quote into a job. Requests can also be typed in by hand with a contact name, email and phone when someone calls. Slot booking will be built on that same foundation rather than a second one.

Every booking and request keeps its lead source, so later on you can see whether riders found you through Google, a club ride sponsorship or a referral. The customer record itself lives in the erp.io CRM, which is live today.