{"id":4441,"date":"2022-08-17T11:51:10","date_gmt":"2022-08-17T11:51:10","guid":{"rendered":"https:\/\/multisite.korebots.com\/SearchAssist\/?p=4441"},"modified":"2022-08-17T11:54:17","modified_gmt":"2022-08-17T11:54:17","slug":"configuring-traits1","status":"publish","type":"post","link":"https:\/\/multisite.korebots.com\/SearchAssist\/concepts\/managing-indices\/configuring-traits1\/","title":{"rendered":"Configuring Traits"},"content":{"rendered":"

Traits are characteristics that can be identified and extracted from the search user\u2019s input. They provide insight into the search user\u2019s intent. In natural conversations, it is common for a user to provide background or relevant information when describing a specific scenario.<\/p>\n

\n

You can also identify traits in jargon (i.e. usage in a trade or profession). For example,\u00a0pax<\/i>\u00a0in the travel industry,\u00a0checkout<\/i>\u00a0in the hospitality industry, and\u00a0discharge summary<\/i>\u00a0in health care.<\/p>\n

Traits are specific entities, attributes, or details that users express in their conversations. The utterance may not directly convey any specific intent, but a trait in an utterance can lead to intent detection and drive bot conversation flow.<\/p>\n

You can extract traits from documents. SearchAssist can then map those traits to user queries and use the information to help to increase the relevance score. Use the traits added to the SearchAssist app to fine-tune an index workbench and configure business rules.<\/p>\n

For example, instead of a simple query, \u201cHow do I pay my bill\u201d<\/i>, the user might say, \u201cI was wondering if it would be possible to make payments.\u201d<\/i>\u00a0 To ensure the SearchAssist app generates the same result for either query, manually define a common trait for these two utterances. Tag the corresponding content source or answer with that trait so that future queries generate the most effective search result.<\/p>\n

<\/span><\/span>Adding Traits<\/span><\/span><\/h3>\n

Follow these steps:<\/p>\n

    \n
  1. Click the Indices menu tab.<\/li>\n
  2. In the left pane, click Traits.<\/li>\n
  3. Click the Add Traits button.\"\"<\/a><\/li>\n
  4. In the Create New dialog box, enter a name in the Trait Group field.<\/li>\n
  5. Enter a word or phrase in the Traits field.<\/li>\n
  6. Hit Enter on your keyboard.<\/li>\n
  7. Repeat steps to add multiple traits.\"\"<\/a><\/li>\n<\/ol>\n

    <\/span><\/span>Adding Utterances<\/span><\/span><\/span><\/h3>\n

    After creating a list of traits, open a trait file and add utterances. An utterance is a word or phrase that is likely to be used in a conversation about the trait by the end-user.<\/p>\n

      \n
    1. Locate a trait and click + Add Utterances.\"\"<\/a><\/li>\n
    2. On the next page, enter an utterance.<\/li>\n
    3. Hit Enter.<\/li>\n
    4. Repeat steps.<\/li>\n
    5. Click Add.<\/li>\n
    6. Click Save.\"\"<\/a><\/li>\n<\/ol>\n

      After creating traits, you must extract these traits from the source content so that the traits are identified in the user utterance and are mapped to the source document.<\/p>\n

      Include these traits in the business rules as required and assign the appropriate action.<\/p>\n

      <\/span><\/span>Managing Traits<\/span><\/span><\/h3>\n

      You can perform the following actions on traits:<\/p>\n

        \n
      1. Search for a specific trait.<\/li>\n
      2. On the Traits page, hover over the corresponding row on the far right to see the edit and delete options.\"\"<\/a><\/li>\n<\/ol>\n

        Note<\/b>:\u00a0Make sure you click the\u00a0Train your App<\/b>\u00a0icon each time you make changes to any index configuration. This builds the index based on the updated configurations.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

        Traits are characteristics that can be identified and extracted from the search user\u2019s input. They provide insight into the search user\u2019s intent. In natural conversations, it is common for a user to provide background or relevant information when describing a specific scenario. You can also identify traits in jargon (i.e. usage in a trade or…<\/p>\n","protected":false},"author":18,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[81],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/posts\/4441"}],"collection":[{"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/comments?post=4441"}],"version-history":[{"count":3,"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/posts\/4441\/revisions"}],"predecessor-version":[{"id":4444,"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/posts\/4441\/revisions\/4444"}],"wp:attachment":[{"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/media?parent=4441"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/categories?post=4441"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/multisite.korebots.com\/SearchAssist\/wp-json\/wp\/v2\/tags?post=4441"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}