We're building the first knowledge graph for the enterprise. SkipFlag organizes communication into an intelligent knowledge base that answers questions for you.
@shahab_21 Thanks! Signing up via Slack OAuth will put you on the waitlist while we prep with Slack to let in more teams, let me know your team name and I'll keep an eye on it.
Report
@peteskomoroch Hey Peter, Thanks for the response. Is there a way to get access without connecting Slack? Wanted to see how it works and understand it better before releasing anything to our team on Slack.
@shahab_21 The free plan is currently Slack only, for the Enterprise plans we offer deeper integrations to Confluence, Zendesk, Email, etc. It builds a custom knowledge base from your communication and documents, so we currently require you to link at least one data source.
If this works well and manages to answer more complex queries, this is a huge value add for organizations! Another interesting use case that immediately came to my mind are company wikis. It takes a lot of time to create and maintain them. An approach like SkipFlag could deliver the right information to employees when they have questions.
@emilkabisch definitely, you can think of this as an AI wiki that maintains itself. We always found it a pain to find things in company wikis, and often content was out of date or unclear ownership.
There is a full-fledged document model and WYSIWYG editor at the core of SkipFlag. Users can create "Notes" which are basically rich wiki pages that are autotagged and linked live as you type. Think of it as an AI powered wiki that links across pages itself and organizes those pages so you can find them later.
There is also a deep notion of reputation built into the app based on content that you discuss or write, so you build a reputation for topics based on what you contribute. Users who contribute more relevant information to a note become a kind of "mayor" of the note called a major contributor and their face is highlighted in green. If someone leaves your company, SkipFlag makes the major contributor the next best author.
Report
@peteskomoroch using that metaphor, might this be used in any situation that calls for aggregation, organization, and annotation of content that flows through communications? for example, if a group of policy researchers were discussing some topic over email for years, could past, present and future comms be organized and morphed into a useful reference material? ditto for any realm of collaborative research. that assumes a regular mail server or hosted (gsuite) - not slack, nor jira et al
@passingnotes yes, email history integration is a feature of our enterprise plan. We actually started out by working with email data - then moved on to short slack messages and github comments which are much harder for NLP to parse and understand. We also do autothreading of slack messages and autosegmentation of conversations in slack to form dialogue based documents. Email is easier for algorithms to understand than IRC or slack messaging, because email chains are threaded and people often use longer, more grammatically correct sentence structure in email.
Thanks for hunting us Chris!
SkipFlag uses your existing conversations, support tickets, and other communication to automatically build and update an enterprise knowledge base. It understands the people, topics, and facts within your company to autonomously answer questions.
We're in the process of Slack app store approval, but contact us if you'd like a demo or want to get started using SkipFlag Enterprise with Jira, Zendesk or ServiceNow
Key features:
- Automatically organizes your all your documentation and messages by topic.
- Instantly resolves issues and questions on JIRA, Zendesk, and Slack.
- When unsure of the best answer to a question, SkipFlag's network intelligence quickly and intelligently routes your request to the right person.
- SkipFlag uses deep learning to automatically detect, link and understand internal jargon, turning unstructured data that lies dormant within your email & messaging into a powerful database of facts and relationships.
- SkipFlag detects meaningful exchanges in your organization within Slack, Github, and other systems and summarizes them as conversation cards.
We hadn't planned on this being posted yet, so anyone who signs up a Slack team today will go on our waitlist until we go through the Slack app directory approval process. People who sign up via Product Hunt now will be bumped up higher in the waitlist when we launch.
While you wait, our system will be working in the background to build a custom knowledge graph for your Slack team based on messages from your public Slack channels.
@peteskomoroch excited to see all the progress! Can you speak to any results or outcomes your initial users have experienced? Oh, and where does the name come from?
@chrismessina thanks! We're working with early alpha customers to analyze the impact on their internal service desks and team productivity. SkipFlag can reduce support ticket volume significantly by auto-answering support questions, even when phrased in different ways. We'll update the site with more details when customers are ready to share numbers. The a-ha moment often comes when they search for internal topics or jargon and SkipFlag auto-organizes a knowledge page around the topic.
Regarding the name, a skip flag is an obscure computer science term that had few google results and I had bought the domain name for :)
"skip flag (n.): The thirty-fifth bit of a channel command word which suppresses the transfer of data to main storage."
Basically it is a flag which causes something to not be written to memory. It's a bit of an inside joke, because our mission is to collect, understand and organize all workplace knowledge.
Report
SkipFlag is tackling one of the most challenging questions for an organization: What do we know, and who knows it. @peteskomoroch@sam_shah
This is an incredibly interesting project, even if I am not certain if I entirely understand what it is supposed to do. I hope my comment is helpful. I once ran a small membership site and went through all the emails, support requests and other information. It was a useful and important exercise, and I was able to identify important themes and issues that were arising and important to uses. The workflow was 1. collect data 2. understand information 3. make changes to the app and processes. Not rocket science, but it took time (even it was enjoyable). This app updates a knowledge base which is great, but the superpower for such an app might be to recognise patterns to improve product and processes.
@ebrahimkhalil This is definitely something we've observed as well. We're focusing initially on internal support and sales use cases, but are hearing a lot of demand for product insights as well. At LinkedIn we had a tool called FBtrends that the product team would use to pick up patterns in user feedback like this and prioritize product feature changes based on patterns.
Looks like a cool product. Name is a bit weird. Hopefully it is just something that people accept instead of them trying to figure out what it means. :)
SkipFlag
SkipFlag
What Will Trend
SkipFlag
FundingPath
SkipFlag
SkipFlag
SkipFlag
Osaurus
SkipFlag
Write Invisible
SkipFlag
Summer Bod 2020