Open House QR Sign-In or Property Page: What Should Visitors Scan?

Separate Property Information From Visitor Sign-In

A person at the front door may simply want to see the floor plan again, check the room sizes or save the agent's contact. Another visitor may want a follow-up and choose to enter details into the agency's existing form. These are different tasks. A QR that opens property information serves the first; a form that records a submitted response serves the second. Scanning either code does not by itself tell the agent who visited.

The QR on a for-sale sign outside has a different setting. A passer-by expects information about that address and may never attend a viewing. The entrance desk is where an agent can explain what a separate sign-in request is for and where it goes. Do not copy the same “Scan here” label onto both signs if the destinations do different things.

Start by writing the visitor-facing promise. “View this property's details” should lead to a public listing or property page. “Send your details to the agent” should lead to the actual form operated by the agency or its provider. If one page presents both, each button must say what happens next. A form is not needed to make basic property information exist on a phone.

Whether the agency asks people to sign in, which information it requests, and what happens after submission are operating decisions for that agency and location. The public page should reflect those decisions instead of hiding them behind a generic “Get access” button.

Choose the First QR Destination

A separate page adds a choice. Use it when that choice helps a visitor; otherwise send the QR to the one action promised beside it.

Keller Williams documents an open-house sign-in form in its own agent-site product. Its flow distinguishes a submitted form from the listing information shown afterward. This is an example of a provider owning registration; it is not a feature of VISU Link.

If the agency already has an excellent listing page and no form to maintain, link directly to the listing. If an agent uses a paper guest book or another existing process, do not create a digital form merely to justify a QR. The visitor should not have to submit information just to discover where the home's details are.

Explain What the External Form Does

When a form is part of the visit, write down its owner before putting a QR beside the front door. The agency chooses the fields and the purpose. The form provider receives the submission. A named agent or team member checks the results and decides how to answer. VISU Link can carry the form URL, but it does not store the response just because the button is on a VISU page.

Ask the operator to prepare a short form brief: the public URL, who can edit it, where a submission arrives, who sees it, and what the visitor sees after pressing Submit. If the form sends an acknowledgement, confirm exactly what it says. Do not write “registered” or “we will contact you today” on the VISU page unless the provider and team actually support that wording.

Keep the property path useful on its own. A visitor might look at the plan during the viewing, or share the listing with someone afterward. If the agency chooses to ask for details, that choice should be visible rather than disguised as an access gate. Local rules and agency policy about visitor data belong with the people responsible for the form.

Prepare a fallback for a phone without connection or a form that does not load. The host can still tell the visitor where the property details are and use the agency's normal alternative process. A single failed network request should not leave the agent unable to explain the home.

A Fictional Saturday Viewing

Fictional example. An agency shows 42 Example Lane on Saturday. Its street sign QR opens the current public property page, which has photos, details and the agent's contact. That sign serves a passer-by even when the home is not open. The open-house desk has a separate card that says “Property details and agent contact” and can open the same page.

The agency also uses an external sign-in form and wants to offer it at the desk. A second card says “Send your details to the agent” and opens that form. The form provider, not VISU, handles the fields and the submitted record. The host can explain that sending details is a separate action from reading the home's information.

If the desk has room for only one QR, the agency can use a property-specific VISU Link page with two buttons: “View property details” and “Send details to the agent.” The first opens the public property page. The second opens the external form. The page does not know who has physically walked through the door and cannot call a scan a completed sign-in.

Before the viewing, the agent opens both links on a phone and checks that the external form belongs to 42 Example Lane and reaches the right team. After the viewing, the agency handles submitted responses in its provider and follows its own process. If the property is withdrawn, it updates the public page and removes the visit card. None of this creates automatic visitor follow-up in VISU.

Give the Agent a Usable Handoff

The useful result of a submitted form is a response in the tool the agency already uses, not a count of QR scans. Before the event, the manager should know which agent receives the form, where that agent checks it and how the visitor is told what happens next. If the form is run by a vendor, test the notification and record location there according to the agency's own process.

Do not put “qualified lead” on a dashboard label because someone opened a page. The agent may see page visits or outgoing clicks where metrics are available, but those signals do not identify a visitor, prove a form was sent or confirm an inquiry. Submitted form records, suitable contact requests and actual follow-up are separate evidence.

One person should own the property information; another may own the external form. If the listing agent changes, update the contact on the property route and the form recipient. If the form URL changes, update the button and retest the desk card. These changes are mundane, but they decide whether the QR serves the right person during the next viewing.

Keep the Viewing Details Current

A visit announcement has a short life. Confirm the date, start and end time, property status and contact before publishing a visit page. After the viewing, remove or revise temporary instructions. The stable property page may continue to show photos and contact while the listing remains active, but a “Visit today” label should not linger once the event ends.

Choose a different message for each printed surface. The street sign describes the property, not an event that happens only for two hours. The desk card can describe the day's optional form and property information. An agency that changes the form for every listing must test that the desk QR opens this listing's form rather than the previous open house.

Use VISU for the Public Route, Not the Register

The VISU Real Estate solution offers a property or agency page, links to details and contact, and QR artwork for signs and printed pieces. For an open house, that can be the public route to property information and an existing external form if the agency chooses to include one. The form provider and agency control the submission, its fields and follow-up.

If the agency needs one QR to open one public listing, it can use the listing URL directly. If visitors need a clear choice between property details and a separate form, a page can organise the two. Native visitor registration, check-in, identity verification, CRM sync or automated follow-up would be another project with its own scope and delivery terms. Do not infer those functions from the presence of a QR.

Run a Doorway Test Before Opening

1. Scan the street sign and desk card separately. Check that each promise matches the first screen.
2. Open the property page without a staff login and confirm the correct home, status and contact.
3. If offering a form, open its public URL and confirm which provider owns it and which agent receives submissions.
4. Read the form's visible message after submission in the provider's own test environment or documented preview, without creating a fake visitor in production.
5. Decide what the host will do if a guest has no connection or declines the form.
6. Name who will remove the temporary visit message after the event and retest the QR before the next one.

Ask for only the steps the agency can operate. The door card should make the visitor's next action obvious, not pretend that the page is a registration system.