Seven Showings, No Word: Fixing Seller Feedback
Thursday, 4:10 PM, the seller calls you
The listing went live a week ago Friday. Seven showings since. The seller has heard nothing about any of them, so he stopped calling his agent and called the office instead.
You know what happened. The agent sent feedback requests after the first two showings, got one reply, and then Tuesday turned into three offers and a failed inspection. The feedback didn't stop mattering. It just stopped getting chased.
And now you're on the phone with a seller who is not really asking about feedback. He's asking whether anyone is paying attention to his house.
The silence costs more than the information
Here's what makes this one expensive. Half the feedback you chase is worth very little. "Nice house, buyer wants a bigger yard." You didn't need that to price or position anything.
But the seller needed to hear it. Not because it changes the plan, but because it proves someone was there, someone asked, and someone came back to him. That's the whole product in the first two weeks of a listing.
When the silence runs ten days, three things start happening. The seller calls the office instead of the agent. The seller starts reading the price as the problem, because no other information has reached him. And when the price conversation finally comes, it lands as a reaction to a quiet listing instead of a read on the market.
This is the listing week leak. The work was done. The showings happened. The updates just didn't go out.
Why chasing feedback falls off every single time
It isn't effort. It's structure. Feedback is the only task in a listing with no deadline attached to it and no consequence for being a day late.
A closing date is a deadline. An inspection response window is a deadline. A showing that happened Saturday at 2 PM generates nothing on anyone's calendar. The request goes out automatically from the showing system, most buyer agents don't answer it, and then the task is: send a second message to a stranger asking for a favor.
That second ask is the piece that drops. It's low status, it's awkward, and it competes with live clients. Any agent will choose the live client. They're right to.
So the fix is not reminding agents to care more. The fix is making the second ask something that happens without the agent having to decide to do it.
Build the one-page feedback standard this week
Before any of this gets automated, write down what a seller update actually is at your brokerage. One page. It takes about forty minutes and it's useful whether or not you ever automate a thing.
Decide four items. First, the window: feedback is requested within a set number of hours after the showing, and a second request goes out if there's no answer by a set time the next day. Pick the numbers that fit your market and write them.
Second, the stop rule: two requests, then stop. You are not going to get feedback from every buyer agent and chasing a third time costs goodwill you'll want on the next deal.
Third, what the seller hears when there's no feedback. This is the most important line on the page. Most brokerages have no answer here, so nothing goes out. Your answer should be something like: the showing happened, the agent was asked twice, no response yet, here's what the other showings this week have said. Silence from a buyer agent is still an update.
Fourth, the cadence: every seller hears something at a set point each week, whether or not there were showings. A listing with zero showings needs the update more than a listing with four.
What a good update looks like when it's written down
Keep it short and keep it concrete. A seller update that works has four parts: how many showings since the last update, what the feedback said, what you asked and didn't get back, and what's booked next.
Say a listing had three showings this week. One agent said the buyers liked the kitchen and thought the basement ceiling was low. One said the buyers are still looking at new construction. One never answered after two requests. Two showings are booked for Saturday.
That's the update. Four sentences. It tells the seller the truth, it shows the work, and it builds the record you'll want in three weeks if a price conversation becomes necessary. When you've sent nine of those, the price conversation is easy, because the seller has been reading the market with you the whole time.
What doesn't work is the summary that only goes out when there's good news. Sellers notice the pattern fast, and then every update is read as either good news or a warning.
A short note before the next section
If you want the arithmetic on what the listing week leak costs a roster your size in a year, the Leak Report lays it out at systems.lionmaker.io/apply. Same place to book the 15-minute Private Automation Briefing if you'd rather we look at your brokerage specifically.
Who actually does the chasing
Once the standard is written, the question is whose hands do the work. There are three honest answers and only one of them survives a busy month.
The agent does it. This is what you have now. It works for agents with two listings and fails for agents with seven, which means it fails exactly when a listing is most valuable to you.
An admin does it. This works, and it's real payroll against a task that is almost entirely sending second messages and copying replies into an email. It also breaks the week your admin takes vacation.
Or the chasing runs on its own inside your systems. The showing happens, the request goes out, the clock starts, the second request goes out if nobody answered, the replies collect in one place, and the seller's update is drafted in the agent's name with the brokerage's four parts filled in.
That's the piece we build. Shepherd chases showing feedback and keeps the sellers in the loop, working from your listing data, your showing records and your own wording. The agent reads the draft and sends it, or approves a whole batch Friday morning. Nothing goes out that you haven't decided can go out on its own, and every automated message is tagged "Automated by Lionmaker AI".
What changes in the office when this is handled
The first thing you notice is the calls. Sellers stop calling the office for status, because status arrives before they think to ask for it.
The second thing is the price conversation. It stops being a confrontation and becomes a reading of nine weeks of feedback the seller has already seen. You're not persuading him. You're pointing at a record you built together.
The third thing is the listing presentation. When a seller at the kitchen table asks what the commission pays for, the agent has a specific answer: here is the update you get every Friday, here is what we do when a buyer agent doesn't reply, here is the recap you get the Monday after every open house. That's a different conversation than talking about marketing in general terms.
And your agents get their evenings back from a task none of them enjoy. The commission won back on one listing that didn't go stale covers more than you'd guess.
Start with three listings, not the whole roster
Pick your three most active listings this week. Write the one-page standard. Apply it by hand for ten days and see where it strains.
You'll learn two things fast. You'll learn which buyer agents in your market answer and which never do, which tells you what to promise sellers going forward. And you'll learn exactly how many second requests a week your brokerage actually generates, which is the number that tells you whether this is a person's job or something that should run on its own.
Then widen it. The standard is the asset. The chasing is just labor, and labor is the part that can be handled without adding a desk.
The first leak we seal at a brokerage is usually live in about two weeks, built inside the phones, CRM and files you already have, in your brokerage's voice and under your rules about what sends on its own.
If you want help with this one
The 15-minute Private Automation Briefing is where we look at where your listing week is leaking and what it would take to close it. You can book it, or read the Leak Report first to see the yearly cost of each of the six leaks, at systems.lionmaker.io/apply.
Our team replies within 24 hours.