Skip to main content

Virtual Reality and Salesforce integration for Real Estate

About Us
Published by admin
18 December 2018
144

Surely, you have ever thought of how to convert more Leads to Opportunity, how to recapture clients after first interaction with sales managers. Real estate is a sphere where such a problem really exists and many companies struggle to solve it by all means.

This is exactly what led. The Parallel (international company headquartered in London specializing in XR (virtual, augmented reality)) and JET BI to join their forces and to create a system - integration between Virtual Reality experience and Salesforce CRM to track customers` behavior in Real Estate and to drive sales process on a new level.

How does VR CRM work?

1

For today, VR CRM builds customer route, displaying sight direction and duration of sight on each dot. The system analyzes data about most preferable districts and objects, marks dots of specific customer’s attraction, gathers information from neurogadget, which helps correct data and pay attention to points of interest, which are triggered instinctively. For analytic purposes also was developed Heatmap feature, which displays data, stored for all sessions and can vibrantly demonstrate locations, which were most attractive to this or that group of customers (can be filtered by gender, age, and country).

Our plans

And we have no plans to stop there. The tool has been already presented at several exhibitions and technical events (in Finland, Germany, in the USA) and received positive feedback. New features, which will be available soon:

  • Each dot will be guided with an audio recording from the conversation with a customer;
  • Customize commercial offer creation and sending upon VR session finishing; 

User’s route

2

Summary information about session

3

Heatmap

4

Apartment view

4525


Anna Metsik
Virtual Reality Consultant
image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026