Who Should You Ask for Feedback in a B2B Client Account?

Ask the people whose roles give them a meaningful view of the client relationship. In many B2B accounts, that often includes a decision maker, a champion, and key users. The supplier should decide whom to invite because it knows the account and needs to understand who each response comes from before it can act on it.

‍

At Cliezen, we leave the recipient list to the supplier. We advise choosing deliberately, then looking for missing perspectives rather than assuming that one helpful contact speaks for the whole account.

‍

For the questions themselves, our B2B customer feedback survey guide explains why the respondent's role should shape what you ask.

‍

Which contacts should be considered first?

Start with people who make or influence the decision to keep working with you, people who advocate for the relationship internally, and people who experience the service or product in daily work. These roles may overlap in a small account and be spread across many people in a larger one.

‍

A useful contact list records each person’s role, what they experience, what they expect from the supplier, and who on your team knows the relationship. It should also show whether that person is already being asked for feedback. The aim is to understand the context of each response, not to maximize the number of invitations.

‍

Our B2B customer journey guide maps stakeholder lanes across stages. This contact list has a narrower job: help the account team decide whom to hear from about the ongoing relationship and how to follow up.

‍

Why does the respondent’s role matter?

People can judge the same supplier relationship against different expectations. A decision maker may focus on the broader business case, while a key user may focus on the reliability of day-to-day delivery. A champion may value the working relationship but see less of the operational detail.

‍

In our work with B2B suppliers/vendors/service providers, we see widely varying feedback inside the same account. That difference is useful when interpreting a response: disagreement does not automatically mean one person is wrong. It may reveal different needs, experiences, or expectations that require separate conversations.

‍

An illustrative account

For example, an operations contact might report that handoffs cause delays while an executive sponsor says the overall relationship is constructive. The account team should learn what each person is seeing before compressing those views into one account-wide judgment. The hidden complexity of B2B relationships offers the broader rationale for hearing beyond the most familiar contact.

‍

Should you ask everyone in the client organization?

No blanket rule serves every account. We caution against treating a broad feedback list as a substitute for knowing whose feedback matters and why. The supplier is best placed to choose relevant contacts; Cliezen does not decide that list for it - but we help with everything pretty much else.

‍

A feedback invitation is useful when the account team knows who the respondent is, what part of the relationship they can speak to, and who can respond to a concern. Otherwise, even candid feedback can be hard to route into a meaningful conversation. This is an operating recommendation, not a statistical claim about sample size or representativeness.

‍

The contact list should also leave room for someone outside the familiar group. If the service affects a team that is missing from the list, find out whether its perspective should be included before concluding that the account is well understood.

‍

What should you do when contacts disagree?

Keep the responses distinct long enough to understand the reasons. Ask what each person expected, what they experienced, and what part of the relationship they are describing. Then decide whether the team faces one shared issue, several separate issues, or a difference in priorities.

‍

Avoid averaging away an important concern. Also avoid treating the most senior person’s view as a complete account of daily service. The practical outcome is a better conversation with the relevant people and a clearer owner for any follow-up, rather than a forced consensus.

‍

A simple contact coverage record

These are examples, not fixed Cliezen categories or a prescribed survey formula. Adapt the record to the account, and connect each response to the person and role that gave it.

‍

When should you review the contact list, and who owns it?

We recommend that the supplier's feedback-program owner review the list twice a year. Check whether response rates are meeting expectations and whether participation has fallen. A decline is a reason to investigate: some contacts may have changed roles or left the client, but the rate alone cannot tell you why. Refresh the names and roles, then consider how to improve engagement with the people whose feedback matters to the relationship.

‍

Ownership and follow-through

The owner should be the person responsible for customer experience on the supplier side. Depending on the company, that person may work in marketing, sales, customer success, or service. Give the review a named owner rather than assuming the account manager will spot every change informally.

‍

Next step: Take one important account and name the people currently invited to give feedback. Can you explain what each person experiences and whose perspective is still absent? Ask the feedback-program owner to review the list and the response pattern at the next twice-yearly check.

‍

Kári Thor is the founder of Cliezen. He holds an MSc degree in Advanced Marketing Management and has 25 years of B2B experience, from tech startups to international companies, in roles spanning marketing, sales and customer experience. At Cliezen, he focuses on helping companies measure, understand and strengthen their customer relationships. Connect with Kári on LinkedIn.