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.
Technician selection
Recommendations consider territory, workload, availability and required material. The system rejects technicians without access to the device or territory.
Technician workflow
A technician sees assigned jobs and may open Ticket 360 without general Service Desk access. The flow covers acceptance, travel, on-site work and resolution.
Completion and material
On completion, reserved toner or parts are consumed from technician stock. Closing without consumption releases reservations. Every action remains auditable.
Resolution and closure
The technician marks work resolved and the ticket leaves active jobs immediately. Dispatch may close or return it; otherwise it closes automatically after 24 hours. It remains in technician history for 60 days.
- 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.
- 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.
The result should be one clear flow: the right signal creates one actionable case with correct SLA and an eligible technician.
Still need help? Contact support.