Support Insights Podcast

There are a handful of genuinely operational ideas - monthly case-digest posts, proactive pre-release notes with use cases, and gamifying cross-team community participation - but these are surrounded by considerable padding, goal-statement repetition, and generic 'customers want value' language. The insight rate is modest, not dense.

“every customer case or question that we get, we capture that information, track it, catalog it, and each month we have a series of, here are the common questions that we've gotten the previous month”

“since we're sending this out a, uh, week early at this point we're starting to see customers who chime in and say, I'm so excited about this feature”

A few thoughtful framings appear - organising community around outcomes rather than features, and using community as a passive product feedback channel - but most of the thinking (buy-in across departments, community-as-self-service-deflection, customer champions) is well-trodden SaaS community orthodoxy with no contrarian or first-principles challenge.

“People don't buy features, they buy the benefits from those features”

“it's taking feedback from them and using it to make their experience better just organically, not even having to ask questions”

Ben Gardner is a genuine practitioner - VP of Customer Support at a known B2B SaaS company with nine years in the function - and he speaks from lived experience of actually building and launching the community, not theorising. He is not an especially prominent or large-scale operator, and Drift's scale limits the applicability for enterprise listeners.

“I am the VP of Customer Support here at Drift. I've been here for a little over three and a half years running the support team”

“I've been doing this, you know, from a running a support team perspective and working in support for close to nine years now total”

The episode is notably thin on hard numbers: no ticket deflection figures, no community member counts, no engagement rates, and no ROI data - the guest explicitly acknowledges results haven't been measured yet. The only concrete figure offered is a rough headcount comparison, and even page-view improvements are described in vague relative terms.

“we have not yet measured, but what we are looking to measure soon is going to be what is the health score to that customer”

“we have seen more page views in the community on different areas than we used to see in our help documentation”

The host occasionally asks sharp questions - pressing on ticket-volume impact and probing the decision not to hire a dedicated community manager - but consistently accepts vague or deflective answers without follow-up, and litters the conversation with uncritical affirmations that prevent any productive tension.

“Why is it that you set the community up in the way that you did and haven't, say, hired a dedicated person to run the community as a whole?”

“That, uh, is fantastic”