How should a field-service app connect onsite technicians with remote experts?
Remote visual assistance is valuable when an onsite person can see and safely perform the work, but a phone call or a sequence of photographs cannot describe the issue accurately and the right expert cannot arrive quickly. The first release should not be a detached video-call button or an ambitious AR programme. It should connect the work order, expert routing, onsite consent, live and paused-image annotation, poor-network fallback, evidence, disposition and escalation into one service journey.
The remote expert advises; the onsite person still confirms the asset, working conditions and every action. High-voltage work, live machinery, confined spaces and tasks restricted to qualified personnel do not become safe merely because a camera is connected. If the conditions cannot be verified, the workflow must stop remote action and arrange qualified onsite support.
Remote assistance is one treatment path within an equipment-service lifecycle; it does not replace alarms, work orders, parts or repair outcomes. Review the scope alongside How should the first phase of an equipment and IoT project close the alert-to-repair loop?. If technicians also need hands-free data capture, assess which field-service tasks are suitable for voice AI as a separate product decision.
Choose tasks that visual assistance can actually improve
A good first-release task has five characteristics:
- The problem is visible. A nameplate, alarm, connector, component position, wear pattern or sequence can be shown through a camera.
- The remote expert holds scarce context. They can combine the asset model, revision, service history and live view to narrow the issue.
- A capable person is onsite. That person has the required authority, qualification, tools and protective conditions, and can refuse or stop an instruction.
- The action can be bounded. Preconditions, confirmation points and stop conditions are explicit; the expert does not silently take control of the equipment.
- Failure has an exit. The case can move to an onsite visit, parts order, depot repair, measurement or another specialist rather than extending the call indefinitely.
Suitable pilots include reading alarms and labels, confirming component location, reviewing a low-risk inspection, checking a replacement part and improving the diagnosis before a visit. A task is a poor fit when the critical area cannot be seen reliably, no qualified onsite person is present, hazardous energy is involved or a missing instrument prevents a defensible conclusion.
TeamViewer's Mitsubishi Electric customer story describes an industrial-automation support team using shared video and augmented annotations and incorporating the capability into tiered support services. It directly demonstrates a viable use case. It is also a vendor case study, so its commercial claims should not be converted into a universal business case.
Start the session from a work order
A temporary meeting link gives the expert very little context and leaves the next colleague with very little evidence. A more complete journey should:
- begin from an asset, service entitlement or work order;
- carry the customer, site, serial number, model, revision, alarm, history and existing photographs into the request;
- route by product, skill, language, shift and service level, while recording queue and response times;
- ask the onsite participant to confirm identity, camera scope, recording choice and operational boundary;
- provide live video, a paused frame and annotations, with explicit confirmation before each critical action;
- close as resolved, observe, parts required, onsite visit or specialist escalation; and
- write a structured conclusion, authorised evidence and accountable next step back to the work order.
The PTC BID Group case contrasts repeated phone, text and photograph exchanges with real-time visual collaboration and annotation. It also describes a local technician consulting a remote specialist. The case supports the product scenario, but its performance claims belong to that customer and are not acceptance targets for a new implementation.
Scope the first release around service work
Work-order context and an expert queue
The request should be attached to a real case and asset rather than a standalone contacts screen. The expert needs the service scope, asset identity, reported problem, onsite role, previous checks and relevant manuals. If nobody is immediately available, the user needs a queue state, callback path and escalation route rather than a list of experts to call repeatedly.
Consent and privacy at the worksite
Before a session begins, explain which camera, microphone, location and attachments are shared; whether screenshots or recordings are allowed; and where retained evidence will be stored. The onsite user should be able to switch cameras, disable video, withdraw recording consent and end the session. People, production information, drawings and third-party equipment may enter the frame accidentally, so recording should be purposeful rather than automatic.
Visual tools that survive real conditions
The practical baseline is usually live audio and video, torch control, freeze frame, screenshots, arrows or freehand annotation, image and document exchange, and a visible connection state. Annotation on a paused image can be more reliable on ordinary phones and constrained networks than an elaborate 3D overlay. Consider headsets or spatially anchored AR only after a real pilot proves that technicians must keep both hands free or that the annotation must remain attached to a physical location.
Degraded-network and interruption recovery
Plants, basements and equipment rooms are rarely test labs. Acceptance should cover reduced video quality, audio-first mode, freeze-frame fallback, reconnection, deferred image upload and session recovery. If the call cannot continue, the work order should retain completed checks and the next action rather than returning to an empty state.
A structured outcome, not a video archive
Useful evidence normally includes participants, asset, time, observations, confirmed actions, authorised images, expert conclusion, risk notice, resolution status, required parts and the next owner. Full recording should not be the default. If recording serves training, quality or dispute review, define its purpose, access, retention and deletion separately.
Keep visual guidance separate from remote control
Seeing and advising is not the same as logging into a controller, PC or customer network. A video session in a field-service app should not inherit device-control privileges. Where remote access is genuinely required, use separate authorisation, least privilege, strong identity, managed access points, session termination and audit evidence. The customer should know who is controlling what, when access begins, what changes were made and when it ends.
CISA's Guide to Securing Remote Access Software notes that remote-access tools are operationally useful but are also abused by threat actors, and recommends identifying authorised tools, monitoring their use and strengthening access controls. It is security guidance rather than a video-service specification. Its relevant boundary is clear: a support call must not become an ungoverned path into customer systems.
Accept complete service scenarios, not picture quality alone
Pilot one product family, one support group and three to five recurring problems. Each scenario should prove the complete outcome:
| Acceptance area | Evidence of success |
|---|---|
| Identity and scope | Correct customer, asset, entitlement and work order; unauthorised users cannot open evidence |
| Expert routing | Correct skill queue, with defined no-answer, transfer and escalation outcomes |
| Onsite consent | Separate, understandable choices for camera, screenshots, recording and retention |
| Visual collaboration | The label, alarm or component is readable; freeze frame, annotation and confirmation work |
| Degraded network | Lower quality, audio first, still-image fallback, reconnection and safe exit work |
| Safety boundary | Hazardous or unqualified actions are stopped and escalated; a video call is not treated as a permit to work |
| Work-order closure | Conclusion, evidence, parts, visit or observation status and next owner are written back correctly |
Track first-contact resolution, escalation to a visit, waiting and session duration, repeat contact, misrouting, disconnections and the reasons onsite staff stop a session. Do not promise a generic improvement percentage. Compare the pilot against the organisation's own phone-and-photo baseline before expanding assets, regions or expert groups.
PTC's Rockwell Automation case describes an onsite engineer using a phone to connect with specialists and annotated guidance for a defined equipment task, followed by broader training and deployment. It supports a task-led pilot and service-process approach, not a universal return-on-investment claim.
Common failure modes
- Delivering a video call instead of a service workflow. Context, decisions and ownership remain trapped with individual experts.
- Buying headsets before validating the task. Hardware, training and site-management cost arrive before evidence of regular use.
- Recording every session by default. Sensitive worksite material accumulates without a clear purpose or retention rule.
- Directing hazardous work verbally. Video does not replace qualifications, permits, isolation checks or the onsite person's stop authority.
- Treating assistance as remote control. Customer authorisation, cyber risk and operational responsibility become unclear.
- Counting connections instead of outcomes. The team cannot tell whether the issue was solved, repeated, escalated or closed correctly.
Wavesteam can integrate remote assistance into a custom equipment-service app, mini program or support portal and connect it to existing work orders, assets and knowledge. The implementation should begin with one verifiable service journey. AR, headsets, AI summaries and deeper device integration belong in later releases only when field evidence justifies them.
Sources
- TeamViewer: Mitsubishi Electric customer success story and its case-study PDF, covering industrial automation support, shared video, annotations and service response; accessed 13 October 2026. Vendor customer evidence, not a universal performance promise.
- PTC: BID Group streamlines service with Vuforia Chalk, covering visual collaboration between local technicians and remote specialists; accessed 13 October 2026. Vendor customer evidence.
- PTC: Rockwell Automation collaborative augmented reality, covering phone-based expert guidance, annotations, a defined task and training; accessed 13 October 2026. Vendor customer evidence.
- CISA: Guide to Securing Remote Access Software, covering authorised tools, monitoring, access controls and misuse risk; published 6 June 2023 and accessed 13 October 2026.