Independent repair shops and in-house facilities teams can take job requests on a brochure site. The form captures the fault and a preferred date so the scheduler is not reconstructing voicemails.
Notify the dispatcher.
Emergency, routine, warranty, follow-up.
Placeholder: make, model, serial, symptom.
Do not treat the preferred date as booked until you reply.
A repair request form is how a customer or employee reports something broken and asks for a visit or a workshop slot. US HVAC and appliance firms and UK high-street repair counters both need make, model, symptoms, and access times. It is not a warranty claim system and not a parts-ordering ERP.
The request pack’s type field can mean in-warranty, out-of-warranty, recall, or follow-up. Preferred date is the access window, not a promise you will be there.
A photo helps; a serial number helps more. Neither should be mandatory on a phone form if it kills conversion.
Do not take full payment card data here. Quote after diagnosis.
ServiceTitan and similar exist for fleets. HTML is how a two-van shop starts.
Next to hours and the service area map.
Graduate when you need van routing and parts.
Still primary for emergencies. Use the form for non-urgent jobs overnight.
Manufacturer portals are separate. This form is your own book of work.
Squarespace plumber sites can host this form. Route notifications to the on-call mobile.
UK consumer law and US state repair-estimate rules still apply to how you quote—not to this HTML.
Ask for a Drive/iCloud link in details, or use a file-upload form.
No. Your job system creates the work order after you accept.
State them on the page copy. The form does not calculate fees.
Use two forms so employee jobs do not mix with paying customers.
Capture repro steps, severity, and environment from users on your site.
Let customers pitch product ideas with context, not a one-line tweet.
A lighter intake than a feature request for culture, process, or UX niggles.