Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Replaced Customer Support Costs
Transcript
- Lucas: You know that moment when you're trying to cancel a subscription or troubleshoot a bug, and you just wish you could ask someone who's already been through it? Luna: All the time. I usually end up on Reddit or some forum before I even think about calling support. Lucas: Right. And that instinct — that's exactly what some brands are now deliberately cultivating. They're building communities specifically to offload support questions. And it's not just about saving money, though that's a huge part of it. Luna: How huge are we talking? Lucas: Let me give you a concrete number. I was looking at a mid-size SaaS company — they have about 50,000 users, mostly small business owners. They launched a private community on Discourse about two years ago. It's now 1,200 active members. And within six months, their support ticket volume dropped by 40 percent. Luna: Forty percent? That's massive. What kind of support issues were they seeing? Lucas: Mostly tier-one stuff — how do I reset my password, how do I integrate with X tool, that sort of thing. The kind of question that one experienced user can answer in thirty seconds. Before the community, those questions were all hitting the support team. After, the community answered them for free. Luna: And I'm guessing that didn't just save money on tickets — it probably also improved response time for the remaining tickets, right? Lucas: Exactly. The support team could focus on the more complex issues. The company estimated they saved about $300,000 annually in support costs. That's not small change for a company their size. Luna: Three hundred thousand — that's like two full-time support hires. So the community basically paid for itself and then some. Lucas: Yeah. And this isn't an isolated case. There's a 2025 Gartner report that looked at companies with active peer-support communities, and they found a 25 percent reduction in ticket volume within the first year on average. That's across industries — SaaS, e-commerce, even hardware. Luna: But I wonder — that model works really well for a product with a passionate user base. What about something more utilitarian, like a utility billing app? Would people really hang out there to answer questions? Lucas: Fair point. The community needs a certain level of user investment. But even for more boring products, you can create incentives — like reputation points, badges, early access to features. Some companies gamify the whole thing. And the payoff is real. Luna: So what's the catch? Because there's always a catch. Lucas: Moderation. You can't just set up a forum and hope it works. You need a dedicated community manager — someone who seeds conversations, answers the unanswered questions, and keeps the tone constructive. That person is a cost. But compared to a full support team, it's much cheaper. Luna: And there's also the risk of bad advice spreading. If a power user gives incorrect information, it can cause real problems. I've seen that happen in some Slack communities. Lucas: True. That's why best practices include having a 'verified' or 'staff' tag for official answers, and sometimes a knowledge base that integrates with the community. Companies like Atlassian and Salesforce have been doing this for years. Their communities are massive — thousands of users helping each other, with staff chiming in on the tricky stuff. Luna: And I bet the community also becomes a feedback loop. The support team learns what issues keep coming up, and they can feed that back to product. Lucas: Absolutely. That's actually one of the hidden benefits. The community becomes a real-time focus group. You see what features people are struggling with, what they're asking for. That's hard to get from a support ticket — there's no conversation, just a one-off request. Luna: It's almost like the community replaces not just support but also some of the product research function. We did an episode on that a while back — a 300-person Discord replacing a product research team. Lucas: We did. And this is a similar principle, but with a different output. Instead of research insights, you're getting reduced support costs and faster resolution times. And it scales beautifully — as long as you keep the community healthy. Luna: Right. So what's the first step for a brand that wants to try this? Do you need a massive user base? Lucas: Not necessarily. The SaaS company I mentioned started with just a few hundred invite-only members. They identified their most active and helpful users — the ones who were already answering questions on Twitter or in their support inbox — and invited them to a private group. That core group then grew organically. Luna: So it's about finding those superusers first. Lucas: Exactly. And then giving them a space where they feel valued. A lot of them genuinely enjoy helping others — it's about community, not just cost savings. Speaking of which, this is a good moment to mention something. If these marketing conversations have sparked something you've actually used in your own work — a tactic, a framework, even just a way of thinking — and you'd like to support the show, it's a huge help. You can buy me a coffee at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. Keeps the show ad-free and lets us keep digging into these specific case studies. Luna: Yeah, and it really does make a difference. It's how we can spend time on deep dives like this one instead of rushing through. So thank you to anyone who's done that. Lucas: Alright, back to the community. One thing I want to highlight is the platform choice. Discourse is great for long-form discussions, but some brands prefer Slack or Discord for real-time chat. The key is matching the format to the type of support questions you get. Luna: For example, if most questions are quick and need instant answers, a chat platform might be better. But if they're more detailed, a forum-like structure with threaded conversations works well. Lucas: Exactly. The company I mentioned uses Discourse with a Q&A category. Users can mark the best answer, so the next person with the same question finds it immediately. It's like building your own internal Stack Overflow. Luna: And that also reduces duplicate questions, which is another efficiency gain. Lucas: Right. So if you're a marketer or a product leader thinking about this, start small. Find your top ten users. Invite them to a private space. See what happens. The data from Gartner and these case studies suggests the ROI is real — but it only works if you invest in the community, not just the technology. Luna: And maybe that's the real lesson. The community isn't a cost center — it's an asset that, if managed well, pays for itself and then some. Lucas: Exactly. I think we'll see more brands move in this direction, especially as AI tools make it easier to surface existing answers. But the human element — the willingness to help — that's irreplaceable.