How does a virtual support session work?

1. An agent starts a session and sends a one-time secure link by email or SMS.

2. The customer taps the link and grants camera or screen-share permission in their browser.

3. The live stream opens in the agent console with pointer, markup, zoom, and flashlight controls.

4. The agent captures photos, writes notes tied to each photo, and runs OCR on labels, plates, or serial numbers when needed.

5. When the call ends, notes, photos, annotations, and OCR results are packaged into a shareable report.

From link tap to live video is typically under thirty seconds, including the browser permission prompt. There is no meeting ID to type, no lobby, and no download.

A short pre-call check verifies camera, microphone, and network, and can be skipped when the customer is ready to go.

Support and screen-share invites are single-use and expire, so a session cannot be joined or hijacked after the fact. Recording requires explicit consent, and every action is written to an audit log.

If a link is forwarded after use, it simply fails to open a session.

The session pack — notes, captured frames, annotations, OCR output, and an AI-drafted summary — exports as a branded PDF and pushes to your CRM or ticketing system.

Because the notes are tied to specific photos, the write-up reads as evidence rather than as recollection.

Virtual Support Pro starts with a secure link sent by email or text. The customer opens it in their browser, and their camera or screen appears in the agent console without an app or account. The supplied starting estimate is usually under 30 seconds, not a guaranteed connection time. Link delivery, browser permissions, device compatibility, and connectivity can affect how quickly the session begins.

For support leaders explaining how virtual support works, preparation should be part of the script: confirm the issue, explain what the agent needs to see, and ask whether the customer can safely show it. For equipment support, request adequate lighting and an accessible model label. For screen-based help, ask the customer to close unrelated documents and hide notifications. Explain the session’s purpose before sending the link, especially when contacting residents, policyholders, or government service users.

A one tap video support link simplifies entry, but it does not bypass browser permission controls. W3C’s Media Capture and Streams specification describes permission requirements for camera and microphone access. Tell customers to expect relevant browser prompts and to approve only access they understand. Camera access and screen sharing are different workflows; do not assume that every device or browser supports the same sharing options.

If the agent cannot see the intended view, first confirm that the customer opened the correct link. Next, check whether camera access was denied, whether the lens is covered, and whether the internet connection is usable. Retry after addressing the likely cause rather than repeatedly resending links. If the customer cannot operate the prompts or hold the device, offer another support route. W3C’s mobile accessibility guidance is a useful reference for planning accessible instructions and alternatives.

During a live video support session, the agent should direct one observation at a time. Begin with a wider view to establish context, then ask for a closer view of the relevant label, indicator, or visible condition. Have the customer pause while the agent checks details. Repeat important text back for confirmation rather than guessing from a blurred image.

For example, a property support team receives a report that a wall thermostat is blank. The agent sends the link, asks the resident to show the thermostat and model label, and checks the normal user controls against approved troubleshooting instructions. The resident should not remove wiring covers or access energized components. If the display remains unreadable or the approved checks do not resolve the issue, arrange technician review. In the service record, distinguish the resident’s report, the agent’s observations, and anything that could not be verified.

A remote view can help clarify a problem, but it cannot establish conditions outside the camera’s field of view or replace measurements and physical tests. Poor lighting, obstructed access, an unstable connection, or an unsafe location can make further remote troubleshooting inappropriate. Stop when the next step would require hazardous access or expertise the customer does not have.

For government inspections or insurer and lender workflows, use the session within the organization’s established review process. ICC’s remote virtual inspection resources provide general context; they do not establish that a particular case qualifies for remote handling. Seek qualified human review when observations conflict or a consequential decision depends on uncertain information. Arrange an in-person visit when concealed conditions, required testing, or local procedures demand it. Close by stating what was observed, what remains unresolved, who owns the next action, and how the customer will receive an update.