A valuation enquiry often arrives as a short message: what could I get for my house? That question leaves several decisions open. The person may want to sell, refinance, review a portfolio, or simply understand the market. They may be an owner, a tenant forwarding a request, or someone acting for another person. A follow-up process should clarify the request before generating confident price language.
AI can help turn replies into a consistent appointment brief. It should not promise a sale price or treat an owner's expectation as a professional valuation. The proposed workflow here covers intake, follow-up and appointment preparation. The agency's qualified decision-maker retains the judgement about value, service scope and what can be represented to the customer.
Start with the purpose and the person making the request
Ask what the person wants the appointment to achieve. Use a short, understandable choice such as a potential sale discussion or an agent visit to assess the property. If the request calls for a formal report or a purpose the agency does not provide, route it to the responsible person rather than making an automatic service promise.
Collect the property address and an agency reference if one exists. Keep the original address alongside any proposed standardisation. A sectional unit, street number and estate name are not interchangeable identifiers. If the message mentions two properties, create two proposed briefs instead of blending their facts.
Record the relationship the requester states they have to the property and who should coordinate access. This is a statement to verify as appropriate, not proof of authority. Ask only for information needed at this stage. An administrative enquiry should not expand into a demand for unrelated financial or identity documents because a model thinks they could be useful.
Collect facts without turning expectations into conclusions
Separate property facts, customer statements and questions for the agent. Bedrooms, bathrooms, parking, recent alterations and known access constraints are useful topics, but every answer should retain its source. An owner-reported bedroom count can be marked owner stated until accepted into the agency's approved record.
If the person says a neighbour sold for R2 million, record that as an unverified statement with the property context they supplied. Do not transform it into a comparable sale or a likely value. If they say they need at least a particular price, label it a stated expectation, not an achievable outcome. Neither statement authorises the workflow to calculate or communicate a valuation.
Source: OpenAI Structured Outputs describes responses constrained by a supplied schema. Fields such as stated purpose, reported facts, unresolved questions and price expectation can keep these categories separate. The schema does not establish that the person's statements are true. A required field can contain an explicit unknown rather than an invented answer.
Ask for availability while keeping access separate
Ask for preferred windows, relevant timezone, access contact and any notice or building-entry requirements. The person may be available on Tuesday afternoon while the tenant can only permit access on Thursday. Those are different constraints. Do not offer a confirmed time until the agent has resolved all required participants and access conditions.
Source: Microsoft Graph calendar resource documents calendar events, calendar views and free/busy operations. These are scheduling building blocks. A calendar showing a free agent does not show that a tenant agreed to entry, that travel is feasible, or that the agency accepted the requested service.
Define proposed states such as intake incomplete, ready for agent review, appointment proposed and appointment confirmed. Only an accepted agent decision and verified booking record should lead to the last state. If a booking operation returns an uncertain result, staff check the record before sending another invitation or trying a second booking.
Reusable valuation appointment brief and follow-up
Complete this proposed brief before asking the agent to accept an appointment. It can be a structured record or a document; the fields matter more than its appearance.
| Section | Required content | Explicit limit |
|---|---|---|
| Request identity | Enquiry ID, requester contact and property reference | Contact identity and authority remain subject to agency checks |
| Purpose | Customer's stated reason and requested service | Do not promise a formal valuation service without acceptance |
| Property facts | Reported rooms, features, alterations and source of each | Unverified statements stay labelled |
| Existing record | Approved property record ID and version, if available | Differences become questions for the agent |
| Price statements | Exact stated expectation and any claimed comparables | No suggested value or guaranteed sale price |
| Access | Coordinator, participant constraints, notice and entry requirements | Preference is not permission |
| Scheduling | Proposed windows, timezone and agent availability check | No confirmed appointment before final checks |
| Outstanding questions | Missing details, conflicts and responsible person | Unknown values remain visible |
| Agent decision | Accept scope, ask for information, decline or redirect | Record the exact service and booking decision |
A reusable follow-up message is:
“Thank you for your valuation enquiry about [property reference]. To prepare the agent's appointment brief, could you confirm [specific missing fact], your preferred visit windows and who will coordinate access? We have recorded [price expectation] as your stated expectation, where provided. The agent will discuss the assessment and any pricing opinion after reviewing the property and the purpose of your request. Your appointment is not confirmed yet; we will send confirmation after the agent verifies the arrangements.”
Remove the price-expectation sentence if none was provided. Replace placeholders only with verified intake values. Do not send a message containing unresolved placeholders. The completion check is that the agent can identify the property, purpose, access route, unresolved facts and exact appointment state without interpreting a long message thread.
Compare a straightforward enquiry with an incomplete one
In a hypothetical normal case, Lerato asks for a potential-sale discussion about property V-18. She reports three bedrooms, states that she coordinates access, and provides two afternoon windows. The existing approved record agrees with the room count. The workflow creates a brief, labels her selling purpose and records the access statement. The agent checks the service scope, confirms the access arrangements and chooses an available slot. The confirmation refers to that recorded appointment and does not include a price prediction.
Now consider a hypothetical message from someone requesting a valuation of their sister's flat. They give the estate name but no unit number and say the tenant is usually home. The workflow asks for the unit reference and access coordinator. It does not book a visit to an assumed address or infer permission from likely occupancy. The agent sees the missing authority and access information as questions to resolve.
A repeated enquiry with the same stable enquiry identifier should update the existing intake history rather than create two appointments. Similar names or addresses alone do not establish a duplicate. Where one person has two units, staff should retain both property identities. If a later message changes the requested purpose, the brief returns to service-scope review; an earlier agent acceptance does not automatically cover a different job.
Give the agent a bounded approval decision
Keep approval of the brief, booking and price communication distinct. An agent can accept the intake while leaving access incomplete. They can approve the appointment while withholding any pricing opinion. A workflow that uses one global approved field can conceal those differences and create an inappropriate follow-up.
Source: n8n human review documents approval or denial before selected agent tools execute. It can support a review boundary for an external message or booking action when configured appropriately. It does not supply estate-agency authority checks or determine the professional significance of a valuation request. Those decisions require the agency's own process and responsible people.
Evaluate the intake pilot using missing facts identified, incorrect property matches, unsupported price language and appointment-state errors. Review whether follow-up questions were necessary and understandable. A large number of completed briefs is not useful if agents must reconstruct the original request or customers believe a tentative visit is confirmed.
Common questions about valuation follow-up
Can the assistant give a broad price range while collecting details?
This intake workflow should not. A range can still sound like a professional opinion or sale promise, especially when based on limited facts. Record the customer's expectation and refer pricing questions to the agent's accepted service. If the agency separately offers a price-estimation tool, it needs its own verified data, limitations and approval process.
What if the owner wants an appointment immediately?
Collect the minimum property and access information, then send the request to the agent with urgency clearly stated. Urgency does not establish availability or permission. Staff may arrange a quicker check through their usual process, but the message should continue to describe the appointment as proposed until the required checks are complete.
How much follow-up is appropriate when the person stops replying?
Use the agency's approved contact purpose and follow-up policy, with an easy way to stop further contact. The workflow should identify the unanswered question rather than send a generic sales chase. If the contact route or consent status is unclear, staff resolve that before another message. Do not invent a universal reminder cadence from the documentation.
If your business needs help defining this process, explore AI agents for estate agencies, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.