Remote Support for Your Customers
How software vendors, equipment makers and IT service providers replace site visits with remote support — connection model, branding, audit trail and integration.
Updated
Software vendors, equipment makers and IT service providers still send engineers to customer sites. Travel cost is the obvious price; the heavier one is that the customer’s business is stopped while they wait for you to arrive.
Remote support compresses most of those visits into a few minutes. Doing it properly means settling three things first: the connection model, how it is branded, and what you can show afterwards.
1. Connection model: attended is the default for customers
Supporting a customer and managing your own fleet are different problems.
| Customer support | Internal operations | |
|---|---|---|
| Default mode | Request-based (customer clicks accept) | Unattended |
| Why | The customer should see and approve every session | Nobody is at the machine anyway |
Request-based should be the default in customer work. Every session is approved by the customer, which is both respectful and your own protection — if a session is ever disputed, “the customer approved each one” is a position that holds.
Only consider unattended access where the customer has explicitly authorised it and the device is one you shipped and operate — a kiosk, an appliance, an industrial terminal. In that case it becomes a privilege to manage deliberately; see unattended access.
2. Branding: whose name does the customer see?
This is the part teams remember halfway through.
A customer asked to download unfamiliar software and shown an unfamiliar interface hesitates — and the “please install this remote tool” moment on a support call loses more people than most teams expect. Custom branding presents the whole flow as your own product, which costs the customer far less trust.
Custom branding is a Team and Enterprise capability; the Free and Personal plans do not include it. For anyone delivering service under their own brand, it is usually a requirement rather than a nice-to-have.
3. The audit trail is for the customer, not for you
Internal operations log sessions mostly for compliance. In customer support, you log them so you can account to the customer.
- When a customer asks what was done during that session, you need an answer
- When a fault is disputed, you need to show the scope of what was touched
- In regulated industries the customer’s own compliance will ask you for records
WorksLink records connection logs and file transfer activity, and can store a whole session as video, so an operation can be reviewed rather than reconstructed from memory.
⚠️ Those audit capabilities are Team and Enterprise only. The Free and Personal plans have the encryption but not the trail. If your situation requires accounting to a customer, the free plan does not cover it — see security and auditing.
4. At scale: integration
Once volume grows, switching between your ticketing system and the remote tool becomes its own cost.
Team and Enterprise plans offer two kinds of integration: remote control integration (start a session from inside your own system, so an engineer launches it from the ticket) and recording and connection log integration (audit data flows into your own ticketing or compliance system, so a finished session files itself against the right ticket).
Together these are what turn remote support from a tool into part of the process.
A rollout order that works
- Start with attended support only — no unattended access anywhere. It pays off immediately and creates no long-lived privileges to manage
- Confirm the audit trail is on before widening access; logging has no retroactive mode
- Add custom branding early if you need it — it affects conversion on the customer’s side, and retrofitting costs more the later you leave it
- Integrate last, once volume genuinely makes the context switching hurt
Feature-by-feature differences are on the pricing page; deployment questions are covered in enterprise deployment.
One example already running
Lenovo uses the WorksLink remote assistance platform to support employees and partners worldwide, with more than 20,000 terminal devices connected, relying on private network deployment and compliance guarantees. More in customer cases.