Describe your HVAC call workflow. Makeform turns it into an editable form for the site, equipment, symptoms, findings, work, parts, labor, status, and next action.
Send service records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a workflow, adjust it, or send the example prompt into the builder.
Audience
Residential technicians documenting diagnostics and repairs
Format
Mobile service record with equipment and work details
Prompt size
258 chars
Example form structure
Mobile service record with equipment and work details
Customer, address, and appointment
Equipment, model, and serial number
Reported symptom and technician diagnosis
Readings, parts, and labor
Completion photos and acknowledgment
Suggested routing tags
Scheduled
Awaiting parts
Completed
Keep model and serial numbers in separate fields so service history is searchable.
Step 1
Intake
customer, site, equipment, and symptom
Step 2
Diagnose
observations, readings, and cause
Step 3
Service
work performed, parts, and labor
Step 4
Close
status, acknowledgment, and follow-up
A complete call record
Replace scattered texts and tickets with one record from reported problem to next action.
Record the symptom, equipment, timing, access, and appointment preference before dispatch.
Separate observations, readings, diagnosis, and completed work instead of burying them in one note.
Close each visit with a clear status, follow-up owner, and target date.
Built around real HVAC calls
Change labels, equipment lists, required fields, and routing to match your operation.
Complaint, equipment, diagnosis, repair, parts, status, and recommendations in a mobile record.
Property, asset, access, readings, downtime, purchase order, and additional-work approval.
Repeatable checks, measured values, exceptions, completed adjustments, and next visit.
Symptoms, urgency indicators, photos, access, contact preference, and appointment windows.
Build the workflow
Generate the intake and closeout structure, then refine it for field use.
Define who submits, what dispatch needs, and what technicians record at closeout.
Use dropdowns for status, numbers for readings, checks for tasks, notes for findings, and uploads for equipment photos.
Branch by call type and status so technicians see only relevant questions.
Connect submissions to the service inbox, Sheets, Slack, or Zapier for follow-up.
Form vs notes vs generic ticket
Make essential details easy to enter in the field and review later.
Field guide
Use these six sections from intake to closeout, with longer answers reserved for exceptions and diagnosis.
Customer and site
Capture the exact location, on-site contact, callback method, access instructions, and scheduling constraints.
Equipment identity
Separate equipment identity from notes, especially when a property has several units.
Reported issue
Keep the customer's report distinct from technician findings, including timing and operating context.
Findings and readings
Record only readings relevant to your equipment and procedure, giving reviewers a clear basis for the diagnosis.
Work, parts, and time
State what was cleaned, adjusted, repaired, or replaced. Keep part quantities and labor in structured fields.
Closeout and follow-up
State whether the system operates, what remains, who owns the next step, and what the customer was told.
Related tools
Connect service calls to work requests, inspections, maintenance records, approvals, and closeout.
Create assigned work records with scope, schedule, materials, status, and completion.
Open toolDocument service tasks, condition, readings, parts, and outcomes.
Open toolBuild inspection checks with findings, photos, readings, and actions.
Open toolGive customers or staff a clear way to report an issue, location, urgency indicators, and supporting photos.
Open toolSummarize completed maintenance, exceptions, costs, recommendations, and work still outstanding.
Open toolRoute proposed work, supporting notes, estimated scope, and approval decisions to the right reviewer.
Open toolFAQ
Practical answers for HVAC owners, dispatchers, service managers, and technicians building a more consistent call record.
It records the issue, site, equipment, findings, work, parts, time, system status, and follow-up. It can begin at customer or dispatcher intake and continue through technician closeout.
Include contacts, address, appointment, equipment identity, symptom, findings, readings, diagnosis, work, parts, labor, photos, technician, status, acknowledgment, and next action. Remove unused fields so technicians can finish it on a phone.
Yes. Use the first section for intake and later sections for field work, hiding technician questions until needed. Separate intake and closeout forms linked by work order number may fit different access rules better.
Use an asset tag or unit label with location, manufacturer, model, and serial number. For several units, repeat the equipment section or create one submission per unit under the same work order number.
Yes. Add uploads for nameplates and completed work, fields for readings, structured part entries, and a signature or acknowledgment. Require only evidence relevant to that call type.
Require a status such as completed, awaiting approval, awaiting parts, or return required. For follow-up, collect remaining work, parts, owner, priority, and target date, then route the record to the service queue.
Yes. Makeform provides unlimited free forms and responses. You can generate, edit, publish, and collect submissions; the paid tier removes the Makeform badge.
Submissions reach your Makeform inbox and can connect to Google Sheets, Slack, or Zapier. Consistent work order, asset, customer, and status fields make records easier to route and sort.
Make every service visit easier.
