Describe your shop or fleet workflow. Makeform builds an online vehicle service request form for vehicle details, symptoms, photos, contact information, and preferred service times.
Route requests to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it, or send it to the Makeform builder. Each field outline previews the requested structure.
Audience
Drivers requesting diagnosis or repair from an auto shop
Format
Mobile-friendly intake with symptoms and appointment choices
Prompt size
339 chars
Example form structure
Mobile-friendly intake with symptoms and appointment choices
Customer and vehicle details
What is the vehicle doing?
When does the symptom happen?
Photos or short videos
Preferred service windows
Suggested routing tags
Routine service
Needs diagnosis
Vehicle unavailable
Ask when the symptom occurs. Speed, temperature, warning lights, and driving conditions add useful context.
Step 1
Identify
customer, vehicle, asset number, and mileage
Step 2
Describe
symptoms, timing, warning lights, and photos
Step 3
Triage
availability, urgency, category, and location
Step 4
Schedule
service window, routing, and follow-up preference
Better service intake
Structured intake captures identification, symptom context, photos, and availability in one submission.
Require the identifiers your operation uses, plus mileage and location when relevant.
Ask when the issue occurs and which conditions or warning lights accompany it.
Collect category, availability, and contact preference with the issue.
Built around the requester
Choose a workflow, then add your categories, identifiers, locations, and schedules.
Capture vehicle details, symptoms, photos, preferred times, and contact method.
Use asset IDs, departments, locations, status, and replacement-vehicle needs.
Request service by mileage, date, or engine hours and attach supporting records.
Ask about address, access, parking, vehicle movement, and parts on hand.
Request workflow
Describe the intake, refine the fields, and publish a request link.
Name the requesters and the identifiers, categories, locations, and scheduling details you need.
Require essential fields and reveal focused follow-ups for selected concerns.
Share it from a booking page, QR code, driver portal, or email.
Use category, status, location, and timing to organize the response.
Intake options
Vehicle-specific questions make a request easier to understand and route.
Field guide
Six sections identify the vehicle, explain the concern, and prepare the next response.
Requester
Collect the customer or driver name, contact details, and preferred method. Add department or supervisor fields only when routing needs them.
Vehicle identity
Ask for year, make, model, plate, VIN, asset number, mileage, and location as needed. Require only the identifiers your workflow uses.
Concern
Use a category for sorting and a narrative for detail. Ask what happened, when it began, how often it occurs, and under which conditions.
Vehicle status
Ask whether the vehicle starts, moves, is parked, or is at a shop. Collect warning lights and observations for team review.
Evidence
Uploads can show dashboard indicators, damage, leaks, tire condition, estimates, or inspection notes. Explain which files are useful.
Timing & follow-up
Ask when the vehicle is available, where service should happen, and how to respond. Label times as preferences until confirmed.
Related tools
Connect intake with inspection, repair, maintenance, and general service workflows.
Create walk-around checks for condition, tires, lights, fluids, and photos.
Open toolStructure vehicle information, requested work, and repair details.
Open toolCollect repeatable results across assets, drivers, branches, and locations.
Open toolAdapt maintenance intake to machinery, tools, and equipment.
Open toolBuild broader intake for vehicles, facilities, equipment, or teams.
Open toolFAQ
Answers for repair shops, fleet managers, service advisors, and drivers.
It is an intake form for requesting maintenance, diagnosis, or repair. It identifies the requester and vehicle, records the concern, and collects context for service-team review.
Usually require contact details, a searchable vehicle identifier, mileage, issue category, symptom description, vehicle status, and availability. Choose VIN, plate, or asset number for your workflow.
Ask what happened, when it began, how often it occurs, the operating conditions, warning lights, noises, smells, leaks, vibration, and recent repairs. Combine focused choices with a long-answer field.
Yes. A scheduled path can ask for services due, target mileage, date, or engine hours. An unexpected-issue path can ask for symptoms, warning lights, photos, and operating status.
Yes. Add upload fields with instructions for dashboard, damage, or leak photos. Keep a text description because images may not capture an intermittent symptom.
No. Label choices as preferred service windows and explain that the team will follow up. This collects availability without presenting a request as a confirmed booking.
Yes. Makeform offers unlimited free forms and responses. You can generate, edit, publish, and use the form without a response cap; the paid tier removes the Makeform badge.
Yes. Add a location dropdown and ask where the vehicle is now. Conditional paths can show the selected branch’s categories, instructions, and availability questions.
Replace incomplete service messages.
