Bring live visual support into Salesforce
Give service agents and field teams a way to start SightCall visual support sessions from Salesforce, connect with customers or technicians, and keep session information tied to service records.
What can you do with SightCall in Salesforce?
Launch visual support from Salesforce
Start SightCall sessions from supported Salesforce interfaces, without making agents navigate to a separate service workflow.
Connect with customers and technicians
Invite a remote participant to a session using supported SMS, email, or URL invitation methods. Mobile-to-mobile initiation is also documented.
Keep session information with service records
Configure SightCall session reports to be associated with Salesforce Cases and, where configured, other objects such as Work Orders.
Route support requests with Omni-Channel
Use documented Salesforce Omni-Channel queue-based or skill-based configurations to route eligible SightCall requests to agents.
Key Benefits
Resolve more issues remotely
Help teams inspect equipment and customer issues visually before deciding whether an on-site visit or escalation is needed.
Keep teams in a familiar workflow
Bring remote visual assistance into the Salesforce environment service teams already use, reducing the need to switch between disconnected tools.
Preserve context for follow-up
Make configured session reports available with related service records so teams can review earlier interactions and support continuity.
FAQs
Can I launch a SightCall session directly from Salesforce?
Yes, you can initiate SightCall sessions from supported Salesforce interfaces.
How do customers or technicians join a session?
Invitation options include SMS, email, and a session URL, depending on the configured workflow.
Does SightCall write information back to Salesforce?
Configured Call Reports and Meeting Reports can be associated with Salesforce records. The precise fields, objects, and automation depend on implementation.
Can SightCall work with Salesforce Omni-Channel?
Yes. There are queue-based and skill-based routing configurations.