Skip to content

Feedback Mechanism in Search AI

The feedback mechanism in Search AI plays a crucial role in evaluating and improving the quality of answers delivered by the application. It allows end users to express their satisfaction with a response through a simple thumbs up or thumbs down action, which can be captured either via the Web SDK or through the public API.

Note

The feedback mechanism mentioned here is different from the feedback surveys that can be created in XO. It is specifically designed to capture user responses related to answer relevance and accuracy within the Search AI experience.

Enabling Feedback Mechanism

To enable the feedback mechanism in answers displayed in the web SDK, go to the Answer Generation page and enable the Feedback Configuration.

alt_text

When a user interacts with a response by giving it a thumbs up or down through the SDK or via the public APIs, the feedback is recorded and associated with that specific answer.alt_text

This data is then shown in the Answer Insights page, providing administrators and content teams with a clear view of how well responses are resonating with users.

In cases where an answer receives both positive and negative feedback, the system highlights the majority sentiment. For instance, if an answer gets 20 feedback entries with 16 positive and 4 negative, the feedback is displayed in green with a count of 16, indicating a favorable user experience.

alt_text

To view individual feedback on a query, click the query. It navigates to the Answer Summary page that lists all the answers that the users have received on the query, along with the feedback on the answer.

alt_text

Click View Details link for any of the answers to view the user comments along with the feedback.

alt_text

To capture the feedback via the APIs, use the Feedback API.

Note

If you implement the Search AI feedback mechanism using SearchAINode, ensure that the searchRequestId is included in the channel response.

  • When the SearchAINode response is directly presented to the user, this is handled automatically.
  • However, if the SearchAINode response is saved in context and later rendered using a custom template, you must explicitly include the searchRequestId in the response. Refer to this to learn more.