Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / Why Brand Communities Are Outperforming Support Tickets
Transcript
- Lucas: So there's a stat that's been rattling around my head all week: a mid-sized SaaS company we've been following cut its support ticket volume by twenty-eight percent in a single quarter, just by moving a chunk of its troubleshooting into a branded community space. Luna: Twenty-eight percent? That's not a rounding error. What did they actually do differently? Lucas: Well, they didn't just spin up a Discord server and hope for the best. They took their top twenty recurring support questions, wrote detailed guides for each, and seeded a community channel where power users could answer follow-ups. Within two months, almost half of all 'how do I do X' tickets were being resolved in the community, often within minutes. Luna: So they essentially outsourced their support to their most enthusiastic customers. Wasn't there a quality problem? I've seen communities where the answers are… well, let's say creative. Lucas: That's the risk, and it's real. But this company built a verification system. They had a 'trusted helper' role that only went to users who'd provided consistently accurate answers, and every community answer had a 'mark as solution' button, which fed into a public leaderboard. The accuracy rate actually went up, not down, because the community itself policed the bad advice. Luna: That's clever. So you're not just offloading support, you're building a self-correcting system. But what about the economics? I've seen the 'community saves money' claim before, but nobody shows the math. Lucas: Let's do the math. This company's average cost per support ticket was about twelve dollars, mostly in agent time. After the community shift, they estimated the cost per resolved issue in the community at roughly two dollars — that's the cost of the community platform, the time spent writing guides, and the occasional swag sent to top helpers. So they went from twelve dollars to two dollars on a meaningful slice of their volume. Luna: That's a six-fold improvement. But you have to wonder, does every company have the kind of passionate user base that'll actually answer strangers' questions at 2 AM? I'm thinking of a typical B2B tool with a hundred users, not a gaming community. Lucas: That's the catch. This works best when you have a dense, engaged user base. But even a smaller community can tackle the 'long tail' of support — the niche questions that stump your own support team. I've seen a company with just three hundred customers run a private Slack group where the founders themselves answer questions, and that's reduced their support load by fifteen percent, with the added bonus of building customer loyalty. Luna: So it's not an all-or-nothing thing. You can start small. But there's another angle: I've noticed that some communities become a 'support graveyard' — people post a question and get no response for days. That would tank your brand, not save it. Lucas: Absolutely, and that's the dark side. A dead community is worse than no community, because it signals that nobody cares. That's why the companies doing this well have a 'response-time SLA' for the community itself. They ensure at least one staff member is active daily, and they have a bot that nudges the thread if it hasn't gotten a reply in twelve hours. It's a delicate balance between organic and managed. Luna: So the community isn't a replacement for support, it's a triage layer. And that changes how you measure success. What metrics are actually being used on the ground? Lucas: The key one is deflection rate — the percentage of people who could have opened a ticket but found an answer in the community instead. These companies track that by asking users 'did this answer your question?' and then linking that community session to the absence of a subsequent ticket. I've seen deflection rates of forty percent in the best cases. Also, they track 'time to first answer' in the community versus average wait time for a ticket. Communities often win by hours. Luna: Hours, huh? That's the killer argument — not just cost, but speed. If I'm stuck on a problem at 10 PM, I don't want to open a ticket and wait until morning. I want to search the community and find the answer instantly. Lucas: Exactly. And that speed has a measurable impact on churn. One company found that users who engaged with the community in their first week had a thirty percent higher retention rate after six months compared to those who didn't. They attribute that to getting unstuck faster and also to feeling a sense of belonging. Luna: Feeling a sense of belonging — that's the kind of thing that makes a customer a superfan. But let's be real, that doesn't happen by accident. What are the deliberate steps to get there? Lucas: First, you need a 'starter library' — a set of evergreen answers to your top questions, written in a human voice, not support-speak. Second, you need a recognition loop. Whether it's badges, leaderboards, or just a monthly shout-out in your newsletter, people contribute when they feel seen. Third, you need to actively invite your best support customers to join the community with a personal note. That doesn't scale, but it seeds the culture. Luna: So it's not about building a big tent, it's about building a campfire. That's a much better image than 'support channel.' Lucas: Right, and it's a campfire that can actually reduce your support costs by thirty percent or more, if you do it right. But there's a cautionary tale here too — I've seen a community that became a breeding ground for misinformation, where a power user was confidently explaining a feature that didn't exist. The company had to step in and correct a thread that was two months old and had been cited in over fifty other threads. It was a mess. Luna: How do you prevent that? I'm guessing you can't moderate every post in real time. Lucas: You have to make accuracy visible. When a staff member marks a solution, the thread gets a little 'verified' stamp. That's a signal for everyone. And you need a 'request clarification' feature so that ambiguous answers get flagged. But you also need to accept that some bad answers will slip through. The key is to correct them quickly and visibly, not to try to be perfect. Luna: That's a healthy mindset. It's the difference between a rigid system and a living one. And I think that's the real takeaway — a brand community is a living thing, not a project you launch and forget. Lucas: And it's a living thing that can genuinely move the needle on your bottom line. We've talked about cost per contact, deflection rates, retention — but there's also the side effect of product feedback. In that same community, the company found a dozen feature requests that became their next quarter's roadmap, for free. Luna: So the community isn't just a support channel, it's a product research lab. That's a pretty good return on investment. Lucas: It is. And it's the kind of thing we explore every week on this show. If these marketing conversations have sparked an idea you've actually used in your own work, that's the kind of thing that keeps us going — and honestly, listener support is what keeps this podcast ad-free. If you've gotten value from what we do, you can buy us a coffee at buy me a coffee dot com slash fexingo. No pressure, just if it's helped. Luna: Yeah, we genuinely love hearing from listeners who've tried something we talked about. It's the best part of this gig. Lucas: Absolutely. Now, back to that company — once they saw the community working for support, they started treating it as a product feature. They embedded the community search directly into their help center, so when a user types a question, they see both knowledge base articles and community threads side by side. That integration is what really pushed the deflection rate from twenty percent to forty percent. Luna: So it's not just 'go to a different place to ask your question,' it's 'find your answer where you already are.' That's the gold standard. Lucas: Exactly. And now there are platforms that do this natively — you can have a community widget that sits on top of your help center, and it pulls in community answers automatically. That's the kind of thing that makes support feel effortless, which is what customers really want. Luna: Effortless — that's the word. And for a marketer, that's a brand promise you can actually deliver on, not just a tagline. Lucas: And it's a promise that compounds. As the community grows, the archive of solved problems grows, and the deflection rate can climb even higher. But you have to keep the community alive — new products, new features, new questions. It's a living asset. Luna: So what's the one thing a marketer should do this week to start moving in this direction, even if they don't have a big community yet? Lucas: Find your top ten support questions, and write a thread for each one — not a formal KB article, but a conversational post. Put them in a public channel, and when a support ticket comes in that matches, link to that thread and ask the customer to try it before opening a ticket. That simple practice can deflect ten percent of your volume in a month. Luna: That's a small step with a real impact. And it's a way to start building that library without a huge investment. Lucas: Exactly. And the next step is to invite your most active customers to contribute. You'll be surprised how many want to help. It's a win-win — they get recognition, you get a community that works. Luna: I feel like we should add one more warning, though. What about communities that become a place where customers complain about your product loudly and publicly? That's a fear I hear from brands. Lucas: It's a legitimate fear, but in my experience, it's actually better to have those complaints where you can see them and respond, rather than scattered across Twitter or Reddit. A community gives you a chance to turn a detractor into a promoter, publicly. And if you're constantly ignoring complaints, that's a systemic issue that will show up anyway. Luna: So it's a radar, not a risk. I like that framing. Lucas: And it's a radar that can give you early warning of product issues before they become support tickets. One company I talked to found out about a bug in their latest release through a community thread three hours before the first support ticket arrived. That's time you can't buy. Luna: Three hours is huge when you're in crisis mode. So communities aren't just a support channel, they're a feedback channel, a product research channel, and a retention machine. Lucas: They're all of those things, and they're becoming a standard part of the marketing stack. I think in a few years, having a community will be as normal as having a help desk. The question is not if, but when you start. Luna: And for our listeners, the when might be now. This week, take that first step. Lucas: That's the takeaway. And if you want to see an example of a community done right, check out the show notes — we've linked to a case study from a company that started just like you'd start, with a simple Slack channel and a handful of power users.