Assets matter when tickets sync between Syncro and HaloPSA

When a support ticket comes in, the clock starts immediately. A technician opens it, reads the description, and then — before they can do anything useful — they start hunting. Which device is involved? What's it connected to? Where does it sit in the network? That information exists somewhere, but it doesn't always exist where the technician is looking.

This is the context switching problem. And for MSP technicians working across co-managed environments, it's a daily reality.

The gap between ticket systems

In a co-managed IT setup, your MSP might run Syncro while your client's internal team works in Halo PSA. Tickets sync between the two systems so both sides stay across what's happening — but historically, that sync has focused on ticket fields: priority, status, description, notes.

What doesn't always travel with the ticket is the asset context. The firewall. The access point. The server that the ticket is actually about.

Those assets are linked as objects in your PSA. They carry meaningful information — device names, locations, configurations — that a technician needs to understand the problem before they can start solving it. When that information stays behind in the originating system, the technician on the other end has to go looking for it. That means Alt+Tab. That means another login. That means time.

What we've added

In this week's product update, Steve walks through a new feature that addresses this directly. When tickets sync between Syncro and Halo PSA through Support Fusion, you can now include the linked asset names in the synced ticket description metadata.

It's a configuration toggle in your integration settings. Turn it on, and whenever a ticket syncs across, the asset names come with it — appended to the ticket description so they're visible immediately on the receiving end.

The example Steve uses in the video is a high-volume blocked inbound connection event. The ticket has a firewall and an access point attached as objects. Without this feature, those object references don't cross the integration boundary. The technician in Halo PSA sees the ticket, but doesn't see which devices are involved. With it, the asset names are right there in the description from the moment the ticket arrives.

Why this matters for technicians

Our mission at Support Fusion is straightforward: arm technicians with all the information they need, the first time they open a ticket. Not after a phone call. Not after logging into another system. The first time.

Every unnecessary tab switch is a small interruption. But technicians working high-volume queues don't experience these as small — they accumulate. Each context switch breaks focus, adds latency to resolution, and increases the chance that something gets missed or misunderstood.

Keeping asset context attached to the ticket removes one of those interruptions. The technician knows what they're dealing with before they've asked a single question.

Part of a bigger picture

This feature is a stepping stone. We're actively building full asset synchronisation — the ability to sync asset records themselves across platforms, not just reference their names in a description. When that's live, the asset data will travel with the ticket at a deeper level.

But the description metadata approach solves the immediate problem today, and it does so without requiring any changes to how your integration is configured beyond flipping a toggle.

If you're running a Syncro to Halo PSA integration through Support Fusion, it's worth turning on.

Watch the full update

Steve covers this feature in detail in this week's Friday product update, including a live walkthrough of how the asset names appear in the synced ticket. Watch it below.

Got questions about how this works in your integration setup? Get in touch with the team.