How to beat other agents to a portal inquiry

At twenty to ten on a Tuesday evening a buyer sees a three-bedroom semi on a portal and sends the same inquiry to four agents. One replies before the buyer closes the laptop. That agent gets the conversation, the qualification, the showing and usually the relationship. The other three send a polite acknowledgement the next afternoon and never learn why they were ignored.

Every agency knows this and almost none are set up for it, for structural rather than cultural reasons. Inquiries arrive in the evenings and at weekends, precisely when the office is closed. They land in a shared inbox. The portal strips the phone number into the body of an email. By the time a human reads it, the race is over.

Why the first agent to reply usually wins the buyer

Speed does not win because buyers are impatient. It wins because of what happens in the first exchange. The agent who replies first sets the frame: which property is being discussed, what the next step is, and who is asking the questions. Everyone else arrives into a conversation that started without them.

There is also a practical asymmetry. A buyer sending four inquiries at ten at night is in a short window of active interest, phone in hand and calendar open. In that window they will answer a question, give you their timeline and take a showing slot. The next afternoon they are at work and the same questions take three exchanges.

So the race is not really about minutes versus hours. It is about whether your reply lands inside the buyer's window of attention. Everything in a speed-to-lead build exists to make sure it does.

Why portal inquiries are structurally set up to go cold

If you map what happens to a typical portal inquiry, the failure points are mechanical and fixable.

• Arrival timing. Peak browsing hours are the hours your office is closed. A rota does not fix this; it moves which person is tired.
• Channel mismatch. The inquiry arrives as an email notification. The buyer will answer a text and will not answer a call from an unknown number.
• Lost structure. The phone number and property reference are buried in notification text rather than arriving as fields, so nothing downstream can use them.
• Generic acknowledgements. The reply restarts the conversation from zero: no mention of the property, no question about timing or finance, no booking link. The agent then spends three exchanges establishing facts that could have been captured in the first minute.
• No sorting. Only a minority of portal inquiries are financed buyers ready to view in the next two weeks. Nobody has time to sort by hand, so either everyone gets the same treatment and the good ones are under-served, or the agent picks by instinct and the quiet serious buyer loses to the loud time-waster.

What a sixty-second reply actually has to contain

A fast reply that says nothing is barely better than a slow one. The first message is doing four jobs, and the order matters.

1. Name the property. Not "your inquiry". The actual address. A reply that names the property outperforms a generic one every time, because the buyer sent four inquiries and cannot tell which is which.
2. Confirm availability. It is the question behind most inquiries and answering it unprompted removes the first objection.
3. Identify the sender honestly. If the reply is automated, say so. An assistant that introduces itself as one and offers to put the inquirer through to a person builds trust. One impersonating a named negotiator destroys it, and in some places is not permitted at all.
4. Ask one question that moves things forward. When would you like to see it. Not a list, not a form, one question with an obvious answer.

Out of hours, acknowledge the hour and keep going: a line saying you know it is late and you are happy to sort this now by text, or someone will call in the morning, whichever they prefer. Speed matters more than politeness about the clock. The property inquiry speed-to-lead build guide carries the full message set, pipeline and workflow specification.

How to build a speed-to-lead system for property inquiries

Step 1: Get the inquiry in as structured data, not as an email

Use a direct portal integration where one exists. Where it does not, parse the notification email and extract name, mobile, email and property reference into real fields. Test the parser against genuine notifications from every portal before launch, and re-test monthly: formats differ and change without notice. A broken parser is invisible until someone notices volume has dropped.

Step 2: Deduplicate before you reply

Match on mobile first, then email. If an open inquiry already exists for that person, append the new property reference to it and notify the agent who owns the thread. Do not create a second record or send a second first-response. Two automated introductions to the same buyer undo everything the speed bought you.

Step 3: Handle the broken cases deliberately

If the property reference cannot be parsed, flag it for a human within a couple of minutes rather than sending a generic reply: getting the property wrong is worse than being slow. If there is no phone number and no email, create a task on the office queue and stop. These two branches are where automated inquiry handling usually embarrasses itself.

Step 4: Reply within a minute, on the channel that works

Text first, email in parallel. The text does the four jobs above. The email carries the listing summary, a few photographs, the booking link and the agent's name. Where no mobile came through, ask for one in the first line of the email. And if the record already shows a known, financed buyer, ring the assigned agent at the same moment the text sends. A hot buyer should not wait for a text exchange.

Step 5: Qualify in the same conversation

Do not send a form. Ask at most two questions per message, in a deliberate order: timeline, then finance, then whether they have a property to sell, then area and minimum bedrooms. Never ask budget before finance, early it reads as a credit check, after finance it reads as scoping. Write each answer to its own field as it arrives, so the agent inherits structured facts rather than a transcript.

Step 6: Score, then route by score

Combine finance status, timeline, whether there is a property to sell, how quickly they replied, and whether they asked a specific question about the property. Then route: financed buyers with a near-term timeline go straight to showing slots with the agent notified; genuine buyers with a longer horizon get a showing offer and, if declined, a short discovery call; browsers go into listing alerts rather than being closed, because a browser today is a buyer in nine months.

Step 7: Draw the guardrails before you switch anything on

Write down exactly which questions an automated assistant may answer and which it must not, with the office manager and your compliance adviser rather than from a template. Facts already published on the listing are fair game (asking price, bedrooms, tenure, floor area, parking, what is included) and every answer must come from the listing record rather than being improvised. Everything else routes to a human: offers, whether an offer would be accepted, mortgage or legal questions, surveys, structural matters, chains, and anything a reasonable person would call a complaint.

More importantly, fair housing and anti-discrimination rules apply to an automated message exactly as they apply to an agent's words. An assistant must never answer questions about the demographics, religion, ethnicity or family makeup of an area or its residents, never steer buyers toward or away from areas on those grounds, and never use schools or crime as a proxy. Build those as hard refusals with a handoff, review transcripts regularly, and have your permitted-answer list, disclosure wording and retention policy confirmed by your own counsel before launch. This is operational practice, not legal advice.

Step 8: Book the showing properly, with travel time in the calendar

Sync agent calendars two-way first, so personal appointments block showing slots, then build the buffer into the calendar itself (time before and after each slot) so back-to-back showings across town cannot be booked. Write the qualification summary into the appointment notes so the agent arrives informed. Where a property is tenanted or occupied, notify the occupier and hold the confirmation until access is agreed; never confirm a showing the vendor has not accepted. Then a reminder the day before with a reschedule link, and a short message a couple of hours ahead naming the agent who will meet them.

Step 9: Put a clock on the whole thing

A scheduled check every few minutes against anything unanswered, a tag applied automatically when the response-time target is missed, and a notification to the office manager. Treat the tag as a management report, not a punishment: a breach almost always means a capture integration has failed, and the point is to find it today.

The listing instruction hiding in your buyer inquiries

There is one question most agents never ask a portal inquirer: do you have a property to sell? A share of every agency's buyer inquiries are undiscovered listing instructions, and the answer is free to collect in a conversation you are already having.

Two rules make this work rather than backfire. Ask it as part of qualification, not as a pitch. It is a reasonable question about their position and buyers answer it readily. And never cross-sell the valuation before you have earned the showing: flag the record, open a valuation opportunity quietly, and schedule the appraisal offer for a couple of days after the showing. One low-key attempt, then hand it on. Pitching an appraisal in the same breath as a showing confirmation reads as what it is.

Mistakes that cost agents the race

Mistake 1: Replying by email only

The inquiry arrived by email, so the reply goes by email, and it sits unread among the other three. Portal inquirers answer texts far more readily. Send both, lead with the text.

Mistake 2: Front-loading a long qualification form

Keep the listing-page form to about five fields, with the property reference passed in as a hidden field. Every extra field costs you inquiries at exactly the stage you are trying to protect. Qualify in the conversation afterwards, where answering is cheap.

Mistake 3: Closing unqualified inquiries with no reason

An unqualified pile with no reasons is the same problem a speed-to-lead build exists to fix. Record whether it was out of area, a budget mismatch, not a buyer at all, or someone who had already purchased, and handle each differently. Budget mismatch gets listings in their actual band rather than a close. Someone who bought elsewhere gets one message a long way in the future, because buyers move again and nobody else will remember.

Mistake 4: Going live without sender registration

In the United States, brand and campaign registration for business messaging must be completed before launch, under the correct use case for conversational lead response. Approval takes days to weeks and unregistered traffic gets filtered, which in a speed-to-lead build means the whole value proposition silently fails. Outside the US, confirm the destination country's registration and consent rules, and authenticate your email domain before the first send.

What to measure

• Median seconds to first response, and the ninetieth percentile. The average will flatter you. The long tail is where leads die.
• Breaches of your response-time target. Should be near zero; anything else means a capture integration is failing.
• Inquiry-to-showing-booked rate, split by source. This is the number that should drive next year's portal spend, rather than lead volume.
• Vendor leads discovered per hundred buyer inquiries. The hidden return on the whole build.

Measured from the timestamp the inquiry arrived to the timestamp the first reply went out, split by source and agent, that response-time number is something most agencies have never had, and it makes portal spend arguable with evidence instead of anecdote. To scope this against your own portals and office hours, book a call and we will test the capture chain first. Other sector builds sit across the AppBO build guides.

Frequently Asked Questions

Is it acceptable to reply to a property inquiry at ten at night?

Replying to an inbound inquiry about a specific property is a direct response to a request, which is a different thing from marketing. Keep automated first responses inside a sensible window (roughly early morning to late evening local time) acknowledge the hour in the opener, and apply standard quiet hours to every follow-up nudge and marketing send. An inquiry is not consent for ongoing listing alerts; capture that separately and record the source and date.

Will buyers mind talking to an automated assistant first?

Most do not, provided three things are true: it says plainly that it is an assistant, it offers to put them through to a person, and it never pretends to be a named agent. What irritates buyers is not automation but a reply that gets the property wrong, answers a question it should not, or loops without escalating. Build the handoff triggers generously and review transcripts.

How many follow-ups should an unanswered inquiry get?

Few, specific, and capped. A short nudge offering two concrete showing times, a call attempt, an email with comparable listings in the same area and band, and one final message offering alerts instead. Then stop. Four outbound touches, enforced centrally, is a reasonable ceiling. The alternatives email is what usually rescues the lead, not the fourth chase.

What should happen to inquiries outside the agency's patch?

One courteous message and a close. Send a short page explaining the coverage area with a referral path where you have one, tag it, and record the reason. A courteous no protects the brand and costs nothing, and the reason code keeps the unqualified pile honest enough to be read.