Service connects telemetry, dispatch decisions, territory, SLA, technician work and material. Review configuration across the complete ticket lifecycle.
Before you begin
- First confirm the correct company and location.
- Prepare a real operating scenario for validation.
- Confirm permission for the intended change, not only read access.
One fault, many signals
Repeated telemetry increases occurrences inside one incident. The deduplication window prevents a new ticket on every poll.
A genuine recurrence
The recurring-fault warning counts separate incidents with the same fingerprint in the configured period — typically when a problem returns after repair.
How to respond
Review earlier service history in Printer 360, verify consumed material and consider deeper diagnosis or device replacement.
Recommended practice
- Test changes on one controlled case first.
- Add a clear audit note to important decisions.
- After saving, verify the result from the operating role’s perspective.
Common pitfalls
- Bulk changes without testing can affect many devices or tickets.
- Overly broad access hides a problem but does not create a sound process.
- An unverified change may behave differently in downstream workflow.
How to verify the result
The result should be one clear flow: the right signal creates one actionable case with correct SLA and an eligible technician.
✓
Continuously updated for the current Printexus release.
Still need help? Contact support.