Conversa vs generic real-estate chatbots: lead generation is not buyer qualification
The short answer
Lead generation creates a contact or starts a conversation. Lead qualification asks relevant questions, evaluates the answers against defined criteria, records an explicit status and routes the person to a useful next step. A portal form, website chat or click-to-WhatsApp ad can create an enquiry without proving that qualification happened.
That distinction is about implementation, not about whether a product uses AI. Current general-purpose platforms can qualify leads, book meetings and hand conversations to people when configured to do so. For example, HubSpot documents website chatflows that ask questions, qualify leads, book meetings and collect initial information before a teammate takes over. Intercom documents a configured Sales role that can guide discovery, qualify leads and book meetings.
The useful buying question is not “Does it have a chatbot?” It is “What does the system know, what criteria does it apply, what status does it record, and what happens next?”
Where the property workflow actually begins
A property enquiry normally arrives with some context: a listing, a message, a source, contact details and a timestamp. That is an inbound contact, not automatically a qualified buyer. idealista/tools' own Inbox documentation separates the received contact from the later work of reviewing the message, adding notes, assigning the contact, creating a demand record, proposing a viewing or continuing on WhatsApp or by phone.
The distinction is even clearer in idealista's rental documentation. A record with household, move-date, income and occupation data is described as pre-qualified, with the agent still deciding whether to continue qualification or discard it. That rental-specific example should not be generalized to every portal or sales enquiry, but it illustrates the operational gap between “contact received” and “fit assessed.”
Five categories, one evaluation standard
The matrix applies the same criteria to every category. “Not established” does not mean a tool cannot do something; it means the cited official source does not establish that capability for this real-estate workflow. Vendor documentation establishes what a vendor says its product supports, not comparative effectiveness.
| Category | Intended buyer/job | Inbound source | WhatsApp channel/transport | Property grounding | Qualification depth | Routing | Viewing/calendar | Human handoff | Languages | Privacy/data boundary | Pricing transparency | Evidence available here |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Portal inbox / CRM intake | Agency teams managing contacts attached to listings. | Portal contact; some systems can also ingest lead emails. | May let the team continue on WhatsApp; automation and transport are separate questions. | Strong listing/source context in the contact record. | Contact management and prioritization; qualification still requires criteria and follow-up. | Assignment to an agent can be supported. | Viewing proposals or recorded activities may be supported. | The inbox is operated by the agency team. | Translation may be supported; verify the exact workflow. | Ask what portal and CRM data is retained, shared and exported. | Check the portal's current commercial terms. | idealista/tools official Inbox documentation. |
| Click-to-WhatsApp entry surface | Advertisers that want a person to start a business chat. | A Facebook or Instagram ad, profile or other supported entry point. | Opens a WhatsApp conversation; downstream handling is a separate system. | Not established by the entry surface. | Not established by a click or conversation-start metric. | Requires downstream questions, rules and ownership. | Requires a downstream booking or human process. | Requires a defined owner and escalation path. | Depends on the downstream conversation flow. | Disclose the demo purpose and define consent, retention and access. | Ad spend and downstream product costs are separate. | WhatsApp Help Center: ads that lead to a WhatsApp chat. A reported conversation start is not, by itself, a qualified agency conversation. |
| Rule-based website chatflow | Website teams collecting information, routing visitors or booking meetings. | A visitor starts in a website widget. | The cited implementation is a website chatflow, not a portal-email-to-WhatsApp flow. | Depends on connected data, actions and configuration. | Can ask questions, store properties and branch; depth depends on the criteria. | Can route, trigger workflows/webhooks or send to a teammate. | Can share a meeting link; that is not proof of a valid property viewing. | Can collect information before a team member takes over. | Configured per chatflow; verify each published language. | Review property storage, contact properties, consent and data-processing terms. | Capabilities can depend on plan, seats and permissions. | HubSpot official setup guide and official action reference. |
| General AI customer agent | Customer-experience, support or sales teams, depending on configured role. | Messages on selected channels and audiences. | Some platforms support WhatsApp when configured; exact connection and ownership still need review. | Can answer from selected knowledge or connected data; property-specific grounding is not inherent. | Can qualify when criteria and a sales role are configured. | Can route according to configured outcomes. | Can book meetings; property-viewing validity remains implementation-specific. | Can escalate or hand off under configured rules. | Varies by platform, channel and configured content. | Review every connected source, access rule, retention term and processor. | Check current platform, usage and outcome charges. | Intercom's official role description, outcome definitions and knowledge-source guide. |
| Conversa current launch scope | Demand-rich, operations-constrained real-estate agencies that already receive buyer enquiries. This is the current ICP hypothesis, not proven market segmentation. | The designed journey starts with an existing portal, site or email property enquiry. | The current first-party description is linked-device transport, not an official WhatsApp Business API claim. | Designed around approved property context and the enquiry's listing/source. | Designed to ask about buyer need, budget, timing, financing, area and fit without inventing a rigid volume threshold. | Designed to route to the relevant next step or a person. | Designed to prepare a valid viewing progression; configured rules and human judgment determine confirmation. | A visible handoff path is part of the current promise. | Current first-party scope: Spanish, English and Arabic. | Buyers should review the data boundary; implementation-specific roles and retention still require agreement. | Review the current pricing page and the exact implementation terms together. | First-party product, features and evidence/methodology pages, plus an open demo. These are not independent customer proof. |
Why “generic chatbot” is not a useful verdict
A rule-based chatflow can ask meaningful questions. A general AI customer agent can use knowledge sources, qualify against defined criteria and hand off. A portal inbox can preserve stronger property context than a standalone chat widget. The label does not decide quality; the configuration, source data, outcome model and operating owner do.
This is why the comparison does not claim that Conversa has capabilities other platforms can never reproduce. Conversa's proposed distinction is a narrower starting point: the current offer is shaped around one real-estate journey—portal/site/email enquiry → WhatsApp → buyer-needs qualification → valid viewing progression or human handoff—rather than around generic demand generation or general customer support.
What Conversa is for in this phase
SME Analytica currently positions Conversa as an AI WhatsApp assistant for real-estate agencies. The target problem is an agency that already receives enough buyer enquiries to create backlog, inconsistent coverage or weak progression. The current offer is not “get more property leads.” It is “handle the buyer enquiries you already have with a defined qualification and handoff path.”
Seller or listing acquisition may exist as a separate or future capability, but it is deferred and unlaunched in this phase. This article does not promise that capability or a launch date, and it excludes seller acquisition from the current demo, schema, ad message and buyer checklist.
The evidence page explains what SME Analytica has measured, the limits on those measurements, and what is not customer-endorsed or independently reproduced. A locally rendered page, a working demo and a company measurement are different evidence tiers.
Who Conversa is not for
- An agency whose main problem is generating new seller/listing demand rather than handling existing buyer enquiries.
- An agency with very little inbound buyer demand and no recurring coverage or qualification problem.
- A buyer that requires an official WhatsApp Business API implementation today; Conversa's current page describes linked-device transport.
- A team looking for a fully autonomous system with no named human owner, judgment boundary or escalation path.
- A buyer requiring guaranteed conversion, guaranteed viewings, guaranteed response times, market leadership or independently verified customer proof.
A buyer checklist for any tool
- Name the job. Is the tool creating demand, capturing contact details, answering questions, qualifying an existing buyer or progressing a sale?
- Bring one real enquiry. Test with the listing, source and wording buyers actually use.
- Inspect grounding. Ask where price, availability, location, features and restrictions come from.
- Define qualification. Write the criteria, questions, statuses and disqualification path before judging the interface.
- Separate contact from outcome. A click, form fill or conversation start is not a qualified buyer.
- Test uncertainty. Ask about missing or contradictory property information and watch whether the system invents or hands off.
- Trace routing. Confirm who receives the conversation, with what context, and how quickly the owner sees it.
- Validate the viewing. A calendar link is not enough; check availability, confirmation, property match and owner rules.
- Review languages end to end. Test buyer messages, generated replies, handoff and operator UI in each claimed language.
- Review transport and data. Ask who controls the WhatsApp number, how it connects, what is stored, for how long and who can access it.
- Price the whole workflow. Include setup, subscription, usage, messaging, integration and human follow-up costs.
- Grade the evidence. Keep vendor documentation, a controlled demo, company measurement, customer endorsement and independent proof separate.
How to evaluate Conversa without treating the demo as proof
You can open the Conversa WhatsApp demo and act like a buyer. Try a normal property question, change your requirements, ask for something the sample property does not establish, request a viewing, and ask for a person. The demo can show the interaction design; it cannot prove your production integration, your team's follow-up, customer outcomes or market-wide performance.
For implementation details, read the feature and transport boundaries. For claim definitions and limitations, read the evidence methodology. If the current offer does not fit, use the correction/contact route rather than forcing the workflow into a generic lead-generation promise.
Market-specific buyer guides
Portal delivery, channel expectations and buyer questions differ by market. Read the source-linked guides for Spain, UK estate agencies or UAE real-estate agencies, then use the cross-market due-diligence checklist. These are first-party evaluation guides, not claims that Conversa is launched, integrated or customer-proven in every market.
Sources and editorial boundary
- idealista/tools: Inbox, updated 5 June 2026.
- idealista/tools: qualified-profile contact, updated 2 March 2026; rental-specific.
- HubSpot: create a rule-based chatbot, updated 12 June 2026.
- HubSpot: rule-based chatbot actions, updated 19 August 2026.
- Intercom: What is Fin?, dated 9 June 2026.
- Intercom: Fin AI Agent outcomes, update date not stably exposed.
- Intercom: knowledge sources, current when checked.
- WhatsApp Help Center: ads that lead to a WhatsApp chat, publication date not exposed.
All external sources are first-party product documentation. They support the specific capability descriptions linked above, not a conclusion about which product performs better. SME Analytica will correct this page when a cited capability, date or Conversa boundary changes.