How to Present Viewing Feedback to a Vendor (Without the Awkward Call)

Why the call feels awkward in the first place

Most agents don’t dread calling a vendor with good news — the awkwardness is almost always about mixed or negative feedback, and specifically about not having a clear way to say it without sounding like either an excuse (“it’s just a tough market”) or a criticism of the vendor’s home. The fix isn’t a better bedside manner — it’s leading with data rather than opinion, because data doesn’t need to be softened the way a personal judgment does.

Lead with the report, not with small talk

Send the vendor report before the call, even if it’s only a few minutes before. A vendor who’s already seen the numbers comes into the conversation informed rather than anxious about what you’re about to say — the call becomes a discussion of what to do next, not a reveal of bad news. This single change removes most of the awkwardness on its own.

Structuring the conversation: data first, recommendation second

A conversation built around feedback holds up better than one built around impressions, because it has a clear shape to follow:

1. State the facts. “We’ve had 8 viewings, average rating 4.2 out of 5.”
2. Name the pattern. “6 of the 8 have mentioned the price.”
3. Pause. Let the vendor react before jumping to a recommendation — most people want a moment to process before being told what to do about it.
4. Offer a recommendation, framed as a suggestion, not a verdict. “Given how consistent that feedback’s been, I’d suggest we talk about a small adjustment — even £5-10k tends to move viewer sentiment quite a bit at this price point.”

This order matters because it keeps the vendor oriented in facts before opinion arrives — by the time you offer a recommendation, it’s clearly grounded in something specific rather than a hunch.

A script for positive feedback

The easy case, but still worth having ready so it doesn’t come out flat: “Really good week — 4 viewings, average rating 4.5, and 3 of the 4 said they’d consider offering. No offers on the table yet, but the interest is clearly there — we’re following up directly with a couple of the more engaged viewers.”

A script for mixed feedback

“Feedback’s been mixed this week — decent interest, average rating 3.8, but two separate viewers mentioned the kitchen needing updating. Nothing that’s put people off entirely, but it’s worth knowing it’s come up more than once. [If relevant: happy to talk through whether a small refresh before further viewings might be worth it.]”

A script for a clear price objection pattern

This is the conversation most agents put off. See how to tell a vendor their asking price is too high for the full version, but the shape is: state the pattern plainly, don’t apologise for it, and move quickly to what it means practically rather than dwelling on it. “6 of 8 viewers have independently raised the price. That’s a strong enough pattern that I think it’s the main thing standing between where we are and an offer — worth talking through the options.”

What not to do

• Don’t soften the numbers. Rounding “6 of 8 mentioned the price” down to “a couple of people mentioned the price” undersells a real pattern and makes the eventual price conversation harder to have later, once it’s undeniable.
• Don’t apologise for feedback you didn’t create. You’re the messenger for what viewers said, not the author of it — there’s nothing to apologise for in relaying an honest pattern.
• Don’t skip straight to a recommendation without the data behind it. “I think we should drop the price” lands very differently from “6 of 8 viewers mentioned the price, so I think we should discuss it” — the second is a conclusion the vendor can follow, not just an opinion to accept or push back on.
• Don’t let one comment carry the same weight as a pattern. Presenting a single viewer’s remark with the same gravity as a repeated theme across several viewings will make vendors distrust the report next time something genuinely significant comes up.

A worked example: the same feedback, presented two ways

Poorly framed: “So, viewings have been happening, people seem to like it but, er, a few have mentioned the price is maybe a bit much, not sure, might be worth thinking about it at some point.” Vague, apologetic, and gives the vendor nothing concrete to respond to.

Well framed: “8 viewings, average rating 4.2 out of 5 — genuinely positive. 6 of those 8 have independently raised the asking price as a concern, and half said they’d consider offering if it came down. That’s a consistent enough pattern that I think it’s worth discussing a price adjustment — even a modest one tends to shift viewer sentiment noticeably at this level.”

Same underlying facts, but the second version gives the vendor something they can actually engage with and decide on, rather than a mumbled impression they have to interpret for themselves.

Where this fits

For the underlying report this conversation is built on, see the vendor report template. For how the feedback itself gets collected in the first place, see our complete guide to viewing feedback for estate agents. For the specific price conversation, see how to tell a vendor their asking price is too high.

If building the report itself is the part that eats your time, ViewingFeedback rolls collected feedback into a vendor-ready summary automatically, so the call can start from the data rather than from a blank page.