Visual Remote Assistant: How to Set One Up Quickly
Learn how to set up a visual remote assistant in four steps and cut dispatch costs with live video and AR annotations for faster field support.

A visual remote assistant lets support agents see exactly what a customer sees, using live video and AR annotations to resolve issues without a site visit. The setup follows four steps: define your goals, choose a platform, configure permissions and page layouts, and send customers a browser-based link. No app download is required on the customer side.
Field service teams spend heavily on dispatching technicians to problems that a guided video call could solve in minutes. Any contact centre team, regardless of which CX platform they use, can deploy a visual remote assistant without rebuilding existing workflows.
Field service teams spend heavily on dispatching technicians to problems that a guided video call could solve in minutes. Any contact centre team, regardless of which CX platform they use, can deploy a visual remote assistant without rebuilding existing workflows.
What Is a Visual Remote Assistant and Why Does It Matter?
A visual remote assistant connects a support agent to a customer's live camera feed. The agent can see the physical environment, annotate the screen, and guide the customer through a fix in real time. It combines video calling with AR overlays to replace the need for an on-site technician.
The business case is backed by reported outcomes. According to CareAR's published case study, one HVAC support team cut call times by 30% after adopting AR remote assistance. The same source reports that one support organisation deflected 40,000 dispatches over six months through remote troubleshooting. Separately, ADT reported avoiding 1 million truck rolls in the first year of using Salesforce Visual Remote Assistant.
The market reflects this momentum. According to IBM's 2026 analysis, the AR remote visual assistance market is projected to grow from USD 1.6 billion in 2023 to USD 14 billion by 2030, at a compound annual growth rate of 35%.
Common use cases include field service (HVAC, utilities, telecom), insurance claims inspection, retail product support, and healthcare device guidance.
How Do You Choose the Right Visual Remote Assistant Platform?
Your platform choice depends on the CX infrastructure you already run. Two main paths exist: a Salesforce-native tool and browser-based video CX tools that connect to other contact centre platforms.
Salesforce Visual Remote Assistant is built directly into Salesforce Service Cloud and Field Service. It provides real-time video with AR annotations, session recording, and desktop sharing, all within the Salesforce interface. Customers join from their mobile browser with no app required. The trade-off is that it requires existing Service Cloud or Salesforce Field Service licences, so it is only a fit if your team already works in that ecosystem.
For teams on Genesys Cloud, NICE, Talkdesk, Verint, Five9, or RingCentral, a browser-based video CX platform is the more direct path. These tools add video calling and cobrowsing to your existing workflows without requiring agents to switch platforms. You can review the Video CX & Cobrowse Features available through this approach to see what a non-Salesforce integration covers.
The core features to evaluate across any platform are: AR annotation tools, no-download browser access for customers, session recording, and native integration with your existing ticketing or CRM system.
Step 1: Define Your Goals and Pain Points
Before touching any configuration, get specific about the problem you are solving. Vague goals produce vague deployments. Start with a clear target, not a general ambition to "improve support."
Start by identifying the support scenarios that cost the most or resolve the slowest. High truck roll volume is the most common driver. If dispatching a technician costs your organisation hundreds of dollars per visit, and a meaningful share of those visits involve problems a camera could diagnose, that is your primary target. CareAR's reported data shows a support team deflecting 40,000 dispatches over six months, which illustrates the scale of savings that is possible when the use case is well-defined.
Resolution time is the second metric to pin down. If average handle time for a category of issue is long because agents cannot see what the customer is describing, AR-guided video can shorten that gap. CareAR also reports a 30% reduction in call times for one HVAC team. Use your own baseline numbers to set a target before you go live.
Write down two or three specific support scenarios, the current cost or time per incident, and the outcome you want to hit. Those numbers become your benchmark once the tool is live.
Steps 2 to 4: Configure Your Platform, Permissions, and Page Layouts
Once your goals are clear, the configuration sequence follows a consistent pattern across platforms, with some steps that are specific to Salesforce.
Install the integration or managed package. For Salesforce Visual Remote Assistant, this means installing the managed package from AppExchange into your Service Cloud or Field Service org. For non-Salesforce platforms, this step is typically an OAuth connection or API key setup within your contact centre's app marketplace.
Set user permissions. Assign the correct permissions to agents who will run visual sessions. In Salesforce, this means enabling access through the appropriate permission sets in your org's setup. On other platforms, enable video calling at the user or queue level through the admin console.
Configure page layouts (Salesforce-specific). Add the relevant session and history components to the page layouts of your cloud objects, such as Contacts or Service Appointments. This places session controls and the history log directly on the records agents work from. This step applies to Salesforce only. On other CX platforms, the equivalent is embedding the video widget into the agent desktop or enabling the escalation button within the existing chat or voice interface.
Test with internal users before going live. Run a session between two agents to confirm video quality, annotation tools, and session recording all work as expected. Aim for at least five internal test sessions before the first customer call.
Does the Customer Need to Download an App?
No. Customers join a visual remote session through their mobile browser with no app or plugin required.
The agent initiates the session by sending the customer a link. The customer taps it, grants camera permission in their browser, and the live video feed opens. The whole flow takes under a minute. This removes the single biggest adoption barrier: customers who would abandon a support interaction rather than download an unfamiliar app.
Auvious is a browser-based video CX platform that lets agents escalate from chat or voice to a live video session in one click, with no app required on the customer side. The same no-download principle applies to Salesforce Visual Remote Assistant, where the customer experience is also browser-based.
Agents control the session from their existing CX platform interface. No new tool to learn.
What AR Features Can Agents Use During a Live Session?
AR tools are what separate visual remote assistance from a plain video call. During a live session, agents can use annotation and guidance features to direct a customer's attention to a specific component or step.
3D annotations and arrows. Agents draw directly on the live video feed to point at a specific component, wire, or part.
Freeze-frame. The agent pauses the video stream so the customer can focus on a still image while following instructions.
Text and shape overlays. Agents can add labels or highlight zones on the image to mark steps in a sequence.
Session recording. Salesforce Visual Remote Assistant includes session recording natively, per salesforce.com. Check your chosen platform for equivalent capability.
Hands-free device support. Some platforms support smart glasses or wearable cameras for field technicians who need both hands free. Confirm this with your chosen vendor.
Together, these tools let an agent guide a customer through a multi-step repair or inspection without any ambiguity about which part or step is being discussed.
Prices and plan limits verified as of October 2026.
FAQs
What is the difference between a visual remote assistant and a standard video call?
A standard video call shows the customer's face. A visual remote assistant streams the customer's environment through their rear camera and adds AR tools so the agent can annotate what they see in real time. The agent can draw arrows, freeze the frame, and mark specific components, making it a diagnostic and guidance tool rather than just a communication channel.
How secure is the session link sent to the customer?
Security practices vary by platform. Confirm your chosen vendor's approach to link expiry, session termination, data encryption, and compliance certifications, particularly for regulated industries like healthcare or financial services.
Can visual remote assistance work on older mobile devices?
Browser-based sessions require a modern mobile browser and a rear camera. Very old devices running outdated operating systems may not support browser-based video. Run a quick test with a sample of your customer base before launch to surface any compatibility gaps.
What CX platforms support visual remote assistant integrations?
Salesforce Visual Remote Assistant integrates with Salesforce Service Cloud and Field Service. Browser-based video CX tools integrate with a wider range of platforms. Genesys Cloud, NICE, Talkdesk, Verint, Five9, and RingCentral all support this type of integration, letting agents trigger video sessions without leaving their existing interface.
How do I measure the ROI of a visual remote assistant deployment?
Track three numbers: truck rolls avoided, average handle time for video-assisted cases versus non-video cases, and first-contact resolution rate. Set a 90-day baseline before launch, then compare after the first full quarter. Dispatch cost per visit varies widely by industry, so use your own figure rather than industry averages to calculate savings accurately.
Conclusion
A visual remote assistant gives support teams a direct way to resolve physical problems remotely, combining live video with AR annotation tools that guide customers step by step. The setup process is straightforward: define the support scenarios you want to address, choose a platform that fits your existing CX stack, configure permissions and agent-side controls, and send customers a browser link to join.
If your team already works in Salesforce, the native Visual Remote Assistant is the logical starting point. If you run a different contact centre platform, look for a browser-based video tool that integrates directly into your existing agent desktop.
See auvious inside your own contact centre.
Book a 30-minute demo and we will show you browser-based video and cobrowse working inside the platform you already use.