Your VoC team has become the silo. Here's how to fix that.

Most housing associations stood up a Voice of the Customer team in the last few years for one structural reason: to break down the internal silos that kept tenant insight trapped inside repairs, or housing management, or complaints. It worked. The team got built. The platform got chosen. The reports started landing. And then, in the more mature programmes, something quietly went wrong. The VoC team became the new silo. Insight goes in. Reports come out, monthly. A Power BI dashboard exists for those who’ll click into it. But the call handler taking a complaint at 9am on Tuesday, and the engineer pulling up to a tenant’s address at 2pm, see none of it. What you’ve built, without quite meaning to, is a silo of the voice of the customer.

A silo of the voice of the customer

The phrase isn’t ours. We borrowed it from a VoC lead at a housing association we work with — said slightly mischievously, about her own team. And once you’ve heard it, you can’t unhear it.

The original mission of a VoC team was structural. Pull the customer’s voice out of the places it was getting trapped. Give the organisation a single platform, a single team, a single monthly view. Most mid-to-large housing associations have done that work, and it took years. The achievement is real.

The unintended consequence is also real. The data now lives with the VoC team. The team is the gatekeeper, sometimes by design and sometimes just by gravity. Reports go out. Dashboards exist. But the colleagues who actually deliver the next service moment — the call handler, the repairs engineer, the scheme manager — are not the audience for those reports. They’re not the people opening the dashboard. They’re the people whose Tuesday morning would change if they had the right insight at the right moment, and who currently don’t.

A monthly PDF read by ten people is structurally a silo. So is a Power BI dashboard nobody outside the VoC team logs into. The format is fancier than the spreadsheet you replaced; the architecture is the same. We’ve written before about why VoC programmes stall when feedback doesn’t reach the right people.

This isn’t a failure of the team. It’s a sign the programme has reached the point where the question changes.

Once you’ve solved collection, the job is distribution

The job of a mature VoC programme is data distribution, not data collection. That’s the reframe. Most programmes haven’t made it yet, and it’s the single most important shift on the maturity curve.

Mature programmes have all roughly converged on the collection answer. In-journey transactional surveys at the moments that matter — repairs, complaints, ASB, lettings, tenancy changes. A single platform. Reasonable response rates. RAG-flagged verbatim. A monthly trend report that gets to the leadership team. None of that is easy, and getting there took budget, political capital, and years of patient work.

Past that point, more data isn’t the constraint. The constraint is reach. Insight that lives only in the VoC team’s reports is a silo, by definition. Even a high-quality one.

You’ll hear the objection: our VoC team has the data, that’s enough. It isn’t. Owning the data is not the same as the data reaching the colleague who can act on it. The right test for Heads of Customer and Insight isn’t “do we have the insight?” — it’s “did the colleague who delivers the next service moment see the relevant insight before the moment, in the tool they were already using?” That’s a much harder standard, and most programmes fail it. It’s the same idea behind the closed-loop principle: insight has to reach the person who can act on it.

The next-generation VoC team’s job, put bluntly, is to make itself invisible. Not because the team has stopped mattering — the opposite. Because the team has matured to the point where its value is measured by what colleagues elsewhere in the business can do without it, not by the reports it produces every month.

The repairs engineer in the van

Here’s what that looks like operationally. A housing association we work with — further along the data-maturity curve than most — has named the problem out loud. Their team is good. They’ve got the data, the platform, the dashboards, the monthly reports. And they’re explicit that their next move is to invert the model: colleagues across the business should be able to self-serve VoC insight without ever logging into the VoC platform.

That ambition is the tell of a mature programme. The team is willing to make itself less central in the daily life of the business so that the customer’s voice can become more central. Housing associations running lean VoC teams have to think this way from day one — distribution is survival.

The vivid version of the same idea, at the same association: the repairs engineer in the van. When an engineer is logged into their repairs scheduling and dispatch tool on the way to a job, the vision is that they should see — at their fingertips — every relevant bit of feedback the tenant has ever given. Past survey scores. Verbatim comments. RAG-flagged risk on the address they’re driving to. Before they pull up. Not a fortnight later, in a manager’s report, after the visit has already gone wrong.

That’s distribution. Concrete, sector-specific, operational. It’s the opposite of a polished monthly PDF, and it’s the standard the next decade of housing VoC will be judged against.

[IMAGE SUGGESTION: Simple hub-and-spokes diagram. The VoC platform as the engine room (a hub), with arrows pushing insight outwards into the operational tools colleagues already use — the CRM most housing associations use, the repairs scheduling tool, the complaints case management system, BI. The colleague does not log into the hub.]

Three signs your VoC team has become the silo — and the move for each

Sign 1: Your distribution mechanism is a monthly PDF, or a dashboard nobody outside the VoC team logs into.

If the answer to “how does this insight reach colleagues?” is “we send a report” or “they can log in and look”, the architecture is wrong. The move is to identify the two operational tools your front-line colleagues actually open every day — typically the CRM most housing associations use, plus the repairs scheduling tool — and make those the surfaces for VoC, not your platform. The VoC platform is the engine room. It shouldn’t be the destination.

Sign 2: The VoC team is gatekeeping rather than enabling.

This usually isn’t a personality problem. It’s a structural one. If the team’s value is measured by reports produced, the team will produce reports and feel protective of the data those reports are built from. The cultural question runs alongside the structural one — the data isn’t the problem, the way it’s used is. The move is to redefine the team’s KPI. From reports produced, to insight reaching the colleague who can act on it. Measure the team on the second thing and the first thing takes care of itself.

Sign 3: Colleagues elsewhere in the business have stopped asking.

The instinct is to read this as success — they’ve got what they need. It’s almost always the wrong reading. Usually it means they’ve concluded the data isn’t for them, doesn’t arrive in time, or doesn’t fit how they actually work. The move is to re-establish demand by pushing one specific, named insight into one specific tool — and tracking whether anything changed in the next service moment. One pilot, one tool, one measurable change. That’s how you find out whether distribution is working, rather than assuming it is.

This is, incidentally, the problem CustomerSure is built around. The platform is designed to push insight into the tools colleagues already use — CRM, repairs scheduling, case management, BI — through webhooks and a REST API, rather than asking colleagues to log into another system to find it. If you’re trying to make the VoC platform less central in the daily life of the business, the technical means matters. Insight has to be able to leave the platform.

The team that succeeds disappears

The risk in a mature VoC programme isn’t that the team failed. It’s that it succeeded at the original brief — collected the data, owned the platform, produced the reports — and in doing so quietly became a silo of the voice of the customer.

The way out is unglamorous. Pick one operational tool your colleagues already open every day. Pick one piece of VoC insight that would change what they do in that tool. Push the second into the first. See what changes. Then do it again, somewhere else.

The team that genuinely cracks distribution is the team that’s willing to be a little less central. To make itself, in operational terms, invisible. That’s not a downgrade. It’s the next-generation job.

Make the platform less central. Make the customer's voice more central.

If you're rebuilding your housing VoC programme around distribution — pushing insight into the CRM, scheduling and case-management tools your colleagues already use — we'd be glad to talk. See how we work with housing associations.

Talk to us