Connect tickets to equipment history. Review custody, earlier faults, and repair effort before making a replacement decision.
Explore with sample data. Adapt fields, views, and workflows for your team.
Record the asset tag, name, class, current custodian, and state. Two people using the same laptop model should not have their histories combined.
Check the symptoms, attempted fixes, dates, and outcomes of linked tickets. A repeated fault after an adapter test is a different decision from a first report with no diagnosis.
Keep the work log attached to the ticket and the ticket attached to the asset. This preserves both the issue history and the effort spent investigating it.
Select the affected ticket and the same asset. Describe the failed repair attempts, proposed replacement, and estimated cost.
The assigned equipment reviewer can return the request for more detail or authorize it. The workflow checks that the proposed device matches the ticket’s asset.
Authorization is not a physical replacement. Record the procurement or handover reference and maintain custody and asset state when the actual change occurs.
Keep one authoritative equipment register. If another ITAM system owns discovery, serial numbers, or procurement records, import or integrate the needed identifiers rather than maintaining contradictory inventories.
Three unrelated requests about a laptop do not prove that it should be replaced. Read the symptoms and attempted fixes. Repeated charging failures after a known-good adapter test deserve a different response from a first-time connection question.
Include the repair result, disruption to the employee, warranty position, and proposed cost. Keep the approved decision with the affected device and ticket. When the replacement arrives, record the handover and the old device’s disposition; approval alone must not make an available device disappear from the register.
Yes. Each ticket has its own issue and handling history, while the asset record connects them through the same stable identifier. This helps a technician recognize recurring faults.
Import a cleaned equipment list with unique identifiers, then establish the ticket-to-asset relationship. Check duplicate tags, custodians, and retired equipment before treating the imported list as current.
No. This app manages recorded assets and their support relationships. Automatic discovery, endpoint monitoring, software-license reconciliation, and remote control require specialist tools or separately configured integrations.
The decision is recorded in the replacement workflow. The asset is not automatically retired or replaced, because the physical handover and authoritative inventory update still need to happen.
Keep the old asset and its history rather than reusing its tag for a different device. Update the lifecycle state and select the current device for new issues.
Start with the linked equipment and tickets, then adapt the fields and replacement review to your organization.
