Service History Insight helps you quickly understand whether a current issue has happened before, and whether there is a recurring pattern in your past work orders.
It reviews your recent structured service history and summarizes relevant findings directly inside the work order screen.
This feature does not replace technician diagnosis. It provides context from previous jobs so your team can make better-informed decisions.
How It Works
When you enter a description in a work order, Service History Insight:
Looks at recent relevant work orders.
Filters by:
Matching asset (if used)
Keyword similarity in the description
Topic/subtype
Prioritizes the most recent relevant entries.
Identifies:
Recurring issues
Previously documented root causes
Relevant past recommendations
It ignores unrelated equipment and routine noise where possible.
The goal is to surface patterns — not to generate assumptions.
What It Requires
For the feature to activate and provide reliable insight:
At least 3 previous work orders must exist.
The current description must contain at least 30 characters.
The more detailed the description, the better the result.
Short descriptions such as:
"Freezer issue"
will not provide meaningful context.
More helpful descriptions:
"Evaporator fan motor keeps turning off intermittently during operation"
produce significantly better analysis.
The system works best when technicians document:
What failed
Observed symptoms
What was repaired or replaced
Whether the issue was fully resolved
Why Detailed Descriptions Matter
Service History Insight relies on structured history and written technician notes.
The more specific your team is about:
Parts replaced
Observed causes
Repeated conditions
Safety concerns
Unresolved issues
the more accurate and helpful the insights will be.
If descriptions are vague, the system cannot detect meaningful patterns.
Strongly Recommended: Use Assets
Using the Assets feature significantly improves accuracy.
When assets are assigned:
History is grouped per equipment unit.
Patterns are not mixed across different machines.
Replacement history stays tied to the correct unit.
Recurring failures are easier to detect.
Without assets, the system relies only on text similarity, which may reduce precision — especially for companies managing many similar devices.
For best results:
Create assets for each maintained unit.
Attach assets to every relevant work order.
Keep asset naming consistent.
This keeps service history structured and reliable.
Example Scenario
If a freezer repeatedly shows:
Ice buildup
Temperature instability
Defrost cycle issues
Service History Insight will highlight those recurring patterns from previous work orders so your team can determine whether the problem is new or ongoing.
If no recurring issues are found, it will indicate that no recent pattern exists.
What It Does Not Do
It does not diagnose the equipment.
It does not replace technician judgment.
It does not invent issues not documented in your history.
It only summarizes what has already been recorded.
Best Practices for Maximum Value
Write clear and specific descriptions.
Always document the root cause when identified.
Mark issues as resolved when applicable.
Use Assets consistently.
Avoid one-line vague notes.
Over time, the quality of your documentation directly improves the quality of insights.
Beta Notice
Service History Insight is currently in Beta.
It is designed to assist — not replace — your team’s professional expertise.
We welcome feedback as we continue improving accuracy and filtering.