Separate a property requirement from a listing commitment
A property enquiry is useful when it preserves the location, unit type, budget and timing the agent needs to shortlist. Do not turn an old listing into a promise about possession, availability or ownership. Keep listing knowledge dated and remove withdrawn properties. A request for legal assurance needs the appropriate professional, not an invented chat answer.
Five problems and the response to design
Use these as design tasks to test with your actual business knowledge. The assistant cannot create missing operational information or make an approval decision simply because a visitor requests one.
- Budget enquiries lack a locality. Ask for budget and preferred neighbourhood.
- Outdated listings imply availability. Use dated approved listings and have an agent confirm availability.
- Residential and commercial requests mix. Let visitors choose buying, renting or commercial space.
- Site visits lack a callback time. Record a preferred visit day as an unconfirmed request.
- Agents repeat discovery questions. Summarise the requirement for the agent.
A sample conversation to adapt
Replace example services and locations with your approved details. This is a conversation design, not proof of a live booking or third-party connection. Keep the confirmation wording visible.
Visitor: A two-bedroom flat near my office. Assistant: Buying or renting, and which locality? Assistant: What budget range and move-in date should the agent consider? Assistant: May an agent contact you? Property availability and visits require confirmation.
Qualification questions that earn their place
Ask only the questions needed for the visitor requested action. A straightforward information answer may need no contact details. Explain the purpose of a callback request and make optional questions easy to skip.
- Buying or renting?
- Preferred locality and unit size?
- Budget range?
- Expected move-in date?
- May an agent contact you?
Test difficult enquiries before publishing
Test a visitor who changes from renting to buying, an unavailable property and a request for title guarantees. The saved brief should reflect the latest requirement and identify what the agent still needs to check.
Include a short message, a change of mind and a question outside the supplied knowledge. Inspect the saved summary as well as the reply. The receiving staff member should understand the request, missing facts and whether the visitor actually asked for contact.
Launch with a person responsible for each enquiry
Start on a relevant service page. Add approved business information and check the widget on a phone and desktop. Submit one test enquiry and inspect it in the workspace, then define who will reply and what response expectation the business can meet. Automated replies do not establish a staffed response-time guarantee.
Keep the telephone or form route available for people who prefer it. Update instructions when hours, prices, services or policies change, removing withdrawn knowledge instead of leaving conflicting answers. Check the mobile contact prompt without covering essential page controls.
Measure a useful brief rather than a busy chat window
Distinguish a question answered, contact requested, request confirmed and transaction completed. They are different events. Review whether the collected brief gave the staff member enough accurate context for the requested next step. Conversation count alone does not show customer acquisition.
Review a small dated sample of appropriately handled real enquiries. Repeated missing questions indicate a knowledge gap; abandoned contact prompts may indicate the request came too early. Improve one issue at a time and avoid fictional leads or outcomes in analytics.