Appointment Scheduling

A booking form is worthless if the availability is fiction

The failure mode of most booking widgets in this space is the same. The widget keeps its own calendar, the shop keeps the real one, and the two drift apart within a week. Customers book slots that are not available, the shop calls to move them, and everyone learns that the online booking is really a request form.

So availability had to come from the shop management software the shop already runs, live, rather than from a schedule someone syncs or re-enters. If the shop books a job over the counter, that slot has to disappear online without anyone doing anything.

That integration is the hard part of the product and the reason it works. Everything else is interface.

Installation had to be something a shop can do

These are not businesses with a web team. If installing the scheduler requires a developer, it does not get installed, and the product fails for reasons that have nothing to do with whether it is good.

So the whole integration is a script tag on the site and a class added to whatever button they already have. Whatever the shop uses as its Book Appointment button becomes the trigger, in place, with the design they already have.

That kept it out of the category of change that requires scheduling a developer, which is the category where good tools go to die.

Verification without making people sign up

Asking a customer to create an account to book a repair is the fastest way to lose the booking. But with no verification at all you collect junk bookings and have no way to confirm the person is reachable.

The compromise is an emailed code. The customer enters their details, receives a code, and enters it to confirm. It takes a few seconds, it proves the address is real, and it does not create a password nobody wants.

That same verified address is what lets them come back later, which is the part that removed work from the shop.

Letting customers manage their own appointment

Once verified, a customer can reschedule or cancel without calling. That is a small feature and it removed a meaningful share of the calls the front counter was taking, because a large share of inbound calls to a shop are not new work, they are changes to existing work.

It also improves the schedule quality. A customer who can move an appointment in ten seconds does that instead of not showing up, and a rescheduled slot can be filled where a no-show cannot.

The shop side stays configurable

Every shop runs differently. Bay counts, job types, how far ahead they will take bookings, and which work they want online at all. The shop-side dashboard lets them set that up themselves rather than having it configured for them at onboarding and then never revisited.

The design target throughout was a service writer who is busy. Fast changes, few clicks, nothing that requires exhaustive data entry to complete a simple action.