When to use showing feedback request emails
Use these after a showing when you need useful feedback from a buyer agent, a buyer, or your own seller update process. For buyer-facing follow-up after a tour, use the listing and showing follow-up templates.
Showing feedback only matters when it changes what you do next. Ask for the specific reaction that affects price, presentation, objections, or the buyer's next step.
One comment is noise; a pattern is a signal
Most showing feedback feels disappointing because agents read it one comment at a time. The buyer who didn't love the kitchen, the buyer who flagged the street, the buyer who never replied: each is a single data point, and a seller update built on a single data point reads like guessing. Log every comment into a small number of categories (price, condition, layout, location, access, presentation, interest level) and wait for the repeats before changing the recommendation.
Showing platforms like ShowingTime send the feedback requests and collect the replies; the agent's job is to read what repeats. Keep one threshold from the log through the seller recap: one mention starts the log, three of the same category across distinct showings becomes a seller-update line, and three with no offer behind any of them becomes a recommendation to move on whatever that category points to, whether price, presentation, or access. Count categories, not showings, so a repeated category with no offer is the trigger no matter how many showings it took to surface.
Plan the collection step around the fact that buyer-agent response rates are uneven. Two moves keep the rate up: send the ask the same day while the showing is still fresh, and keep the form short enough to answer in under a minute (three or four questions, the last one open-ended). Assume most showings will not generate a reply, and let the seller update wait for the pattern across several requests rather than recapping one comment at a time.
Buyer-agent ask vs seller-facing recap
The buyer-agent ask and the seller-facing recap have different jobs. Treating them as one bucket is why most seller updates end up as forwarded buyer-agent quotes.
- Buyer-agent ask: The audience is another working agent. The job is collecting one decision signal: did the buyer move forward, is there a second showing, did they pass, and if so what was the leading reason. Keep it one or two lines, sent by text or email depending on your relationship with that agent, and make a one-word reply acceptable.
- Seller-facing recap: The audience is the homeowner. The job is to interpret what came back. Quote nothing verbatim. Summarize the categories that repeated, the categories that did not, and the next decision sitting on the table. A recap that just lists raw buyer-agent comments puts the seller in the position of pattern-matching for you.
- Neutral language: Recap feedback in neutral property categories: price, condition, layout, location, parking, fees, and offer likelihood. Avoid demographic, family-status, religion, or school-quality language in seller-facing recaps.
Pick the template by which audience needs action
Showing feedback has two audiences: the buyer side (the buyer agent or the buyer you toured) and the seller who needs the pattern. Pick the template based on which side needs the next move.
| Buyer-agent ask (Template 1) | Private showing (Template 2) | No feedback (Template 3) | Seller recap (Template 4) | Price signal (Template 5) | |
|---|---|---|---|---|---|
| What just happened | Another agent's buyer just walked through and the agent has the freshest read. | You showed a buyer the property and need to know whether it stays on the list. | A first feedback ask went out and no reply has come back. | Several buyer comments are in and the seller needs the pattern read. | Three showings have flagged the same value concern with no offer behind them. |
| Pattern action | Ask for the decision signal, not a generic opinion. | Ask what stood out and what the hesitation is, so you know whether it's still on the shortlist. | Lower the effort needed to reply; a one-word reason is enough. | Translate raw comments into the pattern the seller can act on. | Tie the repeated pattern to a specific price, prep, or access move. |
Buyer-agent ask (Template 1)
- What just happened
- Another agent's buyer just walked through and the agent has the freshest read.
- Pattern action
- Ask for the decision signal, not a generic opinion.
Private showing (Template 2)
- What just happened
- You showed a buyer the property and need to know whether it stays on the list.
- Pattern action
- Ask what stood out and what the hesitation is, so you know whether it's still on the shortlist.
No feedback (Template 3)
- What just happened
- A first feedback ask went out and no reply has come back.
- Pattern action
- Lower the effort needed to reply; a one-word reason is enough.
Seller recap (Template 4)
- What just happened
- Several buyer comments are in and the seller needs the pattern read.
- Pattern action
- Translate raw comments into the pattern the seller can act on.
Price signal (Template 5)
- What just happened
- Three showings have flagged the same value concern with no offer behind them.
- Pattern action
- Tie the repeated pattern to a specific price, prep, or access move.
Showing feedback tracker
Track feedback in categories so seller updates do not turn into a pile of quotes. The goal is to spot repeated buyer objections and decide what to change.
Feedback log fields
- 1Showing date and buyer agent.
- 2Buyer interest level: no interest, maybe, second showing, offer likely.
- 3Price feedback.
- 4Condition or repair feedback.
- 5Layout, location, parking, strata or condo fees, smell, staging, or access feedback.
- 6Repeated objection count.
- 7Recommended next step: hold, adjust price, fix presentation, improve access, or follow up.
Feedback-to-action decision tree
Use repeated feedback to decide what changes. The first comment starts the log; the pattern changes the recommendation.
| Hold | Fix presentation | Discuss price | |
|---|---|---|---|
| Signal | Showings are steady and objections are scattered. | Multiple buyers flag the same repair, smell, staging, access, or photo mismatch. | Several buyers like the home but compare it against lower-priced or newer options. |
| Seller update | Interest is still broad enough to keep watching. | The issue is specific enough to address before the next showing window. | The pattern is now about value, not exposure. |
| Next move | Keep collecting feedback and follow up with likely buyers. | Fix the presentation issue, then update photos or remarks if needed. | Review comps, showing count, and seller timeline before recommending a pricing move. |
Hold
- Signal
- Showings are steady and objections are scattered.
- Seller update
- Interest is still broad enough to keep watching.
- Next move
- Keep collecting feedback and follow up with likely buyers.
Fix presentation
- Signal
- Multiple buyers flag the same repair, smell, staging, access, or photo mismatch.
- Seller update
- The issue is specific enough to address before the next showing window.
- Next move
- Fix the presentation issue, then update photos or remarks if needed.
Discuss price
- Signal
- Several buyers like the home but compare it against lower-priced or newer options.
- Seller update
- The pattern is now about value, not exposure.
- Next move
- Review comps, showing count, and seller timeline before recommending a pricing move.
From a filled log to the seller recap
Put the threshold to work on one listing. After six showings, the log reads: kitchen praised in four of six, third-bedroom layout flagged in four of six, price flagged in one, and no offers. The single price flag is still noise. Four flags on the layout, across distinct showings, is the pattern.
The Template 4 recap follows straight from that log. The clearest positive was the kitchen, the repeated hesitation was the third-bedroom layout, and the read is that buyers like the kitchen and lot but stall on the bedroom flow. The repeated category is presentation, so the next move is restaging the third bedroom as an office before the next showing window. A price cut here would solve the wrong problem.
Swap the numbers and you reach for a different template. Four price flags with only a scattered layout comment point at Template 5 and a pricing conversation. Match the template to whichever category crossed three showings with no offer behind it.
Showing feedback request templates
Template 1: Ask a buyer agent for showing feedback
Use this after another agent shows your listing and you need practical feedback.
Feedback on [Property Address]?
Hi [Agent Name],
Thanks for showing [Property Address]. What was the buyer's read, and is there anything you'd want changed before another showing?
One line is plenty.
Best,
[Agent Name]
Ask for the decision signal first. Add a category only when you already know the showing had a specific concern.
Don't prompt with a list of categories ("price? condition? layout?"). A category menu invites a category-shaped reply instead of the decision signal you actually need.
Template 2: Follow up after a private showing
Use this when you showed the buyer a property and want to understand whether it stays on the list.
Thoughts on [Property Address]?
Hi [Name],
Curious what you thought of [Property Address] after seeing it in person. What stood out, and what did not?
If it's a maybe, I'm most interested in the hesitation.
Best,
[Agent Name]
The hesitation matters more than the like. A buyer who only names what stood out usually has a polite reason they didn't volunteer.
Don't ask the buyer to weigh the home against others on their shortlist. They'll do that work themselves; the email shouldn't request the homework back.
Template 3: Follow up when no feedback comes back
Use this when a buyer agent has not responded to the first feedback request.
Re: feedback on [Property Address]
Hi [Agent Name],
Coming back to [Property Address]. If your buyer passed, the main reason is all I'm after.
A one-word answer is completely fine.
Best,
[Agent Name]
Lower the effort required to reply. A one-word reason beats silence.
Don't send repeated feedback requests if there's no reply after the second touch.
Template 4: Recap showing feedback to the seller
Use this when you need to translate buyer comments into a seller update.
Showing feedback recap for [Property Address]
Hi [Name],
Here's the feedback pattern from the recent showings at [Property Address].
The clearest positive reaction was [the kitchen renovation]. The repeated hesitation was [the third-bedroom layout]. My read is that buyers value [the kitchen and lot] but stall on [the bedroom flow], and that gap is keeping them from a stronger offer.
I recommend we [the specific next step, like restaging the third bedroom as an office before the next showing window].
Best,
[Agent Name]
Name the negative pattern in plain terms. Sellers can act on "third-bedroom layout" but not on "mixed feedback."
Don't forward disconnected comments without interpretation.
Template 5: Explain feedback that points to price
Use this when repeated showing feedback suggests pricing is the real issue.
A pricing signal from showing feedback
Hi [Name],
Three of the last [number] showings have flagged price.
The pattern is [number] buyers liked [the kitchen finish and lot] but hesitated on [the value comparison they raised]. Buyers are coming through but comparing it against lower-priced or newer options nearby.
My recommendation is [specific pricing or strategy step]. Worth a 10-minute call to talk it through: I'm around [today at 4] or [tomorrow at 11].
Best,
[Agent Name]
Use repeated feedback, not one buyer comment, as the reason for a pricing conversation.
Don't use feedback as a vague excuse for a price reduction. Show the pattern.