🗓 December 15, 2020: Hitchhikers Office Hours

Webinars and Office Hours
1

Add questions or topics below that you would like to have answered or discussed during this office hours sessions!

2

Hey Team -

My client is a Financial Services client. They have Answers on their Home page and also on their Loan Officer pages.

We have a vertical dedicated to Loan Officers, however, if I search from a Loan Officer page, the client does not want the user to be able to stumble upon a different LO.

At first glance, it seems the only way to set this up would be via multiple Query Rules and multiple Saved Filters (one for each Loan Officer).

Is there a better way to do this?

3

Can we review the Answers implications of changing entity language profiles in the Knowledge Graph? Specifically why one would do so between different English profiles - i.e. English vs. English (United Kingdom)?

4

Can we review how to set the width of an Answers Experience to match the width of the client’s main site?

I know this can be done using the variable --hh-answers-container-width in the answers-variables.scss file but I understand there are also breakpoints to consider.

5

Can you set multiple pieces of criteria for a query rule? I.e. if I want a certain entity to be boosted when someone searches “install” and “download”, can I set 1 rule with 2 pieces of criteria or do I need to set up 2 rules?

6

Here is the recording from today’s office hours. Thanks for joining!

1 Like
7

Hi Jessie,

You can do this using a filter by Entity ID!

Here’s an example of what the rule would look like:

{
      "criteria": {
        "contextContainsKey": "$.entityId"
      },
      "actions": [
        {
          "actionType": "ADD_FILTER",
          "filter": {
            "entityId": {
              "$eq": "{{$.entityId}}"
            }
          },
          "verticals": [
            "loan-officers"
          ]
        }
      ],
      "name": "Filter By Entity ID"
    }

On the LO page (where the search bar is initialized at the top), you can call ANSWERS.setContext() , for example ANSWERS.setContext({entityId: "LO-18219"}).

Here’s the full query rules module for further reference: Query Rules | Hitchhikers

Thanks,
Rose