Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Cut Customer Support Costs by 30 Percent
Transcript
- Lucas: So there's this moment every community manager knows — the release goes live, and suddenly your support inbox is a firehose. One SaaS company I was digging into saw tickets jump by 40 percent in a single week after their spring update. And instead of hiring more agents, they did something smarter. Luna: Let me guess — they turned to their community? Lucas: Exactly. They had a few super-users who were already answering questions in their Discord before the support team even woke up. So they formalized it. They created a 'community champions' program — a small group of volunteers who got early access to features, a private channel with the product team, and a clear escalation path. Luna: And that actually moved the needle on tickets? Lucas: It did. Within one quarter, they cut support volume by 30 percent. Average response time went from twelve hours to under forty-five minutes. And the kicker — customer satisfaction scores went up, not down. The champions were often faster and more empathetic because they'd been in the same boat. Luna: That's a big deal. But how do you train volunteers to handle support without them giving out wrong info or getting burned out? Lucas: That's the real question. They had a structured onboarding — a two-week training period where champions shadowed support agents, had a clear handbook, and took a quiz before they went live. And they had strict escalation rules: anything about billing, security, or data privacy went straight to the paid team. Champions handled the 'how do I do this' stuff, not the 'why is my invoice wrong' stuff. Luna: So they kept the risky stuff out of volunteer hands. That's smart. But what kept the champions motivated? Early access is nice, but it's not exactly a salary. Lucas: Right, and that's where a lot of these programs fail. They started with a points system — badges, leaderboards, that kind of thing. But the thing that actually stuck was the private channel with the product team. Champions got to ask the PMs 'why is this feature built this way?' and get a real answer. That insider access was worth more than any swag. Luna: That makes sense. People volunteer because they feel invested. But did they worry about the champions getting overwhelmed? I mean, the whole point was to reduce load on the support team, but you could just shift the burnout onto volunteers. Lucas: They had a few safeguards. First, champions could set their own hours — no minimum, just a weekly goal of maybe three or four hours. Second, they had a dedicated community manager who checked in with each champion weekly, just a quick DM to see how they were doing. And third, they had a 'take a break' option — champions could pause their status for a week without any penalty. That flexibility kept people around longer. Luna: I love that. So what was the actual financial impact? You said they cut support costs by 30 percent — what does that look like in dollars? Lucas: So they did a rough calculation. Their average cost per ticket, fully loaded, was about twelve dollars. They were handling around five thousand tickets a month before the program. After the champions stepped in, they deflected about fifteen hundred tickets a month. That's roughly eighteen thousand dollars a month in savings — over two hundred thousand a year. And that's not even counting the avoided hiring costs. Luna: That's a real number. But I'm wondering — did the champions ever give wrong answers that made things worse? Lucas: They did have a few bumps. One time a champion told someone a feature was coming in the next release when it wasn't. That created a mini controversy in the community. So they added a 'confirm before you answer' rule for anything about roadmap or timelines. Champions had to check with the product team before posting anything about future plans. That cut down most of the misinformation. Luna: So it's not just about letting volunteers loose — you need clear boundaries and a feedback loop. Lucas: Absolutely. And they also measured quality. They had a weekly review where support agents tagged any champion answer that was flagged as incorrect or unclear. Then the community manager did a one-on-one with that champion to walk through the right answer. It wasn't about punishment — it was about learning. And they saw the error rate drop from about five percent in the first month to under one percent by the third month. Luna: That's a really solid system. What about the champions' perspective? Did they feel like they were doing the company's job for free? Lucas: That's the tension, right? They interviewed a few champions later, and the common thread was that they didn't feel exploited — they felt like insiders. They got to know the product roadmap before anyone outside the company, they had direct lines to the founders, and they genuinely enjoyed helping people. But the company was careful not to ask for more than a few hours a week, and they made sure to say 'thank you' in tangible ways — like sending a handwritten note or a small annual gift. Luna: It sounds like the key was keeping it reciprocal. The champions gave time, the company gave access and appreciation. And that kept it sustainable. Lucas: Exactly. And the interesting thing is, this didn't just help support — it created a group of super-informed superfans who started creating tutorials and guides on their own. The community became a content engine, not just a support channel. That's the multiplier effect you don't get from hiring more agents. Luna: So if someone listening wants to try this, what's the first step? Where do they even start? Lucas: Start small. Pick your top five most active, helpful community members — the ones who are already answering questions in the open channels. Invite them to a private space, maybe a Slack channel, and ask if they'd be interested in a more formal role. Give them a simple one-page guide with do's and don'ts, and set up a weekly check-in. Don't build a whole program overnight. Just test it with a few people for a month and see how it feels. Luna: That's practical. And what about the risk of creating a clique or making other members feel left out? That's a common fear. Lucas: Yeah, that's real. They handled it by being transparent — anyone could apply to be a champion, and the criteria were public: helpfulness, accuracy, and a positive tone. They also rotated champions every six months to avoid burnout and keep the group fresh. So it wasn't a closed club; it was a rotating door. That kept the community from feeling like there was an elite tier. Luna: That makes sense. So, before we wrap up, I know we've been talking a lot about the mechanics — but is there a bigger lesson here about community and business value? Lucas: I think the bigger lesson is that a community isn't just a marketing channel — it's an operational asset. When you give your most engaged members a little structure and trust, they can do things that would cost you a fortune in salaries. And they do it because they care. That's the thing you can't buy. Luna: Well said. And if you're listening and you've started something like this, we'd love to hear how it goes. Lucas: Absolutely. And hey — if you've gotten value from these conversations, and you've actually used a tactic we've talked about, this is the part where we gently remind you that listener support is what keeps this show going ad-free. Buy me a coffee dot com slash fexingo, if you've gotten something out of it. Luna: Yeah, it really makes a difference. A couple of dollars a month genuinely keeps the lights on. Lucas: Anyway — back to that support program. One thing I didn't mention is that they also used the champions to build a searchable knowledge base. Every good answer got documented and turned into a help article. So over time, even fewer tickets came in because people could find answers themselves. That's another layer of deflection that compounds. Luna: So the community is not just answering tickets — they're writing the documentation. That's a huge win. Lucas: Right, and that knowledge base became a recruiting tool too. They published a few of the top articles on their public blog, and it drew in new users who appreciated the depth. So the community support loop fed back into acquisition as well. Luna: I love when one thing does double duty. So if someone wants to try this, what's the one metric they should track first? Lucas: I'd say track the percentage of tickets that get resolved by a champion without escalation. If that number is above twenty percent after a few months, you're on the right track. And keep an eye on customer satisfaction scores at the same time — you don't want to cut costs at the expense of quality. Luna: That's a clear goal. And I guess the final takeaway is that community support isn't just about saving money — it's about building a deeper relationship with your most passionate users. Lucas: Exactly. When they're invested in your success, they become your best advocates. And that's worth more than any support ticket deflection. Thanks for listening, and we'll catch you next time.