What options are available for context configuration?
Context categories can have several types such as device type, geo-location and more.
| Name | Description | Available values |
|---|---|---|
| Normal | This option enables segmentation based on custom criteria, that is, you can define any context values you want to use. For example, you might want to show different content for internal and external users. | The context values you specify. |
| Device type | This option enables segmentation based on device type. |
Bold360 AI works with the following values:
 Note: You must add these values manually to the context category. |
| Geo-Location: Country | This option enables segmentation based on which country the visitor is located in. |
Bold360 AI works with the values included in Context values for Geo-Location: Country. Note: You must add the two-letter country codes you want to use as context values manually. |
| Geo-Location: Custom Mapping | This option enables mapping of geo-location information to custom context values. Based on the two-character country codes, you can provide a mapping to change the names of some of them or create groupings of a few of them. | Contact your Customer Success Manager for more information. |
| IP Mapping | This option enables mapping of IP addresses to custom context values. Based on the IP address, you can provide a mapping to create groupings, for example, internal IPs versus external. | Contact your Customer Success Manager for more information. |
| Domain: Custom mapping | This option enables mapping of domain information to custom context values. Based on the domain of the page that the widget is visited on, you can provide a mapping to create groupings or automatically assign a context value based on the domain. | Contact your Customer Success Manager for more information. |
| Numeric range mapping | If the user?s context is a specific number, for instance, an employee ID, for each range of numbers you can set a specific context value, such as department. This enables mapping articles to a limited set of context values rather than to an endless list of numeric values. | Contact your Customer Success Manager for more information. |
| Name | Description |
|---|---|
| Persistent | The context value is applied to the entire user journey. |
| Topic | The context value is dropped when the user moves to a different intent that doesn't have the same context. |
| Intent | The context value is dropped when the user moves to a different intent. |
| Name | Description | Default Value |
|---|---|---|
| Article Context Required | When this option is selected,articles with single or multiple context values appear on pages with a single context value. These articles however do not appear on generic pages with no context defined, unless the Detect from user search option is selected. | Not selected |
| Visible in widget | When this option is selected, the context of the article is displayed in the search widget. | Selected |
| Auto-learn | When this option is selected, the context is added automatically to a new article that is created based on a voice or a ticket. | Selected |
| Visible in knowledge base and publish center | When this option is selected, the context is presented as a column in the article list in the knowledge base as well as on the suggested content page. The context value of each article appears in the column. This allows you to search articles mapped to specific context values. | Selected |
| Visible in tickets | When this option is selected, the article context is presented as a column in the ticket list. The article context is added to the ticket. Article context can also be forwarded to 3rd party ticketing systems. | Selected |
| Detect from user search | When this option is selected and the context is not specified by the script on page, the context value is extracted from the user's search when the context value is explicitly mentioned. For example, the user may ask a question like How do I cancel the order on the app? or a dialog may be presented to the user where they are asked to provide the context. | Not selected |
| Allow public access | The context values can be accessed and retrieved with an API request to be displayed in the context dialog. | Selected |
| Full value required | When this option is selected, search results must match all context values associated with the user. | Selected |
| Each word is a unique value in the user?s context | With this option, you can use single words to represent context values even when the context value consists of more than one word. For example, "iPhone 6S" may represent one context value across device context, or two context categories: one for device and another one for version. | Not selected |
| Add names of attributes/specification to be used as context | In case the context values are to be picked up from a variable that is already defined on the webpage, capture the variable name in this field. | N/A |
| Text prompt in widget | Enter the text to be displayed in the dialog that comes up to ask for the user's context. This is relevant when the Detect context from user search option is selected. | N/A |
