Field Service
HVAC, Plumbing, Electrical
THE PROMPT
“I run an HVAC company. Technicians need to track service calls, scan equipment QR codes to pull history, log work with photos, capture signatures, and auto-generate invoices.”
Lattice builds the complete system from this single prompt: 5 entities, 50+ fields, 6 automations.
Data Schema
(5 entities, 53 fields)| Field | Type | Required |
|---|---|---|
| Call ID | Auto-ID (SC-####) | |
| Customer | Relation → Customers | |
| Equipment | Relation → Equipment | — |
| Technician | Relation → Technicians | |
| Status | Select[Scheduled, En Route, On Site, Complete, Invoiced] | |
| Priority | Select[Low, Normal, High, Emergency] | |
| Issue Description | Long Text | |
| Scheduled Date | DateTime | |
| Arrival Time | DateTime | — |
| Completion Time | DateTime | — |
| Work Performed | Long Text | — |
| Parts Used | Relation → Parts | — |
| Photos | Images (multi) | — |
| Customer Signature | Signature | — |
| GPS Location | GPS | — |
| Invoice Amount | Currency | — |
| Notes | Long Text | — |
Automations
(6 rules)When Service Call status → "En Route"
When Service Call status → "On Site"
When Service Call status → "Complete"
When QR code scanned
If scheduled call not started within 1hr
When Part stock < reorder point
Available Views
Sample Workflow: Emergency AC Repair
Customer calls: AC not cooling
→ Service call created, priority: High
Dispatcher assigns Mike (HVAC certified)
→ Mike gets push notification
Mike marks "En Route"
→ Customer gets SMS with ETA
Mike arrives, scans equipment QR
→ Full service history loads, last visit was capacitor replacement
Mike completes repair, captures photos
→ Before/after documented
Customer signs on tablet
→ Invoice generated, emailed automatically