Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / When Community Members Become Your Best Customer Support Team
Transcript
- Lucas: If these marketing conversations have sparked ideas you've actually used, that's exactly what we hope for. But here's the thing — we deliberately keep this show free of ads. No sponsors interrupting the flow. If that approach resonates with you, and you want to help keep it going, the simplest way is buy me a coffee dot com slash fexingo. That's it. No perks, no tiers. Just knowing this matters to you. Luna: Yeah, it's a small thing that adds up. And it keeps us honest — no one telling us what to talk about. Lucas: Exactly. So, speaking of communities doing real work — let's talk about something we haven't covered yet: turning your community into a customer support army. Luna: Oh, this is a good one. I've seen it done badly more often than well. Lucas: Right. And the difference between a helpful peer support channel and a chaotic mess is pretty stark. So I want to look at a specific case — a mid-size SaaS company, about 500 employees, selling a project management tool. They launched a Slack community for power users two years ago. Luna: And it turned into a support channel almost by accident? Lucas: Exactly. At first it was just product chat — feature requests, tips. But people started asking 'how do I do X?' and other users answered. Within six months, about 60 percent of all support questions in the community were being answered by other members. Luna: That's huge. But I bet the official support team was nervous — losing control of the answers, maybe misinformation spreading. Lucas: They were. And they had a real problem: ticket volume was growing 20 percent quarter-over-quarter, and they couldn't hire fast enough. So they decided to lean into the community support trend deliberately. Luna: What was the first step? Lucas: They created a dedicated #help channel and set up a simple reputation system. Every time a community member answered a question, they'd get a 'helper' role. After ten verified answers, they'd get a 'senior helper' role. And the senior helpers got a special badge in the community and a quarterly thank-you call with the VP of Support. Luna: No monetary reward? Lucas: None. And that was intentional. They tested small gift cards early on and found it actually reduced participation — people felt weird about being paid to help peers. Recognition was more motivating. Luna: That's a counterintuitive finding. I would have guessed the opposite. Lucas: Same. But the data was clear. They also built an escalation path. If a question went unanswered for two hours, a bot would flag it to the official support team. That kept response times fast without pressuring volunteers. Luna: So the official team still monitored, just from a distance. Lucas: Right. And they held weekly 'community office hours' — a 30-minute Zoom where any community member could drop in and ask questions directly to a product manager or a support lead. That became a huge trust builder. Luna: I love that. It makes the volunteers feel like insiders, not unpaid labor. Lucas: Exactly. After a year, the results were striking: overall ticket volume dropped 40 percent. Average first-response time went from four hours to 12 minutes. And customer satisfaction scores actually increased by five points. Luna: Wait — satisfaction went up even though they were getting answers from other users instead of the company? Lucas: Yeah, because the peer answers were often more practical. They'd say things like 'here's the workaround I use' instead of 'our team is working on a fix.' That real-world context resonated. Luna: Okay, but what about the risks? Burnout among the top volunteers, or someone giving bad advice? Lucas: Both happened. On burnout, they tracked that the top 10 helpers were answering 30 plus questions a week. So they introduced a 'helper cap' — once you hit 20 answers in a week, a bot would encourage you to take a break Luna: Did that annoy anyone? Lucas: A few. But they framed it as 'we care about you not burning out' and most appreciated it. On misinformation, they had community moderators who could flag a wrong answer and the support team would jump in within 30 minutes. Luna: So they kept a light moderation touch rather than pre-approving every answer. Lucas: Exactly. Pre-approval would kill the speed and the authenticity. They relied on the community to self-correct, which it usually did. Luna: I'm thinking about smaller brands. Could a 50-person community pull this off? Lucas: Probably not as a full support channel. But you could have a 'power users' Slack where a handful of loyal customers answer questions during business hours. The key is the same: clear expectations, recognition, and an easy way for the company to step in. Luna: So the size of the community matters less than the structure around it. Lucas: Exactly. And one more thing — they measured the ROI. They calculated that the volunteer community saved them roughly the equivalent of three full-time support hires. That's about $180,000 a year. Luna: Wow. And all they invested was a part-time community manager and some Zooms. Lucas: Right. And the volunteers weren't just saving money — they became more loyal customers themselves. The churn rate among active helpers was less than 2 percent, compared to their average of 7 percent. Luna: That's the hidden upside. People who give support feel more invested in the product. Lucas: Exactly. So if you're thinking about starting something like this, the takeaway isn't 'throw up a Slack channel and hope.' You need the reputation system, the escalation path, the office hours, and the burnout protection. Luna: And the mindset that your customers can be partners, not just users. Lucas: Exactly. That's the real shift.