Two questions come up in almost every customer conversation. How do I get guest data into my CRM without paying someone to build an integration? And how do I compare performance across all my properties without exporting each one and stitching the results together? The Aislelabs product release for September answers the first. Aislelabs Connect now syncs captured guest data into Salesforce on its own, with no custom integration and no developer time. The August release, covered further down, answers the second, alongside occupancy reporting and a new way to analyze groups of zones together.
The September Release
Connect guest data directly to Salesforce
Moving captured guest data into Salesforce used to require a custom integration. It does not anymore.
Aislelabs Connect administrators authorize their Salesforce organization from inside Aislelabs, and captured guest information starts syncing automatically. The sync runs daily, one way, and covers email address, name, phone number, and marketing consent status. Incoming records are matched against existing Salesforce records on email address or phone number, so a returning guest updates a record rather than creating a second one.
From inside Aislelabs you can check connection status, see the timestamp of the last successful sync, reauthorize, or disconnect at any time.
One prerequisite: Salesforce API access must be available with your Salesforce edition. API access is not included in every edition, so confirm yours before setting up the connection.
Give access points recognizable names
You can now assign human-readable names to access points in Flow AI, such as “Main Entrance” or “Food Court – East.” Names are editable from the access point tooltip on the sensor map and also appear in Data Health.
The original identifier stays visible, so IT teams can still match a sensor against network equipment. Plain language for the conversation, the raw identifier for the ticket.
Reuse splash page designs across page types
Connect administrators can reuse an existing captive portal design across login, success, error, and terms and conditions pages. Shared branding and layout carry over, while content specific to each destination page is preserved. One design decision applied everywhere, rather than rebuilding the same header four times.
Also fixed and improved
Smart Review reliability. Configured review destinations, including Google Maps, now appear correctly after a guest submits positive feedback, and Smart Review interactions are recorded more consistently, which improves confidence in campaign reporting. As always, only the review destinations configured for that location are shown to the guest.
Flow AI service health monitoring. Internal health checks now confirm that the platform can successfully serve analytics requests, rather than only confirming that the underlying process is running. That means faster detection and recovery when data services are unavailable.
The August Release
Analyze performance across multiple sites
If you manage a portfolio, this is the change that removes the most work.
Flow AI users can now review analytics across multiple sites in one place. There is no need to move between properties one at a time, export each one, and combine the results in a spreadsheet before you can answer a portfolio-level question. Comparing activity across locations becomes a view rather than a project, and a regional performance question that used to mean a morning of exports is now something you can answer while the question is still being asked.
It matters most for teams responsible for more than one property: retail destination groups, restaurant operators managing several locations, and anyone reporting upward on portfolio performance rather than a single site.
Explore performance by area
The new Areas experience reports on how groups of zones perform within a property. An area is a group of zones, which lets you analyze a wing of a shopping centre, a dining precinct, or an event hall as a single unit rather than reconciling its zones by hand.
For each area you can review total devices, average dwell time, visits, unique visitors, and visits per device. Areas can be compared side by side in a sortable table, expanded to show daily visit and dwell time trends, and exported for further analysis.
Report on occupancy
Occupancy is now a reportable Flow AI metric, showing how many visitors are present within a location at a given time.
Total visits tell you how many people came. Occupancy tells you how many were there at once, which is the number that matters for events, exhibitions, capacity planning, and any environment where concurrent attendance drives the decision.
View sensor placement on a floor map
Flow AI now includes a visual map of access point placement within each zone. Knowing where sensors physically sit gives coverage questions and data health investigations the context they were missing, and it sets up the Sensor Health view that arrived in September, which builds on the same map.
Also improved
Clearer site-level trend charts. Visits and dwell time now use distinct visual treatments rather than overlapping series, so changes over time are easier to spot and easier to explain to someone reading the chart for the first time.
Complete zone heatmaps. Zones with no activity during the selected period stay visible and display a value of zero. Previously an inactive zone simply was not there, which left an open question: was it excluded, misconfigured, or genuinely empty?
More predictable sensor lists. Sensor and device lists use a consistent default sort order based on name or identifier. You can still apply a different sort when you need one, but the list you return to looks like the list you left.
Easier navigation between sites and zones. Site and zone views can be opened in separate browser tabs, which makes side by side comparison and multi-location workflows considerably less tedious.
Frequently Asked Questions
In Aislelabs Connect, an admin authorizes your Salesforce organization from inside Aislelabs. Guest data captured on your captive portal then syncs to Salesforce automatically, with no custom integration and no middleware. Setup is an authorization step rather than a development project.
Four fields: email address, name, phone number, and marketing consent status. These are captured when a guest logs in through the Aislelabs Connect captive portal, and they are written to Salesforce on each sync.
No. The sync is one way, from Aislelabs Connect into Salesforce. Admins can see the timestamp of the last successful sync inside Aislelabs.
Aislelabs Connect matches incoming guest data against existing Salesforce records using email address or phone number. A returning guest updates the record that already exists rather than creating a second one.
Yes. Assign a human-readable name such as “Main Entrance” from the access point tooltip on the sensor map in Aislelabs Flow AI. Names also appear in Data Health. The original identifier stays visible so IT teams can match it to network equipment.
Yes. Aislelabs Flow AI supports multi-site analysis, so you can review performance across properties in one view rather than exporting each location and combining the results manually.
A zone is an individual tracked space within a property. An area is a group of zones. The Areas view in Aislelabs Flow AI reports on those groups together, covering total devices, average dwell time, visits, unique visitors, and visits per device.
Visits count how many people came to a location over a period. Occupancy shows how many were present at the same time. Occupancy is reportable in Aislelabs Flow AI and is the more useful measure for events, exhibitions, and capacity planning.
Need help?
If you have questions about anything in these releases or want help getting started, contact your Aislelabs representative or the Aislelabs team.
