Earlier quoted context omitted.
No sure if they would come up with that in the nearest future. Maybe just adding OpenAI / ChatGPT - it's possible, but I don't think they'e add contextually intelligent bots that would answer queries from your knowledge base.
Right, you should try tapping to old conversation history in these support desk and it would make a good difference on the replies. Didn't see any fine-tuning in the website or docs - do you have plan for these ? I am afraod just langchaining would not make it completely context aware.
Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
31–40 of 117 posts
Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#32Earlier quoted context omitted.
Don't fully disagree but the reason I would care less in this case is I assume most/all of what you would be feeding it is non-sensitive documentation.
I don't think that matters? Sensitive could be just discussing designs, outages, hiring, interview feedback? There's a lot of stuff in the average Slack account people don't want on the internet, let alone in a LLM which will potential expose it to the entire world? Maybe companies like Slack will release integrations natively so it won't matter so much.
Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#33Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#34Hey, uh, real quick Vasyl, could you click on all the images below that contain a stoplight?
Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#35Hey Everybody! We are super stoked to announce present you IngestAI today. It is the fastest way to build contextually intelligent ChatGPT-like bots within your own WhatsApp, Slack, or Discord to answer queries from your knowledge base, documentation, or educational materials. IngestAI is a very useful tool for a diverse range of businesses that have company knowledge base or customer support. IngestAI can save their…
Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#36Privacy policy: > We will not use or share your information with anyone except as described in this Privacy Policy. ... > We want to inform our Service users that these third parties have access to your Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose. Arreeee they? So let me get this strai…
Probably gonna get downvoted for this but people on HN take the Privacy Policy of brand new websites way too seriously. This is probably some template they downloaded from the web, not some sly document they had their nefarious lawyers put together.
Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#37Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#38Privacy policy: > We will not use or share your information with anyone except as described in this Privacy Policy. ... > We want to inform our Service users that these third parties have access to your Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose. Arreeee they? So let me get this strai…
Don't fully disagree but the reason I would care less in this case is I assume most/all of what you would be feeding it is non-sensitive documentation.
Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#39Re: Show HN: IngestAI – NoCode ChatGPT-bot creator from your knowledge base in Slack
#40Earlier quoted context omitted.
I don't think that matters? Sensitive could be just discussing designs, outages, hiring, interview feedback? There's a lot of stuff in the average Slack account people don't want on the internet, let alone in a LLM which will potential expose it to the entire world? Maybe companies like Slack will release integrations natively so it won't matter so much.
Who is feeding interview feedback to a third party regardless if its IngestAI or not?