Optional inquiry or access gate?
A contact form offers a next step while the visitor explores. A POI form attaches that action to a relevant location. Lead protection can require contact information before tour access. These serve different purposes and can create different levels of friction.
Start with the information a visitor needs and ask only for fields useful to the request. A visible form or success message does not by itself prove that a notification email was delivered. Read the funnel guide for page context and follow-up.
Configure a main form
- Open
Virtual Tours → Main Form. Set title, description, button text and the reply shown after submission. - Choose fields, their types and which ones are required. Configure notification email settings where used, then save.
- Open
Virtual Tours → Editor UI, enable and position the main-form control, and save the interface. - Open the visitor link outside the editor session and submit an identifiable test request.
- Check collected data and notification receipt separately before relying on the workflow.
The official forms tutorial documents these controls and the Collected data → Forms section.
Add a form at a useful scene location
In Virtual Tours → POIs, select the room, add a POI, choose its style and select Form content. Configure fields and behavior, save and position the point. Test the actual visitor interaction and delivery.
Use a location-specific form only when that context helps the request. A generic contact action may be easier to maintain than several nearly identical forms. Keep essential contact details available as normal page text as well.
Protect access separately
In publishing protection settings, choose the intended password, lead or supported signup workflow and review the visitor prompt and related settings. Follow the protection tutorial. An embed does not bypass tour access controls.
Test a new private browser session and intended return visits. Decide whether collecting information before entry is appropriate for the audience. Configuring fields does not establish compliance with every jurisdiction or make visitors qualified leads automatically.
Measure the complete path
Define a meaningful inquiry and verify storage, notification and follow-up. A POI view, a form open and a completed inquiry are different events. Native tour reports and external analytics do not automatically use the same definitions.
Use the analytics guide to plan checks. For a property, connect the action to accurate listing information; for a hotel, link to the correct inquiry or booking destination. No inquiry or sales lift is guaranteed.
Availability and delivery
Check the selected release, plan and account functions, and configure email delivery on the actual hosting setup. This page describes form features, not a separate lead-capture plugin. Customer editing accounts and platform subscriptions are described in SaaS.
Build the base tour with the creation guide, deliver it with the embedding guide and review software and operating costs.