Immediate benefits
Less repetition The bot can summarise your community conversation to save you time filling out forms.
Quicker answers While you wait for official support, the bot will suggest relevant guides and resources that might solve your problem right away.
Smoother experience Our goal is to help you without making you jump through hoops between our community, and official support channels.
Same experience for staff Service agents receiving tickets would do so in the same way, with the same (or more) user information, and no workflow disruptions.
Part of the diagram for our prototype.
Feature Roadmap: Beyond the MVP
Content recommendations from our vector database
- While users wait for official support, RØDEBot will proactively suggest relevant articles, videos, and community posts that have helped users in the past. This system would use our vector database, so the system would understand the intent behind the query, not just keywords.
- For example, if a user asks, “how to make my mix louder?” the bot might link to a guide on “adjusting levels”, even though there are no exact matches between those two phrases.
- If the content does help, they could close their ticket straight away.
The goal of this feature is that we could solve around 20% of queries before they even reach our service team.
What did we learn from making this all work?
🏠 What I Learned Building the RØDE Community
Community structure:
💜 Community Strategy (Respect helpers, give them tools)
Community content strategy:
🎓 Community Content Strategy (Learn from audience misconceptions)
Using community data:
😎 Using Community Knowledge (Yep, another guy making chatbots)
Creating custom solutions:
🗺️ Creating a Meaningful Community UX (with Discord)
Service design:
🪄 Service Design (Brands compete on user experiences)
Proving it:
📈 Proving It (Result- chart line go up!)
Misc.
🌐 Why Discord? ❔ Further questions for discussion 📜 Footnotes 👋 Meet the team- one other guy