A useful property enquiry workflow assigns one owner, confirms the property and the person's requirements, checks current availability and records the next agreed action. Before booking a viewing, pass a concise summary to the person conducting it. Fast replies help, but a quick answer about the wrong property is simply a faster way to create confusion.
Property teams receive enquiries through listings, forms, calls and messaging apps. Without a clear process, one person gets three replies while another waits unnoticed. This guide follows a lead from the first question to a useful viewing handover, with qualification prompts, duplicate checks and a practical ownership model.
Capture the enquiry and its source
Record the person's preferred contact method, the property reference and the actual question. Keep the source and time of the enquiry so the team can understand the context. A message saying “Is this still available?” needs a reliable link to the listing the person saw. Without it, staff may answer from a different advertisement or an older version.
Collect only the information needed for the current stage. A first enquiry rarely needs a large collection of personal documents. Explain how information will be used and follow the communication permissions and privacy requirements relevant to your operation. A well-organised workflow should reduce unnecessary copying of personal details across tools.
Give each conversation a clear owner
Assign the lead to a person or a clearly managed queue. Define who responds when the primary owner is unavailable and how the handover is recorded. Ownership should mean responsibility for the next action, not exclusive possession of a name in a database. The client should not have to understand your internal allocation system to receive a coherent reply.
Use a small set of states that reflect real progress: new enquiry, awaiting clarification, availability check, viewing proposed, viewing confirmed and follow-up. Add a next-action date rather than leaving a lead in an attractive but inactive column. A status without an owner and a next step is mostly decoration.
Check for duplicate enquiries before replying again
A person may enquire about several properties or contact the team through more than one channel. Search for an existing conversation using the information your system legitimately holds. Confirm a match before combining records, especially when names or contact details are shared. Two people with similar names are not automatically the same client.
Keep the property interests and conversation history distinguishable even when the person is the same. A new enquiry may reflect a changed budget, preferred area or move date. Do not assume the latest message is redundant. The purpose of duplicate checking is coordinated service, not deleting information that explains what the person wants now.
Ask enough questions to suggest a useful next step
Qualification should help the client and the team decide whether a property is relevant. Start with the intended use, preferred area, practical requirements, timing and an appropriate budget range. Ask in a conversational sequence rather than sending an intimidating questionnaire before answering the original question.
Distinguish essential requirements from preferences. A fixed accessibility need, move date or household requirement may determine suitability more strongly than a preferred finish. Avoid unnecessary sensitive questions or assumptions about a person's circumstances. Record the answers neutrally so another team member can use them without interpreting a collection of informal labels.
| Stage | Information needed | Completion check |
|---|---|---|
| First response | Property and original question | The person receives a relevant answer |
| Requirements | Timing, location and practical needs | Important constraints are understood |
| Availability | Current property status and access | A responsible source confirms it |
| Viewing proposal | Suitable times and contact route | Options are offered without implying confirmation |
| Confirmation | Agreed time, meeting point and host | Both sides know the arrangement |
Verify availability before promising a viewing
Check the current property record and the person responsible for access. An imported listing or old spreadsheet may be useful background, but it should not automatically be treated as current availability. Record when the status was last confirmed and by whom. This helps staff recognise when another check is needed.
Separate “viewing requested” from “viewing confirmed”. A client suggesting a time does not establish that the property can be accessed or that an agent is available. Confirm those details before sending a definitive message. Clear wording prevents a provisional conversation from becoming an accidental appointment.
Use messaging templates without sounding oblivious
A template can make a reply consistent, but it should include the actual property and answer the person's question. Review names, references and links before sending. Avoid asking for information the person has already provided. A client who has just explained their move date should not receive a cheerful request to explain their move date again.
Keep automated and human responsibilities clear. If an assistant provides general property information, define when a person must verify availability, negotiate details or resolve an unusual request. Do not let the assistant promise actions it cannot complete. A useful handoff says what is known and what requires confirmation rather than restarting the conversation.
Prepare a concise viewing handover
The person conducting the viewing needs the property, confirmed time, meeting arrangement and relevant requirements. Include the questions the client wants answered and any agreed practical arrangements. Keep private details limited to what the viewing host genuinely needs. A full conversation dump is often less useful than a careful summary with access to the underlying record.
- Client name and agreed contact route.
- Property reference and current availability confirmation.
- Confirmed date, time, meeting point and viewing host.
- Essential requirements and questions raised.
- Access arrangements and any agreed adjustments.
- Who records the outcome and handles the next contact.
Ask the receiving person to acknowledge the handover through the team's normal process. The goal is not another notification for its own sake. It is to establish that the person responsible for the appointment has the information needed to conduct it.
Worked example: one client, two channels
Imagine a fictional client enquiring through a listing form and then sending a WhatsApp message about the same apartment. The first enquiry goes to a central queue; the second reaches an individual agent. A duplicate check connects the conversations after the identity and property are confirmed, and one owner takes responsibility for the next response.
The client wants to view after work and needs to move within a specific period. The owner checks that the property remains available and that access can be arranged. They offer two provisional times, confirm the chosen slot with the viewing host and send a clear meeting instruction. The host receives a short summary of the client's requirements and questions.
After the viewing, the host records the outcome in the same lead record. The client receives one relevant follow-up instead of two agents independently asking how it went. The improvement comes from ownership and a shared record, not from sending more messages.
Follow up with a reason
After a viewing, ask what the person thought and what information would help the decision. If the property is unsuitable, record the reason accurately and ask whether they want to consider alternatives. Do not interpret every pause as a request for an increasingly frequent sequence of reminders.
Agree the next contact where possible and respect communication preferences. A useful follow-up might answer a specific question, provide a confirmed update or suggest a genuinely relevant alternative. “Just checking again” repeated indefinitely creates work without necessarily creating value. Close or pause inactive enquiries according to a clear process rather than leaving them permanently active.
Measure coordination, not just response speed
Track whether new enquiries have owners, whether next actions are overdue and how often viewings fail because of avoidable information gaps. Response time can be useful, but it does not describe answer quality or suitability. A very fast generic response may be less helpful than a slightly later answer that resolves the actual question.
Review a small sample of conversations regularly. Look for repeated requests for the same information, unconfirmed promises and confusing handovers. Fix the underlying process or source data. If staff constantly need to ask whether a listing is current, improving availability records may help more than writing another response template.
Keep property and contact data maintainable
Give property records consistent identifiers and document how imports are matched to existing listings. Review duplicates and stale entries before they become client-facing confusion. Preserve useful source references so a team member can understand where a detail came from and whether it still needs confirmation.
Review access when staff roles change, and keep the system's actual capabilities clear. A CRM can organise information, but it does not make an unverified listing true. People remain responsible for the accuracy of the claims they make and the appointments they confirm.
Frequently asked questions
Should every enquiry receive the same qualification form?
No. Ask what is needed to answer the question and identify a useful next step. A short initial enquiry may need only a few clarifications, while a later discussion can cover more detail.
Can an AI assistant confirm every viewing?
Only if the actual configured system supports the necessary checks and authorised action. Otherwise, it should collect the request and hand it to a person for confirmation without implying the booking is complete.
When should duplicate records be combined?
After confirming they refer to the same person and preserving the relevant property interests and history. Similar names alone are insufficient. Keep an understandable record of the merge or correction.
How can LeadProps support this?
Use LeadProps to organise property and enquiry information within its available tools. Pair the workflow with the property data quality guide and WhatsApp enquiry guide, and verify which integrations are configured for your workspace.