Set the sign-in. Work the door. Keep the record.
An open house is not a moment, it is a week: the code goes up on Thursday, forty people walk through on Sunday, and on Monday the seller wants to know who they were. This runs all of it, and writes every visitor into your CRM as they sign in.
The code exists before the sign is in the yard.
You create the event against the listing rather than against a blank calendar, so the address, the photos and the property details are already attached. The QR code is generated the moment the event is saved, at one thousand pixels square, and stored on object storage. That resolution matters for one unglamorous reason: a code that was fine on a flyer turns to mush blown up to yard-sign size, and you find out on the Sunday morning.
What the event carries- The listing, the date, and the start and end time
- In person, virtual with a meeting link, or both at once
- Registration required, or an open door with sign-in optional
- An attendee cap, when the property has one
- Co-hosts, including a lender with their credentials shown
- A covered credit budget for guest room redesigns
- Whether the event is listed publicly or stays unlisted
A phone camera, no download, and a form that catches its own errors.
Visitors scan with the camera app they already have. The form checks the email address is a real shape, formats the phone number, enforces the fields you have marked required, and asks for consent to be contacted before it will submit. That is the whole difference between a sign-in sheet and a record: the clipboard cannot refuse a bad entry, and it cannot ask a follow-up question.
Anyone who will not use their phone still gets registered. Sign them in on your own tablet and the entry is marked a walk-in rather than an online registration, which keeps the source breakdown you show the seller honest.
Every registration carries its own cancellation link. A guest whose Sunday falls apart cancels from the confirmation email without messaging you, and your headcount corrects itself.
Cover a few design credits and the visit keeps going after the door shuts.
Turn on AI redesign for the event and set a covered credit limit, or leave it uncapped. Guests spend those credits reimagining rooms in your listing, and you can add a bonus for finishing the questionnaire. The credits come from your own balance, the cap is yours, and the spend is recorded against that specific event so you know what a Sunday actually cost.


The useful part is not the picture, it is the behaviour. Which rooms a visitor bothers to redesign, and whether they come back to do a second one, separates the neighbour who came for a look from the buyer who is furnishing the place in their head.
A registration is not a spreadsheet row waiting to be imported.
The moment someone signs in, four things happen without you. This is the stage most sign-in apps stop short of, and it is the one that decides whether Sunday turns into Monday work.
Five messages go out whether you remember them or not.
Confirmation
Thanks them, confirms the address and the time window, and carries a link that lets them cancel themselves if plans change.
Reminder
The one that reduces no-shows. Sent once per attendee and stamped, so a re-run of the schedule cannot send it twice.
Final reminder
For the visitor who meant to come and lost the afternoon.
Survey request
Four questions, on a single-use token. The answers land on the attendee record, not in your inbox.
Design follow-up
Goes to the guests who actually spent their credits on your rooms, which is the shortest list worth calling.
The sequence runs on the event, not on your memory of the event. Sends are stamped per attendee, so a reminder cannot go out twice to the same person, and a guest who registers an hour before the doors open is not sent a reminder for something that has already started.
Your side of it is notifications rather than work. You are told when someone registers, which you can switch off per event when a busy listing would fill your phone; when a survey comes back; and when a co-host accepts or declines an invitation. Co-host invitations and survey summaries are their own messages, so nobody has to be forwarded anything.
What you can actually tell the seller on Monday.
Attendance is the easy half. The half that changes what you do next is the survey, because it asks the one question a conversation at the door rarely gets a straight answer to.
- Registrations, verified check-ins, and who registered but never arrived
- Where each sign-in came from: online, walk-in, or referral
- Twelve months of history, so this spring is comparable with the last one
- Per-event totals alongside the average across every event you have run
- Survey responses grouped by the answers above, not as raw rows
How was the experience?
Interested in this property?
What is the next step?
Best way to reach you?
Read the third question first. It is the only field that sorts a Sunday afternoon into people who want a private showing and people who wanted to see the kitchen.
The same six stages, four other ways.
- Virtual and hybrid
- An event can be in person, virtual with a meeting link for Zoom, Teams or Webex, or both at once. Virtual attendees go through the same registration, get the same reminders, get the same survey, and can be given the same covered credits. A video tour can be embedded on the event page for anyone who cannot make the window at all.
- Three host roles
- Primary host, co-host, and mortgage consultant. The consultant role exists because a lender at an open house needs their title, company, license number and NMLS identifier shown, not a generic name badge. Co-hosts get full access to registrations and analytics once they accept, and they accept or decline by email with an optional note.
- Listed or unlisted
- Mark an event publicly findable and it appears in a location-based search with your agent profile attached, so a buyer already looking in the area can register from the results rather than needing your flyer. Radius is set by the person searching, in miles or kilometres. Leave the toggle off and the event is reachable only through your own code and link.
- On the API
- Events and their attendees are readable at
/api/v1/open-housesunder thelistings:open-houses:readscope, with a separate write scope for creating, editing and cancelling events. A brokerage system or a partner app can pull the attendee list directly instead of waiting on a spreadsheet.
Before you set one up.
Stage one takes about two minutes.
Pick the listing, set the window, print the code. The other five stages run whether you are standing at the door or driving to the next showing.
Create an open houseNo per-event fee, no per-attendee fee. Guest design credits are optional and capped by you.




