Appliances playbook

Every fault, booked with the right part on the van

Your genie collects the appliance, the fault, the address, and the access notes, checks it against your booking rules and parts wait times, and drops the repair straight into your calendar.

The van shows up without the part because the model was never asked
Phone tag loses the repair to the next name on the list
Double bookings and gaps when jobs are scheduled from memory
You are quoting and scheduling at 9pm instead of resting

The architecture

Booking is a data flow: capture the appliance and fault, qualify it, notify the calendar, resolve it as booked.

How the data moves Capture, qualify, notify, resolve. Every conversation ends as a record, not a lost call.

Intake that never forgets the model number

A repair booking is only useful if the engineer arrives ready. Your genie asks the same questions your best office person would, in the same order, every time, and only offers slots that fit your rules and any parts-order wait time.

What it captures on every booking

Appliance type, brand, and model number

The fault and any error code showing

Service address and access notes

Preferred time within your hours

Name and best contact number

Whether it is warranty or a chargeable repair

The genie only offers times that respect your minimum lead time and any part you need to order in, so the van never rolls out to a job it cannot finish. When a job is too complex to book cleanly, it moves to a field engineer handoff with everything already captured. See how it all connects in the architecture guide.