An enquiry is easy to lose when the message sits in one channel, the property context in another, and the next action only in an agent’s memory. MLS RealtyHub turns supported incoming property enquiries into structured working records, retaining the details provided with the request so the property author can review the person behind the interest and decide what to do next.
The real cost of an incomplete enquiry
A name and phone number are not enough if nobody can tell which property prompted the contact or where the request came from. The agent has to reconstruct the story before responding, and the same problem returns when the enquiry is handed to a colleague or revisited later.
Automatic lead creation and profiling keeps that first layer of context attached to the record. Instead of beginning with an unidentified message, the user begins with an organised enquiry connected to its origin and relevant property or property segment.
What the feature does at the moment interest arrives
This live MLS RealtyHub feature captures an incoming request through a supported enquiry flow and creates a structured record for follow-up. Customisable forms collect basic information supplied by the enquirer and preserve it with the source of the request.
The initial record can include:
- name;
- phone number;
- email address;
- enquiry source;
- connection to a specific property or property segment.
Only details that were provided can be stored. If a person leaves no email address, for example, the feature does not invent or infer one.
How an enquiry becomes a lead you can work with
The workflow separates automatic capture from the professional decision to continue. That distinction matters because a new request is evidence of interest, not proof that the person is qualified or ready to proceed.
- A person sends an enquiry connected to a property through a supported channel.
- MLS RealtyHub records the request and associates the available contact details, source and property context with it.
- The system groups activity at two useful levels: the individual enquiry and the Guest who may have submitted one or more enquiries.
- The property author reviews the captured information and profiles the interest.
- When the user decides to take that person into active work, the Guest can be converted into a Lead or Client record.
- The user can then continue in the wider CRM workflow with the relevant lead card, comments, tasks and pipeline steps.
The result is not a completed sales process. It is a usable starting record that preserves why the person made contact and gives the responsible professional a clearer basis for the next action.
Automation handles capture while the user keeps the decision
MLS RealtyHub automates the repetitive part: receiving the enquiry, retaining the supplied details and connecting the request to its source and property context. The user remains responsible for reviewing the record, deciding whether the interest should become an active lead and choosing the appropriate follow-up.
This division protects the difference between activity and qualification. The system can organise what arrived, but it does not predict conversion, judge whether a prospect is commercially attractive or replace the agent’s conversation with the person.
A property enquiry from first contact to next action
Consider an agent who has published a property and receives a request about it through a supported flow. The form contains the enquirer’s name, phone number and email address. MLS RealtyHub records those details together with the source and the link to the property, so the agent does not have to copy the contact into a blank record and then search for the listing that triggered the message.
The agent reviews the enquiry and sees that the same Guest has also asked about another property. That context helps the agent decide whether to take the person into active work. If the agent proceeds, the Guest is converted into a Lead or Client, and the next call or task can be managed in the CRM and Lead Management module. This example illustrates one possible workflow without promising the same outcome for every enquiry.
The same structure works for developer enquiries
A sales user representing a development can receive interest linked to a project, unit or relevant segment through a supported intake flow. The initial profile keeps the available contact information and source beside that context, allowing the responsible user to review the request before moving it into active lead work.
MLS RealtyHub does not act as the seller, broker or intermediary. It passes the enquiry to the author responsible for the property so that the professional can communicate with the potential client directly.
Why the distinction from Lead Profiler matters
Automatic profiling begins with information that arrives through an incoming enquiry flow. Lead Profiler is a separate live tool: a user sends an interactive form to a prospect to collect and structure additional qualification information in the lead card.
The two capabilities can support different moments in the same relationship, but they are not interchangeable. The automatic feature creates order at intake. The user-sent profiler supports a deliberate follow-up when more structured information is needed.
Built for the beginning of the CRM process
Automatic lead creation and profiling belongs to the CRM and Lead Management module. Its job ends at a clear hand-off: incoming interest becomes an identifiable working record, and the user decides whether to continue with lead management.
From there, related CRM capabilities can support comments, tasks, meetings, a configurable Kanban pipeline and reporting. Those functions form the broader process; they are not part of the automatic capture mechanism itself.
Boundaries to know before you rely on the workflow
The feature is live, but its scope is specific. It structures incoming interest and the basic details supplied with it rather than providing a complete transaction management system.
- Customisable forms are supported, but the available profiler fields may vary between forms.
- Personal documents such as passports, completed contracts and other sensitive client files are not stored in Inquiry, Guest or Lead forms.
- Lead and enquiry data is not sent to external systems through the MLS RealtyHub API or webhooks.
- External calendar synchronisation and meeting booking are not part of this workflow.
- No response time, conversion forecast or sales result is promised.
- Availability depends on the enquiry entering through a supported flow.
Start with a cleaner intake process
See how MLS RealtyHub can capture a property enquiry, preserve its context and prepare the record for a professional decision without turning the platform into an intermediary.