A complete site-visit workflow captures the enquiry, plans the appointment, records whether the visit happened, collects useful feedback and assigns the next action. Keep the property or project context attached throughout.
Capture the enquiry before arranging the visit
Record who is interested, how to contact them, which project or property they asked about and the person responsible for the relationship. Budget, location, property preference and buying timeframe help the team prepare a relevant conversation. Keep the original enquiry source so marketing and sales can understand how the opportunity began.
Use consistent project and unit identifiers where those records are part of the implementation. A property description copied into several messages is harder to follow than a linked record with clear ownership.
Move from appointment to outcome
Plan the visit
Agree the property, date, time, contact person and visit owner. Record changes against the same enquiry.
Prepare the handoff
Make the relevant requirements, prior conversations and appointment details available to the person meeting the buyer.
Record what happened
Distinguish completed, rescheduled and cancelled visits. Capture feedback instead of marking every scheduled visit as successful.
Set the next action
Arrange another visit, share suitable information or agree a follow-up date. Name the owner and keep the customer’s preference visible.
What belongs in a visit-outcome record?
A positive visit is not the same as a booking, payment or possession. Keep those stages distinct and record the supporting information when the process reaches them.
| Information | Why it matters |
|---|---|
| Visit status and date | Separates an actual completed visit from a booking or reschedule. |
| Property or project | Keeps feedback attached to the correct opportunity. |
| Buyer feedback | Captures fit, questions, concerns and preferences in the customer’s context. |
| Next action, date and owner | Makes the follow-up practical and accountable. |
| Related activity | Keeps the conversation visible alongside the enquiry history. |
Try the OWY site-visit example
The OWY website includes a sample real estate journey so you can explore a visit and its next step in a CRM-style screen. It is a browser demonstration using sample information; it does not book a real appointment, send a WhatsApp message or update a production CRM.
Use the example to decide which fields and decisions matter for your business. In a guided product demonstration, confirm the configuration for projects, units, brokers, visit ownership and the follow-up stages you need.
Questions worth asking
What is the difference between a site visit and its outcome?
The site visit records the appointment and whether it happened. The outcome records the buyer’s response, open questions and agreed next action. Both should stay connected to the enquiry and property.
Should a site visit automatically become a booking?
No. A completed visit and a confirmed booking are different business events. Keep separate stages and require the relevant information for each.
Does the OWY website demo create a real property booking?
No. The site-visit demo is illustrative and stays in the website experience. Use a product walkthrough to confirm the live configuration for your organization.
AI Business Platform