Managing Site-Visit Requests for Property Teams

A site-visit request is a different animal from a general property enquiry. The person has moved from browsing to wanting to stand inside the building. That intent is fragile. A visit that is never confirmed, or a follow-up that never comes after they walk the show flat, is a near-buyer lost for the sake of an admin step.

Take a residential developer with three active projects: a completed tower with ready units, a development still under construction, and a new launch selling off plan. Each has different show arrangements and a different sales team. The site-visit workflow has to hold all three without visits getting booked against the wrong project or nobody turning up to host.

Capture what the visit is actually for

A request that just says "I would like to visit" creates work for whoever picks it up. The details you need are specific, and worth asking for on the booking form rather than in a follow-up email.

• Which project the person wants to see
• The unit type or configuration they are interested in, for example a two-bed or a particular tier
• Their preferred date and a rough time
• Whether they have visited before, and whether an agent is already working with them
• How they found the project, so the channel gets the credit

With a dedicated form per project, embedded on that project's page, the request arrives already tagged to the right development and the right unit type. That is the difference between a lead the sales team can act on immediately and one they have to email back to clarify before anything can happen.

Not every request comes through the form

Plenty of site-visit requests arrive by phone, by a reply to a marketing email, or as a walk-in at one project asking about another. If those only live in the memory of whoever took them, they are the ones that get missed. The rule is that every request becomes a record the same way, whatever door it came in through, with the same few details captured.

For a phone or walk-in request, that means the person taking it enters the project, the unit type and the preferred date there and then, and it joins the same list as the web bookings. A request that is not written down in the same place as the others is a request that is not really in the system.

Confirm fast, and confirm properly

A booking request is not a booking. Until someone has replied with a date, a time, a place to meet and the name of the host, the visit does not really exist. The prospect is often waiting on that confirmation to arrange their day, and a slow reply reads as a team that will be slow about everything else too.

Confirmation should go out the same day and include the practicals: the exact meeting point, parking or access notes, what to bring if anything, and the name and number of the person hosting. Put those same details on the lead record, so any colleague can answer if the prospect calls back with a question. For an under-construction project, add whatever site-safety detail the visitor needs to know before they arrive.

Remind, because no-shows are mostly forgotten appointments

Most missed viewings are not cold feet, they are diary slips. A reminder the day before, and a short one on the morning itself, recovers a meaningful share of them. For an off-plan launch where the visit might be a week or two out, a mid-week nudge in between helps as well.

Keep the reminder personal and easy to answer. A line from the host saying they are looking forward to it, with the time and place repeated, gives the prospect a simple moment to say if something has changed. A rearranged appointment is far better than an empty slot and a wasted Saturday morning. If a visitor does not show and does not respond, that is not a dead lead either: one polite message offering another date recovers a fair share of them.

Log the visit outcome while it is fresh

The visit happens and the host learns a great deal: which unit the prospect gravitated to, what they compared it against, what gave them pause, whether a partner still needs to see it, what the realistic timeline is. If that goes into a quick record straight afterwards, the follow-up almost writes itself. If it stays in the host's head, it is gone by the next weekend of viewings.

1. Whether the visit happened, and who hosted it
2. Which units or configurations were shown, and which drew the most interest
3. Objections or blockers the prospect raised
4. The agreed next step and when it is due
5. A rough read on how close this buyer is

Follow up after the visit, on a plan

The days right after a visit are the warmest the lead will ever be. This is not the moment for a single "thanks for coming" email and then silence. A light sequence works: a same-day thank you with the specific unit details and pricing, a check-in a few days later to answer questions that surface once they have thought it over, and a clear next step such as a second viewing, a hold on a unit, or an introduction to the booking process.

If the answer is not now, find out why and when. A buyer waiting on a property sale or a loan approval is a real lead with a date attached, not a dead one. Schedule the next contact around their timeline and note the reason, so nobody has to reconstruct it in three months. A visitor who came with a partner who has not seen the unit is one specific follow-up: get the second person booked in.

See which projects and unit types pull visits

Because each request carries its project, unit type and source, over a quarter you can see which project is converting browsers into visitors, which unit configuration people actually ask to see, and which channel produces requests that turn up. If one project generates plenty of enquiries but few visit requests, the listing or the pricing is doing something the others are not.

That is a different question from how many leads each project has, and it is often more useful. A visit request is a much stronger signal than a form fill, so the pattern of requests is an early read on which project will sell out first.

Keep every visit visible to the team

Across three projects with different teams, the risk is that site visits live in individual inboxes and personal calendars. One person knows a viewing is booked for Saturday; the colleague covering that morning does not. Requests get double-booked, or hosted by someone with none of the context the prospect shared last week.

A shared view of upcoming visits, each linked to its lead with the project, unit type and history attached, keeps the whole team on the same page. In AliveCRM the site-visit request comes in through a per-project form as a lead, the follow-up before and after the visit sits as scheduled actions with reminders, the outcome goes on the record, and leads stay organised by project. The workflow is small, but it is exactly where property teams lose buyers who were ready to move.