Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slack: add support to rephrase user message #1528

Merged

Conversation

mboret
Copy link
Contributor

@mboret mboret commented May 28, 2024

Hello,

We've been utilizing Danswer to actively monitor and respond to user Slack messages, but we've encountered poor results because often the end user doesn't craft their messages with the understanding that a bot is interpreting them.

To enhance the quality of our responses, this Pull Request introduces an additional step that rephrases user messages for clarity before processing.

Copy link

vercel bot commented May 28, 2024

Someone is attempting to deploy a commit to the Danswer Team on Vercel.

A member of the Team first needs to authorize it.

@mboret mboret force-pushed the feat/add_slack_rephrase_message branch from 32897da to 8c59334 Compare May 29, 2024 08:12
Copy link
Contributor

@yuhongsun96 yuhongsun96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you share some examples of where this was not performing well without and now does a good job?

@yuhongsun96 yuhongsun96 merged commit a0e10ac into onyx-dot-app:main Jun 9, 2024
2 of 4 checks passed
vanabharathiraja pushed a commit to sernddev/docudive that referenced this pull request Nov 28, 2024
* Slack: add support to rephrase user message

* fix: handle rephrase error

* Update listener.py

---------

Co-authored-by: Matthieu Boret <matthieu.boret@fr.clara.net>
Co-authored-by: Yuhong Sun <yuhongsun96@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants