Yes, you can embed custom forms directly inside a virtual tour, and three approaches cover nearly every use case: a persistent main form button, a POI or scene-level form, and a hotspot-activated popup. The key to conversions is matching form depth to where the visitor sits in your funnel and placing each form where it makes contextual sense.
TL;DR:
- Forms should be placed based on the visitor's funnel stage, with top-of-funnel forms limited to email and a single intent question to reduce abandonment.
- Mobile form design requires large tap targets, vertical stacking, and simple dropdowns to prevent frustration and improve completion rates.
- Testing on mobile data and verifying form activation, required fields, and notification setup prevents common technical issues.
- Submissions should be mapped automatically to CRMs or webhooks, and monitoring abandonment at each funnel stage enables ongoing optimization.
- Privacy compliance entails clear messaging about data use, minimizing unnecessary fields, and restricting data access, especially when collecting personal information.
Table of Contents
- Where to place forms inside your tour
- How to add and activate forms in your tour builder
- Choosing the right fields for each funnel stage
- Multi-step forms, conditional logic, and smart triggers
- Where submitted form data goes and how to connect it
- How Simple Virtual Tour handles forms and lead capture
- Privacy and data protection for forms in virtual tours
- Keeping forms fast on load
- Making sure forms work well on mobile
- Common troubleshooting tips for form issues
- Tracking form conversions and what to measure
- A practical launch-day checklist
- Try Simple Virtual Tour for your own forms
- FAQ
- Sources
Where to place forms inside your tour
Each placement option serves a different purpose, and choosing the right one depends on what you're asking the visitor to do and how far along they already are in their decision.
- Persistent main form (button): A fixed button visible throughout the tour, ideal for a general "contact us" or "request info" action that should always stay within reach.
- POI or scene form: A form attached to a specific point of interest, useful when a particular room, exhibit, or location naturally invites a question or booking request.
- Hotspot-activated popup: A form triggered by clicking an icon inside a scene, well suited to brochure requests, scheduling a viewing, or capturing feedback at a natural pause point.
- Inline embed: A form built into the tour layout itself rather than triggered by an action, often used for feedback surveys at the end of a walkthrough.
On mobile, fewer simultaneous prompts work better since screen space is limited, so reserve popups for moments with real intent signal rather than firing one on every scene change. Our hotspot design checklist walks through matching a form's placement to the visitor's current context in more depth.
How to add and activate forms in your tour builder
Most tour editors follow a similar pattern for setting up forms, and Simple Virtual Tour's workflow is a good reference point since its documentation lays out each step clearly.
- Open your tour editor and locate the form settings, usually under an Editor UI → Main Form menu for a persistent form.
- Give the form a title, a short description, and button text that tells visitors exactly what happens when they click.
- Choose your fields and mark which ones are required, keeping the required list as short as your funnel stage allows.
- Set a reply or confirmation message so visitors know their submission went through.
- Add a notification email address so you (or your team) get alerted the moment a form comes in.
- For a scene-specific form, go to POIs → Add POI, then choose Form as the POI's content type instead of a hotspot link.
- Preview the tour and submit a test entry yourself to confirm the data appears where expected.
- Check your collected-data screen and your inbox to verify the notification and confirmation message both fired correctly.
Simple Virtual Tour's tutorial on adding forms documents these exact settings, including title, description, button text, reply message, notification email, and field selection, alongside where to find submissions once they come in.
Pro Tip: Submit a test entry from a phone, not just a desktop browser, since mobile keyboards and field spacing sometimes reveal layout issues a desktop preview won't catch.
Choosing the right fields for each funnel stage
The biggest mistake in form design isn't a missing feature, it's asking for too much too soon. A visitor who just opened your tour has a different tolerance for questions than one who has already spent several minutes exploring a specific room or unit.
Industry guidance on lead forms points to a clear pattern: top-of-funnel forms perform best with a small number of fields, typically just an email address and one intent signal, while mid-funnel forms can expand to several fields, and bottom-funnel qualification forms can reasonably ask for multiple fields or be broken into a multi-step flow, according to OrbitForms' real estate lead form guide. That structure holds up because each added field creates another chance for a visitor to abandon the form before they've committed to the action.
- Top-of-funnel example: name, email, and a single dropdown for "what are you looking for?"
- Mid-funnel example: name, email, phone (optional), preferred move-in timeline, and budget range.
- Bottom-funnel example: full contact details, specific unit or scene reference, financing status, and one open-text field for questions or notes.
Use dropdowns or radio buttons for structured data like budget and timeline rather than open text, since structured answers are what actually make the data usable later for segmentation or routing. Keep phone number optional until the visitor shows stronger intent, and always include one open-text field so visitors can add context a dropdown can't capture.
Multi-step forms, conditional logic, and smart triggers
Long forms discourage completion, but breaking the same questions into a one-question-at-a-time flow with a visible progress indicator tends to keep visitors moving instead of abandoning midway, a pattern OrbitForms also highlights as a completion driver for real estate lead capture.
Conditional branching takes this further by only asking questions relevant to the visitor's path. A tour for a property, for example, might branch into a buyer path asking about financing and timeline, or a seller path asking about current property details, instead of showing both sets of fields to everyone.
- Hotspot click trigger: opens a booking form the instant a visitor clicks a "schedule a viewing" icon in a relevant scene.
- Timed popup: appears after a visitor has spent a set amount of time in the tour, signaling real engagement.
- Exit-intent trigger: captures an email address with a low-friction offer just as a visitor is about to leave.
Pro Tip: Start with just two branches (buyer versus seller, or inquiry versus booking) before building out more complex logic, since each added branch multiplies the testing you'll need to do.
Where submitted form data goes and how to connect it
Once a visitor submits a form, you need a reliable path from that submission to someone who can act on it. Most tour admin panels, including Simple Virtual Tour's, include a dedicated collected-data screen where you can view or export every submission, as outlined in the Main Form and POI form tutorial.
- Check the admin UI's collected-data screen first to confirm a submission actually registered.
- Set a notification email and test it immediately after enabling any new form.
- For ongoing lead flow, map submissions directly into your CRM, as explained in our guide on mapping virtual tour leads to your CRM.
- Use webhooks or an automation tool like Zapier when you need to route specific leads, such as high-intent bottom-funnel submissions, to senior staff automatically.
How Simple Virtual Tour handles forms and lead capture
We built Simple Virtual Tour's form system around the same main form and POI form structure described above, available whether you run a cloud-hosted subscription or a self-hosted deployment with full source code ownership. Both paths support the same field settings, notification setup, and CRM-ready submission data, backed by an editor interface designed for non-technical users.
We've designed every form setting, from button text to notification email, to be configurable without touching code.
Our platform currently serves many active users, with plugin options and documented tutorials covering form setup in detail on our product site.
Privacy and data protection for forms in virtual tours
Any form collecting names, emails, or phone numbers inside a tour is collecting personal data, which means the same privacy expectations that apply to a standalone contact form apply here too. Visitors should know what they're submitting and why before they hit the button.
A clear, short description above the form fields does more for trust than a lengthy policy link buried in a footer. State plainly what happens after submission, whether that's a callback, a brochure email, or a scheduling confirmation. If you operate a self-hosted deployment, you control where that data lives, which matters for organizations with specific data residency or retention requirements.
Avoid collecting fields you don't actually need. A feedback form doesn't need a phone number, and a brochure request doesn't need a budget range. Every unnecessary field is both a conversion drag and an added data liability. When you do store submissions, make sure access to the collected-data screen is limited to people who need it, and remove or archive old submissions on a schedule rather than letting them accumulate indefinitely.
If your tour serves visitors across different regions, consult your own legal counsel or a privacy specialist about consent language and retention rules that apply to your specific audience, since requirements vary by jurisdiction and by the type of data you collect.
Keeping forms fast on load
A form that lags behind the rest of a tour's smooth panorama transitions stands out for the wrong reason. Visitors who came for an interactive walkthrough expect the form to feel just as responsive.
Keep field counts aligned with funnel stage, since fewer fields mean less to render and less for a visitor to wait through. Avoid loading heavy scripts or third-party embeds inside a popup that only needs to appear once per session, and lean on your tour platform's native form feature rather than stacking an external form builder's script on top of it when you can avoid it.
Test your form's appearance on a throttled connection, not just your office Wi-Fi, since a visitor touring a property from a phone on mobile data will notice a slow popup far more than someone on a desktop. If you're using conditional logic, confirm that branching happens instantly rather than triggering a visible reload, since a stutter at that moment can cost you the submission entirely.
Making sure forms work well on mobile
Most virtual tour traffic now happens on phones, so a form that's easy to fill out on a small screen matters as much as the tour itself looking good there. Buttons need to be large enough to tap accurately, and fields should stack vertically rather than cramming side by side.
Dropdowns and radio buttons tend to work better than long text fields on mobile, since typing on a phone keyboard is slower and more error-prone than tapping a preset option. Keep your required field count especially tight on mobile-first tours, since abandonment rates climb quickly once a form demands more than a few taps.
Common troubleshooting tips for form issues
Most form problems in a virtual tour trace back to a handful of recurring causes, and checking these first will resolve the majority of issues without needing deeper technical digging.
If a form isn't appearing at all, confirm it was actually activated in the editor UI rather than just saved as a draft. If submissions aren't showing up in your collected-data screen, check that required fields were correctly marked, since a misconfigured required field can silently block submission on some browsers. When notification emails aren't arriving, verify the address in your form settings first, then check spam folders before assuming the integration is broken. If a POI form doesn't display correctly on a specific scene, confirm the POI's content type is actually set to Form and not still pointing to a hotspot link or media file.
For CRM or webhook integrations that stop syncing, test the connection with a single manual submission before troubleshooting further upstream, since most sync failures come from an expired API key or a changed field mapping rather than a platform-wide outage.
Tracking form conversions and what to measure
Knowing how many visitors reach a form is only half the picture. You also need to know how many actually complete it, and where they tend to drop off if they don't.
Track submissions against total tour sessions to get a baseline completion rate, then break that down by placement, comparing a persistent main form button against a hotspot-triggered popup to see which earns more completions relative to its visibility. If you're running multi-step forms, watch for the specific step where abandonment spikes, since that's usually where a field feels too invasive or unclear. Over time, compare completion rates across funnel-stage field sets (the 2 to 3 field top-of-funnel version against a longer bottom-funnel form) to confirm your field counts are actually matched to visitor intent rather than just assumed.
A practical launch-day checklist
Embed a form wherever a scene supports a clear next action, such as booking a viewing, requesting a brochure, or getting a quote, and skip it where no real action exists.
- Confirm placement matches the scene's intent.
- Set field count to match funnel stage.
- Enable and test notification emails.
- Map submissions to your CRM or webhook.
- Submit a test entry yourself.
- Monitor completion rate weekly.
— Andrea
Try Simple Virtual Tour for your own forms
If you want main forms and POI forms set up the way we've described here, without writing any code, Simple Virtual Tour gives you both the editor controls and the deployment flexibility to make it happen. We support cloud-hosted subscriptions for teams that want everything managed, and a self-hosted option with full source code ownership for organizations that want control over where their lead data lives.
- Main and POI forms, CRM mapping, and notification settings come configured through the same non-technical backend.
- Choose cloud hosting starting with our Free Forever plan, or a one-time self-hosted purchase with no ongoing subscription cost.
- Plugin options extend functionality further, including CRM and e-commerce integrations for teams scaling past a single tour.
Ready to set up your first form? Get started with Simple Virtual Tour and have your main form live in your tour today.
FAQ
What software can I use to create virtual tours?
Several platforms let you build interactive virtual tours, ranging from simple photo-based walkthroughs to full panorama tools with embedded forms. Simple Virtual Tour is one option built specifically to support both cloud-hosted and self-hosted deployment, along with main and POI form features for lead capture.
What are the downsides of virtual travel?
Virtual travel can't replicate the sensory details of being physically present, such as scale, temperature, or ambient sound, which limits how much a tour alone can substitute for an in-person visit. It also depends heavily on connection quality, so a visitor on a slow connection may get a degraded experience of panoramas or embedded forms.
How do I make my own virtual tour?
Creating a virtual tour typically starts with capturing photos or video of each space, then uploading them into a tour builder where you link scenes together with hotspots. From there, you add interactive elements like POIs, forms, and branding before publishing the finished tour for visitors to explore.
How do I create virtual field trips?
Virtual field trips follow the same core process as other virtual tours: capture panoramic images of each location, sequence them in a tour builder, and add informational hotspots or POIs that explain what students are looking at. Adding a short feedback or quiz-style form at the end can help confirm what visitors took away from the experience.
How do I create forms for virtual tours?
Most tour editors let you add a persistent main form through the editor's form settings, or attach a form to a specific point of interest by choosing Form as that POI's content type. From there, you set the title, description, button text, required fields, and a notification email so submissions reach your inbox.
Sources
- Simple Virtual Tour - Tutorials | How to add Forms into the Tour (Main Form / POIs Form)?
- Real estate lead forms — OrbitForms blog