Service Request Form Template

Field service lives and dies on first-visit completion: did the right person arrive at the right door with the right tools and enough context to finish the job? Every failed visit, whether a wrong address, a missing gate code, or a repair that turned out to be an installation, costs a truck roll and a customer's patience. This form is a dispatch document disguised as a contact form, and every field on it exists to protect that first visit.

Every field guards the first visit. The service dropdown is the tooling question: an installation, a repair, and an inspection put different equipment on the truck and sometimes different people in it, so the request self-sorts before a coordinator touches it. The address block is structured rather than free text because "the blue house past the church" does not geocode, and a clean address is what your routing software runs on. The phone number is required and framed with candor: visits get confirmed by a person, and technicians call when they are twenty minutes out. The urgency selector separates the burst pipe from the annual service, and its emergency lane tells your dispatcher which requests to read first. The job description placeholder asks for symptoms, model, and duration, the three details that let an experienced tech guess the fault and load the likely part. The access-notes field is the quiet hero: gate codes, parking realities, and a dog named Bruno prevent more failed visits than any scheduling system.

What the request omits. An appointment-slot picker, since this form promises a confirmation call instead, because slot pickers imply a live calendar and field schedules shift by the hour, and a promised callback you keep beats an instant booking you have to move. Payment details and serial numbers stay out as well; both belong in the job itself, not the request.

Trades that dispatch with it. HVAC, plumbing, and electrical companies, appliance repair shops, garage-door and locksmith outfits, IT field service, cleaners, and property services, anyone whose product arrives in a van.

Adapting it to your trade. Rename the service lanes to your trade's vocabulary and add lanes for your top three job types. Turn on email notifications so the dispatcher sees requests the moment they land, or wire a webhook into your job-management tool with the urgency answer in the payload for automatic prioritization. This form will live on a public website, so the built-in layered spam protection (honeypot, timing checks, and an invisible challenge that escalates only under abuse) matters more than it might seem. Embed it inline on your "book a service" page or behind a popup button, and both snippets are on the Share page.

Protect the first visit. Every question here either routes the request, reaches the customer, or prepares the technician. Keep that filter when you customize: if a field does not serve the visit, it is friction.