From 3-Ring Binders to Agentic AI: What JLG’s Transformation Teaches Every Field Service Leader

Key Takeaways:

JLG’s AI success was a people-and-data story first, not a technology story.

• The field service knowledge brain drain is accelerating as experienced experts retire with decades of undocumented institutional knowledge
• Knowledge-Centered Service methodology is the critical prerequisite to any AI rollout; without clean, structured knowledge, AI has nothing to work with
• JLG saved 11,750 hours per year by shifting agents from “authors” of manual logs to “editors” of AI-generated drafts
• Most AI projects fail because of people problems, not technology problems; solving agent frustration before deployment is the most underrated success factor

For decades at JLG Industries, the answers to the hardest technical support questions lived in the margins of three-ring binders. Not databases. Not shared drives. Handwritten notes belonging to individuals who guarded them fiercely.

Today, JLG handles 2,000 inbound service contacts daily, and that same institutional knowledge powers Landis, their AI virtual service agent. At Field Service Next West, Travis Myers, JLG’s Director of Customer Support, and Chloe Lind from Aquant explained how they got there. What emerged was not a technology blueprint. It was a masterclass in getting the human and data fundamentals right before deploying a single AI model. It also showed why agentic AI deployment fails when the groundwork is weak. More importantly, it framed AI adoption as a long-term agentic AI transformation.

What Is the “Knowledge Brain Drain” Problem and Why Does It Keep Getting Worse?

Travis opened with a photo from his early days: thick monitors, cluttered desks, and three-ring binders at every workstation.

“A lot of knowledge resided within the extra notes in the margins of their books,” he recalled. “Their books were sacred, and you didn’t dare go into someone else’s book.”

JLG’s support team holds over 1,300 years of combined experience. That is an extraordinary asset, until every retirement takes years of undocumented expertise permanently out of circulation. New agents cannot inherit what was never written down, and junior staff spend months learning by proximity to veterans rather than from structured, accessible resources.

The knowledge-hoarding vs. knowledge-sharing dynamic is not unique to JLG. Across heavy equipment manufacturing, the aging workforce crisis is making this urgent. Every retirement is effectively a data loss event, and organizations that fail to systematically capture expert knowledge before it walks out the door are increasingly vulnerable. This is also an agentic AI workplace transformation problem because people, process, and trust have to change together. Many leaders now see that groundwork as part of agentic AI for digital transformation.

What Is Knowledge-Centered Service and Why Is It the Foundation of Any AI Rollout?

Before deploying any AI tool, JLG invested in the Knowledge-Centered Service methodology, where knowledge is captured as a natural byproduct of every support interaction rather than as a separate documentation task.

The concept is simple: each time an agent solves a problem, the solution is stored in a reusable, structured format. It is not future questions that give rise to knowledge, but real ones. This renders it practical, grounded, and instantly useful.

For JLG, adopting KCS meant a genuine cultural shift. Agents had to stop treating documentation as administrative overhead and start seeing it as core to their role. That change is harder than it sounds under high-volume pressure, but it is what made everything that followed possible. That kind of shift sits at the heart of agentic AI workplace transformation.

Knowledge governance for AI starts with KCS, not with a model selection meeting. That foundation is essential for agentic AI service management. It is also what makes agentic AI for field service practical instead of experimental.

How Does AI Case Documentation Actually Save Time at Scale?

With a clean knowledge foundation in place, JLG targeted the most time-consuming and least valuable part of an agent’s day: case documentation.

AI case documentation automation shifted agents from writing notes manually to reviewing and refining AI-generated drafts, which Travis called moving from “authors” to “editors.” The outcome was 11,750 hours saved annually, equivalent to five full-time support agents, without any additional employees. That kind of gain is one of the clearest proofs of value for the agentic AI field service. It also creates cleaner records for future agentic AI api deployment.

That regained capacity was directly channelled into complex troubleshooting, the high-value diagnostic work that actually needs human expertise.

What Is Agentic AI and How Is It Different From a Chatbot?

JLG’s virtual assistant, Landis, is often called a chatbot. Travis and Chloe were clear: it is not. It is already a practical example of agentic AI field service in action.

A chatbot is reactive and scripted; it matches keywords to pre-written responses and fails when a question falls outside its scope. Agentic AI for field service customer support retrieves information dynamically, reasons across multiple steps, takes action within defined boundaries, and knows when it has reached the edge of its competence. That is what makes agentic AI for field service different from a scripted assistant. It is also why JLG’s model feels closer to true agentic AI service management.

Landis is built to autonomously resolve up to 20% of live service engagements, grounded in high-fidelity service manuals and real historical case data. When it cannot reach a high-confidence answer, it executes a graceful AI-to-human handoff, passing full conversation context to a live agent so the customer never has to repeat themselves. AI handles the scale. Humans handle the empathy. That boundary, clearly defined and consistently respected, is what makes the model work.

Why Do Most Enterprise AI Projects Fail — and What Did JLG Do Differently?

Close to 95% of AI pilots never reach production. JLG is operational and expanding. Five factors made the difference. JLG also shows that successful agentic AI deployment depends on operational discipline. Its rollout is better understood as an enterprise agentic AI transformation than as a single pilot.

• Solve Real-World Problems: Don’t start with a solution, looking for a problem. Identify agent frustration first.
• Data Support: Ensure you have the historical data and transcriptions to fuel the models.
• The ADKAR Methodology: Use a structured change management for AI approach (Awareness, Desire, Knowledge, Ability, and Reinforcement).
• Dual Accountability: Both IT (led by stakeholders like John Tocato) and Business must own the success criteria.
• Context is King: Use voice-to-CRM automation to ensure your system data is consistent and actionable.

That is why agentic AI API deployment across service systems has to be carefully planned. It is also a reminder that AI programs live inside a wider agentic AI for digital transformation effort.

What Does Vision AI Mean for the Next Phase of Field Service?

Travis closed with a glimpse of where JLG is heading. Instead of calling support to describe a broken hydraulic valve, a technician simply opens their camera. Vision AI field technician real-time diagnosis identifies the fault from the live feed, cross-references service history, and delivers step-by-step repair guidance, no voice call required.

It is the natural next step from everything JLG has built. But reaching it requires the same prerequisites that made Landis possible: clean, structured data, a functioning agentic AI layer, and mobile-first tooling that puts intelligence directly in the technician’s hands. That is one reason agentic AI use cases for field service in telecommunications are getting attention, too.

Conclusion

JLG’s journey from three-ring binders to Landis is built on a simple sequence: capture knowledge consistently, automate the transactional, then elevate the relational. AI works best when it removes administrative burden, freeing human experts to do what only they can do.

The foundation of JLG’s success is consistent, high-quality data capture at every service interaction. See how Praxedo’s mobile field service app gives your technicians the tools to fuel your own AI journey. Request a demo today.

FAQs:

1. What is the knowledge brain drain problem in field service?

It is the loss of institutional expertise when experienced staff retire, taking undocumented knowledge that was never captured in any accessible system.

2. What is Knowledge-Centered Service methodology?

An organized method in which knowledge is documented as a byproduct of solving actual customer interactions, instead of being developed independently as a documentation project.

3. What is agentic AI, and how is it different from a chatbot?

A chatbot is scripted; agentic AI is dynamically retrieved, reasons step by step, acts within its limits, and intelligently escalates when it reaches its confidence threshold.

4. How does AI case documentation reduce agent workload?

By automatically generating case summaries after each interaction, agents review and refine drafts rather than writing from scratch — significantly reducing after-call admin time.

5. Why do most enterprise AI projects fail?

Primarily because of the human side, ignoring agent frustration, skipping structured change management, and deploying AI on top of inconsistent data.

6. What is Vision AI in field service?

It allows technicians to open their camera on-site and receive real-time fault diagnosis based on what the AI sees, removing the need to verbally describe complex technical problems to remote support.