How to collect customer feedback in B2B: eight methods, and the one that explains why
Collect customer feedback in B2B by pairing cheap passive channels like support tickets with scheduled calls. Tickets show where people struggle; calls show why.
The best way to collect customer feedback in B2B is to pair cheap passive channels (support tickets, an in-app link, account notes) with a well-timed short survey and calls you book on purpose. Passive channels tell you where people struggle. Calls tell you why.
Decide what you need to learn, then pick the cheapest channel that can answer it. Two B2B quirks matter. With tens or hundreds of customers, a survey can return too few answers to count, while a handful of conversations covers a real share of your accounts. And the user is often not the person who pays, so you need to hear from both.
A made-up onboarding company
Here is a made-up example: you sell employee onboarding software to 40 mid-sized companies. HR coordinators use it daily and HR directors sign the contract. Some accounts invite every new hire through the product, others still send paperwork by email, and you want to know why.
1. Write the question before you pick a channel
Fill in: "We need to learn ___ so we can decide ___." For the onboarding company: "We need to learn why some HR teams keep using email for paperwork, so we can decide whether to fix the document flow or change onboarding."
That sentence rules channels out. An NPS score won't answer it, and ticket tags only show where people get stuck. Calls with coordinators at the email-heavy accounts will show what they do instead and why.
2. Pick from eight channels by what each can tell you
| Method | Best for | Effort | Watch out for |
|---|---|---|---|
| Support tickets and chat | Where people get stuck, in their words | Low, once tagged | Only hears from people who contact support |
| In-app feedback link | Reactions at the moment of use | Low | Self-selected, often short |
| Short survey after a key event | Direction of sentiment across accounts | Low to medium | Small B2B samples; reasons missing |
| Account check-ins | Renewal risk and priorities of the buyer | Medium | Buyers may not know daily problems |
| Sales call notes | Objections and competing options | Low | Secondhand and summarized |
| Scheduled customer calls | Why something happens and what it costs | Medium to high | Takes time to recruit and run |
| Calls with lost deals and churned accounts | Why people chose something else | High | Hard to book; memories fade |
| Product usage data | What people do, as opposed to what they say | Medium to set up | Shows what, not why |
Four of these need care:
- Support tickets. A team at the UK Government Digital Service built a shared set of ticket categories by having three people tag the same 50 tickets and compare, then tagged new tickets as they arrived and reported every two to three months. A support queue becomes countable feedback.
- In-app feedback. NN/g describes customer feedback from links, buttons, forms and email as coming from a self-selected sample. Good for spotting problems, unreliable for judging how common they are.
- Surveys. Keep them short and tied to a moment, such as 60 days after launch. If you use NPS, Bain's method is the percentage of 9s and 10s minus the percentage of 0 to 6 answers. With 40 customers and perhaps a few users each, expect few responses and treat changes cautiously. (A big swing can be two people having a bad week.)
- Usage data. NN/g's framework separates "what people say" from "what people do," which are often quite different. In the example, it would show which accounts send documents through the product, and not why the others don't.
3. Book calls for the questions that need a why
Calls are the most useful B2B channel when a decision is at stake, because you can follow up and hear what happened. GOV.UK's interview guidance says interviews can run from 30 minutes to 2 hours (longer gives more detail but is harder to recruit for) and should focus on stories and real examples rather than how things should happen.
For the onboarding company, a first round could be six 30-minute calls: four coordinators at accounts that still email paperwork and two at accounts that don't. Ask each to walk through the last new hire they onboarded, starting from the signed offer. Where did documents go? Who chased signatures? What happened when something was missing? The answer usually shows up in the difference between the groups.
- Invite the user and the buyer separately, since they see different problems. How to interview B2B users, buyers and champions covers the differences.
- Include people who left or never bought. Churned customers and lost deals need their own approach, and a win-loss program makes the lost-deal calls routine.
- Use tested wording. Customer interview questions has past-event questions.
4. Keep everything in one place
Feedback scattered across a help desk, a CRM and three people's notes is hard to use. Pick one place, give every item the same few fields (account, role, date, source, tag, quote) and review it monthly. A simple research repository is enough at this size. To turn the channels into a standing program with owners and a reporting rhythm, see voice of customer programs.
5. Tell people what their feedback changed
When a change ships because of feedback, tell the people who asked for it. People who see feedback lead somewhere are easier to ask next time.
Your next step
Write your one-sentence question, check which channel can answer it, and book the first three calls this week.
If the people you need are not your customers, such as HR coordinators at companies using a competitor, search for people by describing the role (people and talent professionals in HR technology is one example). Instant Expert sends the invitations once you review who it finds, and you pay only for calls that get booked.