You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The chat interface lacks user acknowledgment or reaction options for messages. This can impact user engagement and reduce the interactive experience within the chatbot. A reaction or acknowledgment feature would allow users to respond to chatbot messages quickly (e.g., with emojis or acknowledgment symbols like thumbs up, thumbs down), making the interface more user-friendly and engaging.
Steps to Reproduce:
Open the chatbot interface.
Interact with the bot by sending or receiving messages.
Notice the absence of any option for reacting to or acknowledging received messages.
Expected Behavior:
Users should be able to react to individual messages in the chat, with options such as emojis or acknowledgment icons to express responses or feedback.
Actual Behavior:
No option exists for users to react to messages, limiting interactivity.
Description
The chat interface lacks user acknowledgment or reaction options for messages. This can impact user engagement and reduce the interactive experience within the chatbot. A reaction or acknowledgment feature would allow users to respond to chatbot messages quickly (e.g., with emojis or acknowledgment symbols like thumbs up, thumbs down), making the interface more user-friendly and engaging.
Steps to Reproduce:
Open the chatbot interface.
Interact with the bot by sending or receiving messages.
Notice the absence of any option for reacting to or acknowledging received messages.
Expected Behavior:
Users should be able to react to individual messages in the chat, with options such as emojis or acknowledgment icons to express responses or feedback.
Actual Behavior:
No option exists for users to react to messages, limiting interactivity.
Screenshots
Any additional information?
No response
What browser are you seeing the problem on?
Chrome
Checklist
The text was updated successfully, but these errors were encountered: