Question Base - Turn Slack into a knowledge base with generative AI

@richard_gao2 Oh, great tip! We will see every single work tool and touchpoint of the workflow of a team be powered up by AI this year. Such exciting times! Thanks for the support, Richard!

@ks1072002 Thank you, Karan!

@ctraganos Oh, thank you, Chris! Hearing from you is always a pleasure! We should so much catch up soon :)

@ctraganos thank you so much for the support Chris!!

@daniel_kovari Thanks a lot, Dániel!

@raghav_shankar @chameli_kuduva One of the teams who used it in BETA connected their sales team to the product team to get fast answers to product specific questions and speed up the resolution time of customer requests.

@realdesigntack Thank you, Vaibhav! That's very sweet of you to say! It's been lots of iterations based on teams' feedback to get to this solution. :)

@yanavlatchkova Iteration loops, back and forth are effort intensive but they makes sense in the end. All the best wishes!

@quinnha Thank you Quinn! We dream each company will have a QB within 5 years so chances should be good ;)

@tomaslau Thanks, Tomas! Back to the craziness. I love it ❤️ Super good questions. 1. Slack works in a way where you are only granted permission on a must-know basis. So people add the Question Base bot to the channels they choose (private or public) and it will then work in them and help capture and share information. We use the permissions from Slack to know if a person has an access to a piece of content or not and thus we stick to the already created permission in the team by selecting who has access to what channels. 2. Well, in general, our target group is fast-growing teams where information gets buried in the stream of conversations. If teams are not at a size where Slack is affordable, it will be a hard upsell for Question Base. Anyway, regarding your use case - QB saves the answers as they get populated so the 90 day limit is not a problem. This is how it will capture it - https://www.loom.com/i/b2393d367... and then you're saving know-how and surpassing the limit. When we scrape the history of a channel, we will just not find that much info. :) But that's a later update anyway. So just try it out and we'd super happy to get your feedback and figure out how to make it even more useful for you and the team.

@manas_sharma Sounds very interesting, Manas. Let's connect on Linkedin and talk :)