Halo
TeamViewer

Halo + TeamViewer Integration

Remote in from the ticket.
No code hunting, no delay.

Halo's native TeamViewer integration stores remote access codes against client sites and individual assets — so engineers can connect in seconds, straight from the ticket or asset record. No tool switching. No asking users for their ID. Included in every Halo licence, at no extra cost.

Talk to us about the integration See implementation plans
✓ Site-level remote codes ✓ Asset-level remote codes ✓ One click from the ticket ✓ Instant engineer access ✓ Native — included in every licence

Two ways to use it

Remote access at site level and asset level.

The integration works in two distinct modes — store codes against a client site for broad remote support, or against individual assets for direct device access. Use one, or both.

Client / Site level

Support clients remotely from the ticket

Store a TeamViewer code against each client site in Halo. When an agent opens a ticket, the remote access code is right there in the site details pane — one click to connect. No back-and-forth asking the client for their ID. No searching a spreadsheet. Just immediate access.

✓ TeamViewer code stored against the site record in Halo
✓ Instantly accessible from the ticket details pane via the Site link
✓ Remote into the client environment without leaving the ticket
✓ Each site has its own code — works cleanly across all clients

Best for

IT teams and MSPs providing remote support to clients or end users.

Asset level

Connect to a specific device, instantly

Activate the TeamViewer field on your Asset Types and link it to the Asset Details screen. Each asset — laptop, server, workstation, kiosk — holds its own TeamViewer code. When something breaks, the engineer connects straight to that device from the asset record. No looking up IDs. No waiting for the user to find theirs.

✓ TeamViewer code stored against each individual asset record
✓ Works with any asset type — laptops, servers, workstations, kiosks
✓ Direct access to the faulty device from the asset record or linked ticket
✓ Eliminates the "what's your TeamViewer ID?" back-and-forth entirely

Best for

Engineers supporting a managed device estate with named, identifiable assets.

What you get

Everything the integration delivers.

The full feature set — active from day one, included in your Halo licence, no extra configuration required beyond initial setup.

Site-level remote codes
Store a TeamViewer code against each client or site. Accessible from the ticket details pane the moment an agent clicks the Site — no tab switching, no asking the client.
Asset-level remote codes
Save a TeamViewer code against individual assets. Engineers connect directly to the specific device — laptop, server, or workstation — straight from the asset record.
One click from the ticket
The remote code is visible on the ticket details pane the moment a ticket is opened. Access is immediate — no tool switching, no external lookup required.
Asset Details screen integration
The TeamViewer field connects directly to the Asset Details screen. Engineers see the remote code alongside all other asset information — in one place, in context.
Fast, secure remote connections
TeamViewer's connection technology is unchanged — encrypted, reliable, fast. Halo surfaces the code where your engineers need it. The connection itself is still TeamViewer's.
Any asset type supported
Activate the TeamViewer field on any Asset Type in Halo — desktops, laptops, servers, kiosks, or custom types specific to your environment.
Multi-client ready
Each client site holds its own code. MSPs supporting dozens of clients have every remote access code organised and accessible — no separate reference document needed.
First-party — no middleware
The integration is built natively into Halo. No third-party connector, no API wrapper, no additional subscription. It ships as part of the platform.
No extra licence cost
The TeamViewer integration is included in every Halo licence. No add-on, no activation fee. Configuration is a scoped professional services engagement with Allied ESM.

Getting connected

How the integration is set up

Configured entirely within Halo — no external software required.

1

Enable the TeamViewer integration in Halo

In Halo, go to Configuration → Integrations and enable the TeamViewer module. It ships with every licence — no separate download or installation required.

2

Add TeamViewer codes to your site records

Navigate to each client or site record in Halo and enter the corresponding TeamViewer code. The code then appears in the ticket details pane whenever an agent opens a ticket for that site.

3

Activate the TeamViewer field on your Asset Types

In Halo's Asset Type configuration, activate the built-in TeamViewer code field. This makes the field available on every asset of that type — ready to accept a remote access code per device.

4

Connect the field to the Asset Details screen

Link the TeamViewer code field to the Asset Details screen so it surfaces alongside all other asset information. Engineers see it immediately when they open any asset record.

5

Populate codes and go live

Enter TeamViewer codes against your assets and sites. From that point, every engineer opening a ticket or asset record has the remote access code immediately to hand — no searching, no asking, no delay.

Allied ESM can scope and configure this for you

If your team uses TeamViewer, Allied ESM can scope and configure the integration — handling the setup for site records and asset types. If you're already live on Halo without the integration, we can set it up as a standalone engagement.

Real-world uses

Three ways this integration delivers.

The most common reasons IT teams and MSPs configure the Halo + TeamViewer integration.

01

MSP support desk: remote in without asking

A client calls your MSP helpdesk. Your agent opens the ticket, sees the site's TeamViewer code in the details pane, and is connected to the client environment in under a minute. No "what's your TeamViewer ID?" No hold time while they look it up.

Ticket opened → Code visible → Connected
02

IT team: faulty asset, instant access

A user logs a ticket — their laptop won't connect to the VPN. The engineer opens the asset record, sees the TeamViewer code saved against that specific device, and remotes straight onto it. Diagnosis begins immediately. No chasing the user for IDs.

Asset opened → Code saved → Remote on
03

Multi-site org: one code per location

Your organisation has sites in five locations. Each site record in Halo holds its own TeamViewer code. When a ticket comes in from any location, support can reach that environment without maintaining a separate spreadsheet or calling someone to ask for the ID.

Site identified → Code in Halo → Remote in

Common questions

Frequently asked questions

Is the TeamViewer integration included in the cost of Halo?
Yes. The TeamViewer integration is a native, first-party Halo feature — included in every Halo licence at no additional cost. There is no middleware, no third-party connector, and no extra subscription required. Configuration is a separate professional services engagement — get in touch with Allied ESM to scope it.
Do we need a TeamViewer subscription to use this?
You need an existing TeamViewer setup and the relevant TeamViewer IDs or access codes for your sites and assets. Halo stores and surfaces those codes — it does not replace your TeamViewer account. The actual remote connection still goes through TeamViewer's platform.
Can we use site-level and asset-level codes at the same time?
Yes. You can configure both simultaneously. Some teams use site-level codes for broad client support and asset-level codes for device-specific engineering work. Both operate independently and can be configured to suit your team's workflow.
Does the integration work with HaloITSM and HaloPSA?
Yes. The TeamViewer integration is available across HaloITSM and HaloPSA. The site-level and asset-level code features work the same way regardless of which Halo product you are running.
When should we set up the TeamViewer integration during a Halo implementation?
Allied ESM can scope and configure the integration as part of a Halo implementation engagement so it is live from day one. If you're already live on Halo without it, we can scope it as a standalone piece of work. Get in touch to discuss your requirements.

Ready to connect Halo and TeamViewer?

Allied ESM can scope and configure the Halo + TeamViewer integration — whether you're planning a new implementation or adding it to an existing Halo environment.

Talk to us See implementation plans