Most chatbot implementations treat every website visitor the same. Someone asking about a property to buy and someone asking for a market appraisal both receive the same opening message, the same sequence of questions, and the same outcome: a callback request captured in a CRM with minimal context.
For buyers, this is a missed opportunity. For vendors, it is a conversion problem. A vendor who comes to your website thinking about selling their home and encounters a generic script, one clearly built around buyer enquiries, will either abandon the conversation or fill in the minimum required fields and expect nothing useful in return.
The qualification job for a vendor is fundamentally different from the one for a buyer. Understanding that difference is the starting point for building a conversation flow that actually converts valuation enquiries into booked market appraisals.
What buyers need from a qualification conversation
A buyer qualification conversation is designed to establish financial readiness and property intent. The core questions are whether the buyer has a mortgage in principle, their chain position, their budget and preferred location, their timeline, and, for first-time buyers, which purchase schemes they might be eligible for.
The goal is to establish whether this buyer can actually proceed on a property and within what timeframe. A buyer who has their DIP, is chain-free, and wants to move within three months is immediately prioritised. A buyer who hasn't spoken to a lender goes into a nurture sequence with a mortgage advice recommendation first.
The primary scoring dimension is financial readiness. Everything else, area preference, property type, specific requirements, is important context but secondary to "can they buy?"
What vendors need from a qualification conversation
A vendor qualification conversation is solving a completely different problem. The vendor is not in a financial readiness conversation, they're in an instruction decision. The questions that matter for a vendor are:
- What is the property address and postcode? (The commitment signal, a vendor who provides this has crossed from curiosity to intent.)
- Do they want to sell or let?
- What type of property is it?
- What is their timeline to go to market, actively planning now, in a few months, or just exploring?
- What is driving the move?
- Are other agents already booked to value? (The competitive intelligence question, unique to vendor qualification.)
- Do they have a price expectation? (Optional, but surfaces expectation gaps before the appointment.)
The goal here is not financial readiness but instruction readiness. And the competitive context, whether other agents are already in the picture, is a signal that simply doesn't exist in a buyer qualification conversation.
Why generic scripts fail vendors
The average generic chatbot script for an estate agency website is built around buyer enquiry patterns. It asks about mortgage status, viewing availability, and budget range. When a vendor starts a conversation, they hit questions that don't apply to them, "Do you have a mortgage in principle?", and either abandon the flow or push through and receive a callback prompt that treats them the same as a buyer who just wants to book a viewing.
Neither outcome serves the vendor. And it doesn't serve the agency either, a vendor who abandons the chat will simply contact a different agent whose website handles their enquiry correctly.
The fix is straightforward: detect intent from the first message and branch to the appropriate qualification flow. A visitor who says "I'm thinking of selling my house" or "Can I get a valuation?" should immediately enter a vendor-specific conversation, not a generic one that will ask them about their mortgage status.
The intent branching moment: A well-designed AI assistant detects vendor intent from the first message and routes to a separate qualification flow before any generic questions are asked. The visitor never has to specify "I'm a vendor, not a buyer", the conversation adapts to what they're saying from the start.
A vendor-specific scoring rubric
Once the qualification signals are captured from a vendor, scoring uses different weights from a buyer rubric. For buyers, financial readiness, DIP, chain position, dominates the score. For vendors, the key dimensions are:
- Timeline: Actively planning to list now scores highest. "Just exploring" scores lowest. Timeline is the best single predictor of how soon an instruction will be awarded and how urgently you need to respond.
- Motivation: Concrete motivations, school deadline, property to buy already found, probate, relocation, indicate a vendor who will proceed. Vague motivations indicate lower urgency.
- Competitive position: No other agents yet contacted is the best position, this vendor enquiry is yours to win. Multiple agents already booked signals a more competitive situation requiring faster response and first-appointment priority.
- Address provided: Vendors who provide an address have crossed a meaningful threshold. Those who don't are still browsing rather than planning.
A vendor who is actively planning to list, has a concrete motivation, hasn't contacted any other agents yet, and has provided their address is a Priority A lead who should be contacted immediately. A vendor who is exploring values six months in the future and hasn't provided an address goes into a nurture sequence.
For a full breakdown of the scoring rubric and how to use it in practice, see the guide to qualifying valuation and vendor leads.
What lead-type branching looks like in practice
In Sift, intent detection is built into the core of the conversation engine. When a visitor starts a chat, the assistant identifies from the first message whether they're looking to buy, rent, or get a market appraisal. Each branch runs the appropriate qualification flow, different questions, different scoring weights, different outcomes.
For vendor and landlord enquiries, Sift's valuation qualification captures address and postcode, sell-or-let intent, property type, timeline, motivation, and competitive status. It then scores on the vendor rubric, not the buyer rubric, and books the market appraisal. Your team receives a qualified vendor summary before the first callback, with context about timeline, motivation, and how many other agents the vendor is already seeing.
Sift never provides an instant online valuation figure. The job of the qualification flow is to win the appointment; the number comes from your valuer at the property. What the AI layer provides is a pre-qualified, pre-scored lead so the morning callback starts from a position of knowledge rather than cold outreach.
For the broader picture of how one assistant handles all three lead types, buyer, tenant, and vendor, without separate tools, see sales, lettings and valuations from a single AI assistant. And for the out-of-hours dimension, where vendor qualification matters most, read why agencies lose instructions overnight.
The test: Open your current chatbot or chat widget and type "I'm thinking of selling my house, can I get a valuation?" Watch what happens. Does it ask buyer questions? Does it route to a generic callback form? The answer tells you whether your front door is set up for vendor enquiries or only for buyer enquiries.
