4 ms·

This is great @mrjn. I can tell you from my experience, that this will save people a lot of time by reducing transcribing efforts and facilitating faster lookup

This is great @mrjn. I can tell you from my experience, that this will save people a lot of time by reducing transcribing efforts and facilitating faster lookups. A few questions (haven't tried the product yet) - Is it possible for the bot to summarize on slack, and drop a link to your UI? - does the bot have query / search capability through directly from slack? hopping into another UI at times can make it a poor experience ^ give your product roadmap, I am guessing this may not be on top of your list - how does your bot know when a discussion thread has ended? Is the AI generation more a batch model today? - also does the bot handle merging two threads sharing similar context? A few use-cases I believe this can solve right away - [more from engineering side] often times runbooks/dev solutions for issues can be generated from such discussions/threads. Your tool looks very promising to generate runbooks from slack threads. This kind of fits somewhere inbetween messaging-apps, stackoverflow & documentations (which is how I would use it atleast).

mrjn 3y ago
Hey! 1. I'm working on adding Slack commands to the bot, so you can search, and even directly ask questions off the bot from within Slack. You're right that the need to switch to another website to find information is annoying -- in fact, that's where the full Struct Platform would be of incredible help -- one platform for chat and knowledge capture. 2. We sync the conversations every few hours. At that point, if there was some new chats in a conversation, we re-run the AI. So, it updates the title and summary according to the sum of all the chats the thread has so far. The bot doesn't, but in Struct, we'd allow for a way to merge threads which are similar, or fork a thread which has deviated from the main topic. For engineering, even sales and marketing, this would be amazing! I can think of so many use cases there -- for example, every GitHub issue, every sales deal, every customer issue, all could be threads in Struct, allowing easy communication with all the context readily available. The possiblities are VERY exciting! :-)

mrjn 3y ago

Hey! 1. I'm working on adding Slack commands to the bot, so you can search, and even directly ask questions off the bot from within Slack. You're right that the need to switch to another website to find information is annoying -- in fact, that's where the full Struct Platform would be of incredible help -- one platform for chat and knowledge capture. 2. We sync the conversations every few hours. At that point, if there was some new chats in a conversation, we re-run the AI. So, it updates the title and summary according to the sum of all the chats the thread has so far. The bot doesn't, but in Struct, we'd allow for a way to merge threads which are similar, or fork a thread which has deviated from the main topic. For engineering, even sales and marketing, this would be amazing! I can think of so many use cases there -- for example, every GitHub issue, every sales deal, every customer issue, all could be threads in Struct, allowing easy communication with all the context readily available. The possiblities are VERY exciting! :-)