The Viewing Feedback Loop

A viewing had taken place. The buyer had an opinion. The vendor was waiting. But the information between those three facts was still being moved by memory, calls, inboxes and handwritten notes.

For this independent sales and lettings agency, the problem was not a lack of effort. Negotiators were already chasing feedback and keeping vendors informed. The weakness was that every person had to remember the next action, assemble the context and decide when to chase again.

The important work happened after the viewing

The agency's booking process was already established. The operational gap opened as soon as a viewing was marked complete. Some buyers replied immediately, some needed a prompt, and others answered with feedback too vague to be useful to the vendor.

That produced four recurring points of friction:

• 1
  Follow-up timing varied.
  The first request depended on the negotiator's workload and memory.
• 2
  Feedback arrived in different shapes.
  Calls, emails and messages left useful detail scattered across channels.
• 3
  Vendor updates were rebuilt by hand.
  Agents had to gather the latest activity before every conversation.
• 4
  Exceptions were hard to see.
  There was no single queue showing what was late, incomplete or needed judgement.

One simple task, split across five places

Before changing any software, we mapped the movement of the work. A completed viewing could touch the diary, the CRM, an inbox, a phone note and a private task list before the vendor heard anything useful.

The issue was not any one tool. It was the manual hand-off between them.

A feedback loop with a human decision point

The rebuilt workflow starts from an event the agency already records: a viewing being completed. From there, the system creates the follow-up, keeps track of elapsed time and gives the team one place to see what needs attention.

The team works from exceptions, not memory

The control view was intentionally simple. It did not try to replace the agency's core systems. It brought the moments that needed attention into one operational queue.

Automation handles movement. Negotiators handle meaning.

Viewing feedback can include negotiation signals, personal circumstances and comments that need context. The workflow was designed to recognise those moments and stop treating them like routine administration.

A calmer process, with fewer invisible gaps

The main result was not another dashboard. It was a clearer operating rhythm after every viewing: the buyer is contacted, silence is visible, useful feedback is structured and the negotiator knows exactly when to step in.

A note on results: the client asked us not to publish numerical performance data. This case study explains the operating change without turning private figures into marketing claims.

Connected to the agency, not imposed on it

The workflow was built around the agency's existing source records, communication channels and ownership rules. That kept adoption practical: the team did not need to run a second version of the business just to benefit from the new process.