Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Cut Customer Support Tickets by 40 Percent
Transcript
- Lucas: So we talk a lot on this show about brand communities as engines for product feedback, loyalty, even revenue. But there's another use case that I think gets less attention than it deserves: cutting your customer support tickets by a serious margin. Luna: I love this angle. Because support is expensive. And if a community can deflect even a chunk of those tickets, that's a direct line to savings. Lucas: Exactly. And there's a case I want to walk through today — a mid-sized SaaS company, call them CloudMetrics, about 500 employees, B2B analytics. They launched a private Slack group for their top 200 power users. No grand ambitions at first, just a place to share tips. Luna: And what happened? Lucas: Within six months, their support ticket volume dropped by 40 percent. Their CSAT scores actually went up. And the community wasn't even officially positioned as a support channel. It was just that users started answering each other's questions before the company could get to them. Luna: If those conversations have sparked something you've actually used in your own work — maybe a community strategy, a moderation tweak, something you tried that worked — that's exactly what keeps this show going. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's what makes it possible to keep producing episodes like this one, ad-free. No pressure, just if it's useful to you. Lucas: Yeah, seriously. Knowing the show helps someone on the ground is the whole point. So back to CloudMetrics — the key mechanic they stumbled into was what I'd call 'ticket deflection by design.' Luna: How did they design it? Was it just organic or did they nudge it? Lucas: A bit of both. They set up a dedicated channel called #get-help. The rule was: before submitting a ticket, post your question here first. The community agreed to a shared norm — answer if you know, tag a community manager if you don't. And the company made sure top contributors got early access to new features and occasional swag. Luna: So you incentivize the helpers, not just the askers. Lucas: Right. And they tracked it. They used a simple bot that counted how many times a question in #get-help never became a ticket. That's your deflection rate. For CloudMetrics, it hit about 40 percent within three months, and then stabilized. Luna: Is there a risk that the community starts giving bad advice? Or missing edge cases? Lucas: Absolutely. That's the biggest concern. CloudMetrics handled it by having a community manager monitor the channel actively. If a solution was incomplete or risky, they'd chime in with a correction. They also pinned a 'verified answers' thread. But they were lucky — their power users were genuinely knowledgeable. Luna: So you need the right crowd. Not every community is going to have that expertise. Lucas: True. But you can cultivate it. Another company I looked at, a CRM platform called SalesFlow, took a different approach. They opened a community forum to all users, not just power users, but they had a 'trusted contributor' badge. Only users with a certain track record could answer. That created a quality filter. Luna: And did they see similar deflection numbers? Lucas: Not as high — about 25 percent. But their support team was also smaller, so even 25 percent was meaningful. The interesting thing is that both companies saw a spike in customer satisfaction scores after launching the community. The theory is that peer answers feel more relatable, less scripted. Luna: That makes sense. There's a trust factor. 'Another user just solved my problem in two minutes' feels better than 'Your ticket is number 4523 in the queue.' Lucas: Yeah. And it's not just about speed. It's about depth. Power users often give context — 'I had the same issue, here's what actually fixed it' — whereas support might give the official workaround. The community adds the 'real world' layer. Luna: But what about the cost? Running a community isn't free. You need moderation, maybe a platform fee. Lucas: CloudMetrics calculated that each deflected ticket saved them roughly $15 in support labor. Their community costs — Slack subscription, community manager half-time, bot maintenance — came to about $3,000 a month. They were deflecting around 1,200 tickets a month. That's $18,000 in savings. Net positive by a long shot. Luna: So the ROI is clear if you have volume. What about smaller companies? Lucas: It scales. Even a company with 100 tickets a month could save $1,500. The key is to start small. You don't need a full community platform. A Slack group or a Discourse forum works. The important thing is the culture: encourage helping, reward helpers, and make sure the community doesn't become a dumping ground for complaints. Luna: What about the downside? I've heard of communities where power users burn out from answering too many questions. Lucas: That's real. CloudMetrics avoided it by limiting the number of top contributors to about 20, and they rotated. They also gave them direct access to product managers, so answering questions wasn't just charity — they got influence. And they had a clear escalation path: if a question went unanswered for two hours, it automatically became a ticket. Luna: So you protect the helpers from being overwhelmed. Lucas: Exactly. And you protect the customers from getting stuck. The community is a supplement, not a replacement for support. The companies that fail are the ones that treat it as a way to cut headcount. That never ends well. Luna: I want to ask about measurement. How do you know if it's actually working? Beyond ticket deflection. Lucas: Good question. CloudMetrics tracked three metrics: deflection rate, average time to first response in the community versus via ticket, and CSAT for community-resolved issues. They also surveyed users quarterly to see if they felt the community was helpful. The data showed that community-resolved issues had a CSAT of 4.8 out of 5, versus 4.2 for regular support. Luna: That's a significant gap. Lucas: It is. And it held across segments. Even new users who were initially skeptical ended up preferring the community for simple questions. The key is to make it easy to find — put the community link right next to the contact form. Luna: So it's almost like a triage layer. Simple stuff goes to community, complex stuff goes to support. Lucas: Exactly. And that actually makes support more efficient too. They get fewer tickets overall, and the ones they do get are more complex and interesting. That improves agent morale, reduces turnover. There's a ripple effect. Luna: I hadn't thought of that. So the community doesn't just save money, it makes the support team better. Lucas: Right. And the community members themselves become more loyal. CloudMetrics saw that top contributors had a 95 percent retention rate, compared to 80 percent for the average user. Helping others creates a sense of ownership. Luna: That's a powerful argument for any brand community manager. You're not just building a forum; you're building a support multiplier. Lucas: Exactly. And the best part is, you can start today. Pick a channel, invite your most engaged users, set a simple norm: ask here before you file a ticket. See what happens. Worst case, you learn something. Best case, you cut your tickets by 40 percent. Luna: I'm going to try that with a client actually. Start small, measure everything. Lucas: Let me know how it goes. If it works, maybe we'll do a follow-up episode on scaling it.