How to Link Assets to Tickets in Freshservice
What Will This Guide Cover?
Before walking through the linking process itself, here is a quick summary of what this article covers:
- Why connecting assets to tickets matters for faster resolution and better reporting
- How Freshservice ITSM Software relates to linking assets and tickets together
- How to manually associate an asset with a ticket from the ticket view
- How Asset Impact automatically updates ticket priority based on linked assets
- How to automate asset association and link assets through the API
- Answers to frequently asked questions about linking assets to tickets in Freshservice
How Does Freshservice Relate to Linking Assets and Tickets?
Freshservice ITSM Software includes a built-in Assets tab directly within the ticket view, letting agents search for and connect a Configuration Item, or CI, to any ticket in just a few clicks. Because this connection lives natively inside the ticket interface, technicians do not need a separate tool to cross-reference which hardware or software relates to a reported issue; instead, Freshservice keeps the ticket and the affected asset linked in one place.
This matters directly for the topic of this article because linking assets to tickets does more than add context to a support request. Freshservice reveals its value here through its Asset Impact feature, which automatically re-evaluates a ticket’s impact and priority once the system associates a linked asset, and through API support that lets larger organizations automate this linking process at scale rather than relying on manual entry for every ticket.
Why Does Linking Assets to Tickets Matter in the First Place?
Before covering the specific steps, it helps to understand why this connection improves service management rather than simply adding an extra field to fill in.
How Does Asset Linking Speed Up Ticket Resolution?
When agents link a ticket to a specific asset, they can immediately see that device’s history, including past incidents, its current location, and its assigned user. This visibility helps agents diagnose recurring problems faster, since they can spot patterns tied to a specific device rather than treating every ticket as an isolated issue.
This matters especially for hardware nearing the end of its useful life, since repeated tickets tied to the same laptop or server often signal a device that needs replacement rather than repeated troubleshooting. Without a consistent link between tickets and assets, this kind of pattern can go unnoticed for months, with agents repeatedly addressing symptoms instead of recommending a permanent fix.
Why Does Asset Data Improve Reporting and Change Planning?
Linked assets also feed into broader reporting, letting IT teams identify which hardware or software generates the most support tickets over time. This data supports smarter hardware replacement decisions and gives change managers a clearer picture of which systems carry the highest risk before a planned change goes live.
Beyond replacement planning, this reporting also helps justify IT budget requests with concrete data rather than general impressions. A report showing that a specific server has been linked to a disproportionate share of incident tickets over the past quarter makes a far stronger case for prioritized investment than an anecdotal sense that “that system causes problems.”
How Do You Manually Link an Asset to a Ticket in Freshservice?
For most day-to-day support tickets, manually associating an asset takes only a few clicks directly from the ticket view.
Where Do You Find the Assets Option on a Ticket?
When viewing any ticket, look for an Assets tab or button located under the ticket description. Clicking this option opens a panel where you can search for the specific asset involved in the issue rather than scrolling through the entire inventory.
How Do You Search for and Attach the Correct Asset?
Once the Assets panel opens, click Associate Asset, then either select the asset’s category from a drop-down menu or search directly for its name. This flexibility helps when an agent knows the type of device involved, such as a laptop, but not its exact display name, since narrowing by category first often speeds up finding the right record.
Can You Link Assets to Requesters as Well as Tickets?
Yes. Each asset in Freshservice supports a “Used By” field found on the asset’s own record, which shows which user is currently assigned to that device. This connection works alongside ticket-level associations, so agents can view an asset from either direction: starting from the ticket to find the asset, or starting from the user’s profile to see every asset currently assigned to them.
Table: Ways to Associate Assets with Tickets in Freshservice
The table below summarizes the different methods available for linking assets to tickets, depending on the situation.
| Method | Best For | How It Works |
|---|---|---|
| Manual association (ticket view) | Individual, one-off tickets | Agent searches for and selects the asset directly within the ticket’s Assets tab |
| Asset Impact | Incident and alert tickets | Automatically updates ticket impact and priority based on the linked asset’s own impact level |
| Workflow Automator | Recurring or rule-based scenarios | Automates asset association based on defined trigger conditions |
| API (associate_ci or assets key) | Bulk operations or custom integrations | Developers link assets programmatically through PUT or POST requests |
| Project task associations | Project-related tickets, problems, and changes | Links a ticket, problem, change, or asset directly within a project task’s Associations tab |
Choosing the right method depends on volume and consistency: manual association works fine for occasional tickets, while automation and API-based linking make more sense for organizations handling a high ticket volume tied to specific asset categories.
How Does Asset Impact Automatically Adjust Ticket Priority?
Beyond simply recording which asset relates to a ticket, Freshservice uses that connection to influence how urgently a ticket gets treated.
What Does the Asset Impact Feature Actually Do?
The Asset Impact feature automatically re-evaluates the impact of an incident ticket whenever an asset gets associated with it. Specifically, Freshservice compares the ticket’s existing impact field against the impact level of the newly linked asset, then updates the ticket to reflect whichever value is higher. For example, if a ticket initially shows “medium” impact and a “high” impact asset gets linked to it, the ticket’s impact field updates to “high” automatically.
How Do You Enable Asset Impact for Your Tickets?
To turn this feature on, navigate to Admin, then Service Management, then Service Desk Settings, then Priority Matrix. From there, scroll down to the Asset Impact section and enable the toggle labeled Pass Associated Asset Impact to Ticket. Note that this feature is only available for incident and alert tickets, not for service requests or other ticket types.
How Does Asset Impact Interact with the Priority Matrix?
When the Priority Matrix is enabled alongside Asset Impact, associating a new asset can also shift the ticket’s overall priority, not just its impact field. For instance, if a ticket’s urgency is “medium” and its impact is “low,” the priority matrix might initially calculate “low” priority. Once a “medium” impact asset gets linked, the impact field rises accordingly, which can then raise the calculated priority as well, ensuring tickets tied to more critical assets get appropriate attention faster.
How Can You Automate Asset Association for Larger Volumes?
Manually linking assets works well for individual tickets, but organizations handling high ticket volumes often look for ways to reduce this repetitive task.
Can Workflow Automator Handle Asset Association?
Yes, though this typically requires a Workflow Automator rule rather than a fully automatic default behavior, since Freshservice does not automatically guess which asset belongs to which ticket in most standard cases. Administrators can configure automator rules based on trigger conditions, such as specific keywords in a ticket description, to associate a relevant asset automatically.
What Precautions Should You Take Before Automating Asset Association?
Broad automation rules carry a real risk of misattributing assets to tickets, which can pollute reporting data over time. For example, an automation that assumes a requester’s assigned laptop is always the “problem asset” could incorrectly link that device to a ticket actually caused by a server outage or a shared application issue. Building in specific trigger conditions, rather than applying a blanket rule to every ticket from a given requester, helps avoid this kind of data quality problem.
A safer approach often involves layering conditions, such as checking whether the ticket description contains phrases like “my computer” or “my laptop” before triggering an automatic association with the requester’s assigned device. This extra filtering step reduces false positives while still capturing the majority of straightforward, single-device tickets that genuinely benefit from automatic linking.
How Do Developers Link Assets Through the API?
For custom integrations, Freshservice’s API supports linking assets to tickets using an “assets” key containing a comma-separated list of asset display IDs in PUT or POST requests. Developers should note that including the “assets” key removes any existing assets not listed in the request from the ticket, so each call must include every asset that should remain associated. Freshservice is phasing out the older “associate_ci” format in favor of this newer “assets” key structure, so new integrations should use the current method.
Conclusion
Linking assets to tickets in Freshservice creates a direct connection between a reported issue and the specific hardware or software involved, whether through a quick manual association from the ticket’s Assets tab or through automated rules and API calls for higher-volume scenarios. This connection speeds up diagnosis, supports better reporting on which assets generate the most support activity, and, through the Asset Impact feature, even helps ensure tickets tied to critical assets receive appropriately urgent priority.
Freshservice ITSM Software brings these capabilities together in a way that keeps ticket and asset data connected without requiring a separate tracking system on the side. Whether an organization relies on manual association for occasional tickets or builds automated workflows and API integrations for scale, the underlying goal stays the same: giving agents immediate context about the assets behind every ticket they handle.
Frequently Asked Questions
Yes. Freshservice allows users to associate multiple assets with a single ticket, which is useful for incidents affecting several devices at once, such as a network outage impacting multiple workstations connected to the same switch.
Only when the user enables the Asset Impact feature and the ticket type is incident or alert. When enabled, Freshservice compares the ticket’s existing impact against the linked asset’s impact level and updates the ticket to the higher value, which can then affect priority if the Priority Matrix is also active.
Yes, though it usually requires setting up a Workflow Automator rule with specific trigger conditions, since Freshservice does not automatically determine which asset caused a given issue on its own. Organizations can also use the API to associate assets programmatically for bulk operations or custom integrations.
