Elite Field ServiceIntelligence Engine
How a heavy-equipment service company in Michigan deployed the Intelligence Engine to capture 20 years of tacit knowledge and compress 3–4 call troubleshooting into a single query.
Heavy Equipment. Complex Problems. Decades of Knowledge.
Elite Field Service (EFS) sells, services, and repairs heavy equipment across Michigan — spider lifts, boom lifts, scissor lifts, and compact construction equipment. Their technicians handle complex troubleshooting calls from customers and field service teams every day.
Knowledge Was Walking Out the Door
EFS had three data sources that never talked to each other. Technicians would answer the same questions repeatedly because there was no way to search past conversations. When a senior tech retired, decades of tacit knowledge left with them.
Conversations = Black Box
Hundreds of support conversations per month (calls, messages). Zero transcription. Zero searchability. The only record was in the technician's memory.
Service Orders = Isolated
FullBay tracked every service order, but it had no connection to the conversations that initiated it. Context was lost.
Manuals = Buried
Service manuals for every piece of equipment existed as PDFs in file shares. Technicians couldn't quickly cross-reference a fault code with the manual.
The Retirement Problem
When senior technicians left, their 20 years of troubleshooting experience walked out with them. No handoff. No archive.
One Engine. Three Data Sources. Infinite Connections.
Creative Intelligence deployed the Intelligence Engine for EFS over 90 days. All three data sources were connected, classified, and made queryable through a chat interface and autonomous reporting.
Implicit Data
Support conversations (Zoom calls in this case) transcribed and classified every 15 minutes. Speaker diarization, entity detection, automatic topic tagging.
System of Record
FullBay API connected and synced every 15 minutes. Service orders, customer data, invoicing — all queryable alongside conversations.
Documents
Every service manual for every piece of equipment ingested and chunked. Fault codes, wiring diagrams, troubleshooting steps — all searchable.
The Magic: Cross-Reference
For the first time, EFS could ask a single question that pulled from all three sources simultaneously. A query about "fault code 1440" returned the manual entry, every historical service call mentioning that code, and the troubleshooting steps that actually worked — all in one response.
What Actually Happened
Fault Code 1440: From 3–4 Inquiries to 1 Query
3–4 inquiries → 1 queryA technician asked about fault code 1440 on a spider lift. Previously, this required 3–4 separate inquiries: check the manual, find historical service orders, ask a senior tech if they'd seen it before. With the Intelligence Engine, a single query returned: the manual entry, every past conversation with that code, the replacement parts list, and the step-by-step fix.
Zero Volts → E-Stop: Saved a Misdiagnosis
Prevented unnecessary parts orderA customer reported "zero volts" on their equipment. The first instinct was battery failure. But the Intelligence Engine cross-referenced the phrase "zero volts" with historical calls and found that in 80% of cases, it was actually an E-stop problem — not battery failure. The technician checked the E-stop first and solved it in minutes.
CMC Manufacturer Demo: They Want to Buy It
Manufacturer wants to license the systemCMC, a spider-lift manufacturer, visited EFS for a demo. They watched a technician query the Intelligence Engine about a complex fault and get a complete answer in seconds. CMC's own call center takes 3–4 calls per issue. They immediately asked how they could deploy the same system for their global support operation.
Permission-Based Access: Right Data, Right Role
One system, multiple rolesGeneral mechanics see service orders and troubleshooting steps. Sales sees replacement timelines and upsell opportunities. Executives see everything — cross-department insights, trending issues, and leading indicators. Same database, different lenses.
How the Three Buckets Mapped to EFS
Implicit Data: Conversations
Zoom Business Phone (example)
Every support conversation transcribed with speaker diarization. Ted, Jason, and the field service team's conversations automatically classified by topic: Troubleshooting, Billing, Parts, Sales, HR/Legal.
"Show me every conversation about fault code 1440 in the last 6 months"
System of Record: FullBay API
FullBay Service Management
Service orders synced every 15 minutes. Customer records, equipment serial numbers, warranty status, parts ordered, technician assignments — all linked to the calls that created them.
"Which customers have open service orders for model S31?"
Documents: Service Manuals
PDF Manuals for All Equipment
Every CMC, JLG, Genie, and Snorkel manual ingested and chunked. Fault code tables, wiring diagrams, maintenance schedules, safety procedures — all semantically searchable.
"What does fault code 1440 mean and what parts do I need?"
What They Said
"The ability to cross-reference a fault code with every historical call and the service manual — that's not something we could do before. It's like having every technician's experience available instantly."
— EFS Leadership
Ready for your own Intelligence Engine?
EFS proved the model. The Intelligence Engine is productized and extensible to any business with calls, a system of record, and documents.