How to Facilitate a Customer Advisory Board Call in English

A customer advisory board (CAB) call brings a handful of key customers together to give product direction feedback — a different register from a support call or a sales demo, since the goal is candid strategic input, not resolving a single customer’s ticket. Engineers and product leads who facilitate these calls need English that invites honesty from customers who may be reluctant to criticize a vendor directly.

Opening and Setting Expectations

Set the tone early: this is a working session for honest input, not a presentation to be politely nodded through.

• “Thanks for making time for this — the most useful thing you can do today is disagree with us, not be polite. We’d rather hear hard feedback now than find out after we’ve built the wrong thing.”
• “We’ll cover three topics today: the roadmap update, a couple of open questions we specifically need your input on, and a review of the commitments from last quarter’s call.”
• “Everything said here is genuinely going back to the product and engineering leadership — this isn’t a box-checking exercise.”

Closing the Loop on Past Commitments

Before asking for new feedback, show that previous feedback was acted on — this is what earns candor.

• “Last time, three of you raised the reporting export limits as a blocker — that shipped in March, and I’d like to hear whether it actually solved the problem or just moved it.”
• “We committed to investigating the API rate limit issue and decided not to change it this quarter — I want to be upfront about that and explain the tradeoff we weighed.”
• “One thing we didn’t get to from last quarter is the SSO configuration complexity — that’s still open, and I don’t want to pretend otherwise.”

Drawing Out Honest Feedback

Customers often soften criticism in a group setting — use direct, low-pressure prompts to counter that.

• “If you were in our shoes, what’s the one thing on this roadmap you’d deprioritize to make room for something else?”
• “I’m going to ask a blunt question: is there anything here that, if we shipped it exactly as described, would actually disappoint you?”
• “Feel free to disagree with each other too — if two of you want opposite things, that’s useful for us to hear, not a problem to hide.”

Handling Disagreement Between Customers

When customers want conflicting things, acknowledge the tension openly rather than picking a side in the room.

• “It sounds like there’s a real tension here — [Customer A] wants more configurability, and [Customer B] wants fewer options and stronger defaults. We’ll need to make a call on that, and I’ll follow up on how we’re thinking about it.”
• “That’s a useful disagreement to surface — it tells us this isn’t a simple ‘everyone wants X’ situation, and we should be more careful about generalizing from one customer’s request.”

Closing With Concrete Follow-Up

End with specific commitments and a stated timeline, not a vague “thanks for the input.”

• “Here’s what I heard as the top three themes today: export flexibility, SSO simplification, and pricing transparency. I’ll circulate detailed notes by Friday.”
• “On the SSO point, I can’t commit to a timeline today, but I will come back to this group specifically, not just in the general release notes, once we’ve scoped it.”
• “Same time next quarter — and I’ll open with a direct progress update on each of today’s action items before we move to new topics.”

Vocabulary Reference

Key Takeaways

• Set the tone explicitly as a working session for disagreement and candor, not a polite presentation.
• Close the loop on prior commitments before asking for new feedback — this is what earns genuine candor over time.
• Use direct, low-pressure prompts (“what would you deprioritize?”) to counter customers softening criticism in a group.
• Acknowledge conflicting customer requests openly rather than picking a side in the room.
• End with specific, dated follow-up commitments, not a vague thank-you.