Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a 500-Member B2B Community Used Ambassador Roles to Boost Active Participation by 60 Percent
Transcript
- Lucas: So Luna, we've talked a lot about getting people into communities, but there's a different challenge: what happens after they join? The typical pattern is you get a spike of activity, and then it plateaus. Most members just lurk. Luna: Right, and we've covered lurkers before—that they're not necessarily bad. But if you want to deepen engagement, you need to move people from passive to active. What's a concrete way to do that? Lucas: I want to talk about ambassador programs. Not the typical influencer thing where you give them a discount code. I mean structured, volunteer leadership roles inside a community. There's a B2B SaaS company—let's call them 'ProjectFlow'—with a Slack community of about 500 members. They were stuck at about 15 percent weekly active users. So they launched a three-tier ambassador program. Luna: Three tiers? That sounds a little corporate. How did they keep it from feeling like a hierarchy? Lucas: Good question. The tiers weren't based on status—they were based on contribution type. Tier one was 'News Shapers'—members who agreed to share one industry article per week and start a discussion around it. Tier two was 'Connectors'—people who would introduce two members who hadn't met yet each month. Tier three was 'Mentors'—experienced users who would answer questions from newcomers in the first week. Luna: So it's role-based, not rank-based. That makes sense. How did they recruit ambassadors? Lucas: They didn't open applications. The community manager identified the top 10 percent of contributors by message volume and reaction score—people who were already adding value—and personally invited them to a private channel called 'the crew.' She gave them a very clear description: you're not a moderator, you're a catalyst. Your job is to spark activity, not police it. Luna: Interesting. And what was the incentive? People are busy. Lucas: No monetary reward. No swag. The only perk was early access to product updates and a quarterly video call with the CEO. The real incentive was recognition and a sense of ownership. The community manager framed it as: 'I can't make this community great alone. I need leaders among you.' And it worked. Within three months, weekly active users jumped from 15 percent to 24 percent—that's a 60 percent increase. Luna: Sixty percent—that's huge. But did the quality of conversation stay high? Sometimes when you push for volume, you get low-effort posts. Lucas: They measured that. Messages per active member actually went up 35 percent, not down. And the number of threads with at least three replies rose too. The News Shapers were curating high-quality content, which gave others something to react to. The Connectors were directly pairing people who had complementary needs, which led to deeper conversations. The Mentors reduced the time it took for new members to get their first answer—from 12 hours down to about 45 minutes. Luna: That's impressive. I want to dig into the Connector role—how did they actually do the introductions? Was it manual? Lucas: Pretty manual at first. The Connectors had a shared Google Doc where they'd list members they'd noticed and why they might connect. Then they'd drop an @-mention in a thread like: 'Hey @alex, you were asking about API integrations—@jordan just built one. Mind if I connect you two?' Very personal, no automation. The community manager estimated each Connector spent about 20 minutes a week on this. But the payoff was huge: members who were introduced via a Connector had a 70 percent higher retention rate after 90 days. Luna: That's a key metric—retention tied directly to that human touch. Now, what about burnout? These are unpaid roles. Did any ambassadors drop off? Lucas: Yeah, some did. About 20 percent rotated out in the first six months. The community manager handled it well: she had quarterly check-ins where ambassadors could step down without guilt, and she'd replace them with new high-contributors. She also encouraged ambassadors to take a month off if they needed it. The key was that the program felt like a volunteer gig, not a job. Luna: That's a good lesson. Keep it light, keep it voluntary. Now, you mentioned they tracked time from sign-up to first ambassador interaction. Why was that metric so predictive? Lucas: Because if a new member got a personal welcome or a connection from a Mentor within the first two days, they were six times more likely to post within the first week. And that early posting behavior is the strongest predictor of long-term retention for communities. So the ambassador program directly improved that onboarding experience. Luna: You know, hearing this makes me think about how many community managers spend all their time moderating instead of cultivating leaders. This is a smarter use of energy. Lucas: Exactly. And it's scalable. You don't need to be the one answering every question. You create a structure where the most engaged members naturally become the hosts of the community. Luna: If today's episode gave you a concrete idea you might try—like setting up a simple Connector role—this is exactly the kind of conversation that stays ad-free because listeners support it directly. If that's something you value, you can buy me a coffee dot com slash fexingo. Seriously, those small contributions add up and keep us independent. Lucas: Absolutely. We don't do sponsorships or ads—that's a choice. So if you've gotten useful insights from this show, that's the way to keep it going. No pressure, just gratitude. Luna: Alright, back to the ambassador program. One thing I'm curious about: did they ever have a situation where an ambassador became too controlling? Like, gatekeeping conversations? Lucas: It happened once. A Connector started only introducing people who matched his own interests, ignoring others. The community manager had to gently remind him that the goal was diversity of connection, not personal networking. She rotated him to a News Shaper role, which fit better. So you do need to monitor, but it's manageable. Luna: That makes sense. So the community manager still has to be the shepherd. But the ambassadors do the heavy lifting. Lucas: Right. And the data from this program was so compelling that they now have a 10-minute onboarding session for every new ambassador where they share the core philosophy: 'You are not a moderator. You are a host. Your job is to make others feel welcome and seen.' That phrase alone shifted the culture. Luna: I love that distinction—host vs. moderator. It's less about rules and more about hospitality. So for our listeners, the takeaway might be: look at your current top contributors, invite them to a private channel, and give them one specific action to take each week. Start small. Lucas: Exactly. Don't try to build a 10-person program overnight. Start with three ambassadors. Pick one role—maybe News Shaper—and see if it lifts engagement. Measure before and after. That's what ProjectFlow did, and it paid off. Luna: And if you do try it, let us know how it goes. That's all for this episode—thanks for listening. Lucas: Yeah, thanks. See you next time.