A property enquiry and viewing pipeline needs to connect an applicant, a particular listing and a bookable appointment. The enquiry is not the viewing, and the viewing is not an offer. Keeping these records separate lets a negotiator handle several properties for one applicant without losing feedback, access instructions or follow-up ownership.
Start with the negotiator's morning queue
Imagine opening the CRM before the first viewing. The useful questions are concrete: which enquiries need a reply, which appointments lack confirmation, who has the keys, and which viewers still need a follow-up? A board showing only new, contacted and won cannot answer those questions without extra notes.
Design the queue around appointment readiness and applicant decisions. An enquiry waiting for a callback should not disappear because a viewing was provisionally pencilled in. Show the next action, responsible negotiator and due time, plus the property reference. Let staff switch between an applicant view and a property view without duplicating the conversation.
Use this workflow for enquiries and viewings. Sales progression, tenancy administration and financial checks have their own requirements and should be separate scope decisions. A first release can improve appointment coordination without attempting to replace every system in the agency.
Separate a physical property from its listing
Give the physical property a stable record, then represent a marketing instruction or listing separately. That allows a later listing to have a different asking price, availability date or responsible office without rewriting the earlier history. Connect the enquiry to the listing the applicant actually responded to.
Store applicant preferences such as location, budget range and desired timing on the applicant record, with a last-confirmed date. Keep property-specific questions on the enquiry. Someone asking about parking at one flat should not acquire a permanent profile note implying that every future enquiry concerns that same flat.
Capture the incoming source reference when available and preserve the original message. Match repeat enquiries cautiously. A shared email address or similar surname should prompt review where the identity is uncertain. If two messages refer to different properties, link both to the applicant while retaining separate enquiry records.
Appointment states should reflect real commitments
Use provisional, confirmed, completed, cancelled and no-show as appointment states if they fit the agency's process. A provisional slot needs an expiry or review time. Confirmation should require the necessary participant and access checks, rather than happen merely because a calendar entry exists.
Represent negotiator availability and property access as separate constraints. An available employee does not establish that the property can be entered. Record the access arrangement, its owner and whether it has been confirmed. Restrict sensitive access details to the staff who need them, and keep them out of generic reminder messages.
Decide whether overlapping viewings are allowed for a listing. An open viewing may intentionally include several applicants, whereas an individual appointment may reserve the property and negotiator exclusively. Model the open event and its attendees explicitly instead of disabling conflict checks across the entire calendar.
A viewing readiness checklist for the front desk
- Confirm the current listing status and that the appointment still makes sense.
- Check the applicant's contact details and the chosen confirmation channel.
- Assign the viewing host and account for travel or preparation time.
- Record the agreed access arrangement and who will resolve any uncertainty.
- Check for resource conflicts, including appointments created by another office.
- Prepare a follow-up task that becomes due after the viewing, with an owner.
Make the missing items visible beside the appointment. A general warning banner that requires opening several tabs is easy to overlook. Allow an authorised person to record a reason for an exception, but do not let that override hide the unresolved access question from the viewing host.
Feedback belongs to the viewing, not just the contact
After the appointment, record attendance and feedback separately. The applicant may attend but not yet have an opinion; the host may leave operational notes while the applicant's response is still pending. Distinguish those sources rather than combining them into one unattributed comment.
Create an offer or further-interest record when appropriate, linked to the listing and applicant. A second viewing can then be scheduled without overwriting the first. If the listing becomes unavailable, find affected future appointments and assign review tasks before sending any messages. Staff should confirm the next step rather than automatically recommending an unsuitable substitute.
Test a withdrawal between booking and attendance
In a fictional acceptance test, applicant Sam enquires about two flats and books a viewing for each. Two negotiators then try to reserve the same exclusive slot at the first flat. The system should accept one reservation and explain the conflict to the other user, without losing their enquiry.
Withdraw the second listing before its viewing. Expect a task to review that appointment, an accurate cancellation history and no attendance reminder after cancellation. The first viewing must remain intact. Record Sam attending it, requesting a second visit and changing their preferred moving date; verify that historical enquiry details still make sense.
Report enquiry response time, confirmed viewings, attendance and outstanding feedback as separate measures. Review these alongside cancellations by reason, so listing withdrawals are not mistaken for applicant no-shows. For another capacity-sensitive workflow, see event enquiry and booking coordination.
Explore Visuosofts CRM development with an anonymised enquiry and your current diary rules. Contact the team to map the booking constraints, access responsibilities and follow-up queue before specifying integrations.