USE CASE
Property viewing request forms
A property enquiry lands as three lines in a DM: interested, when can I see it. The agent spends two replies working out whether it is a buyer, a seller, or a tyre-kicker, and by then the hot lead has booked with someone faster.
Buyers and sellers need opposite questions, yet the same request form asks both for a budget and a listing, so half of every submission is blank and none of it routes itself.
LIVE DEMO · READ-ONLY
Try it right here — this is the real thing.
The Property Viewing Requesttemplate, live. Flip between page and guided mode — it’s a preview, so nothing you enter is recorded.
Question 1 of 7. Your name. Read-only preview — nothing is recorded.
Your name *
WHAT MAKES IT WORK
The parts that carry this use case
STEP BY STEP
How you’d run it in FormNest
- 01
Open with intent, one question at a time
The guided flow leads with a single buying-or-selling choice on its own screen — the answer that decides everything downstream — so a lead on a phone commits before the form asks for anything harder.
- 02
Branch the questions on that answer
A buyer is asked for a budget and the property type they are hunting; a seller skips both and is asked about the home they are listing — the same form, two qualifying paths, no dead fields.
- 03
Pin a viewing date while the interest is hot
The preferred-date field books the viewing inside the same request, so the lead names a slot in the moment instead of starting an email thread that cools for a day.
- 04
Route the qualified lead to the right agent
With intent, budget, and property type captured, the real-estate lead-routing sends each request to the agent who covers that type and area — so it lands with the person who can actually book it.