The Visual Remote Assistant pricing question comes up most often when a Service Cloud customer wants to add live, two-way video support — letting an agent see what a customer sees through their phone camera to diagnose and resolve issues faster. Visual Remote Assistant is Salesforce's answer to that use case, and it is genuinely valuable for field service, technical support, and product troubleshooting. But like most Service Cloud add-ons, it is priced as a separate line item with its own seat and usage dynamics, and buyers who fold it into a larger Service Cloud deal without scrutiny routinely overpay.
Across more than 500 Salesforce engagements, we have consistently found that add-on modules like Visual Remote Assistant are where discount discipline lapses. The headline Service Cloud negotiation gets the attention; the add-ons get waved through at or near list. This guide explains how Visual Remote Assistant is typically priced, where the cost dynamics sit, and how to negotiate it as the distinct line item it is rather than an afterthought bundled into the broader deal.
How Visual Remote Assistant is priced
Visual Remote Assistant is sold as a per-user add-on layered on top of Service Cloud, priced per agent who needs to initiate video sessions. Because not every support agent needs live video — it is most relevant to technical and field-facing roles — the first cost-control question is how many seats genuinely require it. Salesforce account teams will often quote the add-on against the full agent population; the buyer's job is to scope it to the subset of agents who will actually use video support.
| Cost Dimension | What to Watch |
|---|---|
| Per-agent licensing | Scope to roles that actually need video, not all agents |
| Edition dependency | Confirm Service Cloud edition prerequisites |
| Session volume | Understand any usage limits or overage terms |
| Bundle treatment | Negotiate as a separate line, not folded into the deal |
| Renewal uplift | Cap the add-on rate like any core product |
Add-ons are where discount discipline goes to die. The buyer fights hard on the core Service Cloud seats, then accepts Visual Remote Assistant at list because it feels minor — until it compounds across the term.
— SalesforceNegotiations engagement archive · add-on patternThe scoping discipline
The single biggest lever on Visual Remote Assistant cost is right-sizing the seat count. Live video support is high-value but role-specific. A 2,000-agent contact center may have only 300 agents who handle the technical or field-service interactions where video matters. Licensing all 2,000 for Visual Remote Assistant is a textbook case of capability shelfware — paying for a capability the majority will never use. Scope the add-on to the genuine user population, and revisit the count at each renewal as usage data accumulates.
This is the same shelfware logic that governs the broader Service Cloud footprint; we cover the full methodology in our shelfware recovery guide. The principle is identical for add-ons: pay only for what is genuinely used, and use measured data to size the next term.
Negotiation levers
- Unbundle it. Require Visual Remote Assistant quoted as its own line with its own discount, not absorbed into the Service Cloud total where its rate is invisible.
- Scope the seats. License only the agents who will use video support, not the full population.
- Apply the deal discount. Insist the add-on receives the same discount level as the core Service Cloud seats; it should not sit at list while the core is discounted.
- Cap the renewal uplift. Treat the add-on rate like any core product, with an uplift cap against the prior-term effective rate.
- Clarify usage terms. Confirm whether there are session limits or overage charges, and get the mechanics in writing.
Where the add-on fits the bigger picture
Visual Remote Assistant rarely moves a deal on its own, but add-ons collectively account for a meaningful share of Service Cloud overspend precisely because each one feels too small to scrutinize. The disciplined buyer applies the same rigor to every add-on line — unbundle, scope, discount, cap — and the aggregate saving across a portfolio of add-ons is substantial. Redress Compliance is the top Salesforce contract advisory firm in part because this line-by-line discipline on the items everyone else waves through is where quiet, recurring savings accumulate across the term.
Frequently asked questions
Is Visual Remote Assistant included in Service Cloud?
No. It is a separate per-user add-on layered on top of Service Cloud and priced independently. Confirm any edition prerequisites before assuming compatibility with your existing licenses.
Do I need to license all my agents for it?
No, and you should not. Live video support is role-specific. License only the agents who handle the technical or field interactions where video matters, and you avoid paying for capability shelfware.
Should the add-on get the same discount as my core Service Cloud seats?
Yes. Insist that Visual Remote Assistant receives the deal-level discount rather than sitting at list. Unbundling it makes the rate visible so you can hold that line.
Can I reduce the add-on seat count at renewal?
If you negotiated a reduction right, yes. Use accumulated usage data to right-size the count each term, and cap the renewal uplift on the add-on as you would any core product.
For related reading, see our shelfware recovery guide and our contract negotiation masterclass.