Skip to main content
Jared
Inspiring
March 10, 2025
1. New

Proposal for Improving External Knowledge Feature Flexibility and Article Management

Related products:Moveworks Setup
  • March 10, 2025
  • 2 replies
  • 27 views

 

I would like to propose an enhancement to the External Knowledge (EK) feature, specifically concerning the management and exclusion of articles from the entities offered within our support bot framework.

Current Challenge:

The integration of external articles from entities such as Asana, Slack, 1Password, among others, is invaluable. However, we face challenges in maintaining a curated selection of content due to the platform's approach to entity article inclusions, which automatically includes all articles from selected entities. This often leads to the inclusion of irrelevant content, overwhelming users with articles not applicable to most (e.g., articles relating to changing global permissions or features not available to most users).

Furthermore, we have encountered an exclusion limit that restricts the percentage of articles we can exclude. This limitation does not consider the relevance of entities to our operational environment, resulting in the inclusion of content from tools not utilized by our company. We estimate that only about 50-60% of the articles for each entity would add value to the majority of our employee base.

Proposed Solution:

To address these issues, we propose the following enhancements:

  1. Enhanced Exclusion Flexibility: Modify (or remove!) the exclusion limit to allow a greater degree of control over which articles and entities are included or excluded, based on their relevance. This could include a nuanced approach to exclusions that doesn't penalize organizations for fully excluding irrelevant entities.
  2. Persistent Curation: Ensure that manually curated selections of included articles for specific entities are maintained and do not automatically revert to including all available content.
  3. Relevance-Based Inclusion Criteria: Introduce a feature that allows organizations to set criteria for relevance, automatically filtering out articles and entities that do not meet these predefined standards. This could include sub-categorizing features (e.g., Admin features) to enable swift exclusion of all admin-feature-related articles.

Value Proposition:

Implementing these changes would significantly enhance the usability and effectiveness of the EK feature for our company and potentially other clients. By providing more relevant, curated content, we aim to improve the efficiency of information retrieval for our users, reduce information overload, and increase overall satisfaction with our support bot.

 

2 replies

DIANA.TWC
Inspiring
July 16, 2025

@Jared - FYI it seems they gave the permission to exclude down to the article level, its on setup. It will be nice if we can also have a ‘keyword’ list where external knowledge shouldnt be referenced.

Jared
JaredAuthor
Inspiring
July 17, 2025

Hi ​@DIANA.TWC, are you aware as to whether they overrode the old policy that you could not exclude more than 10% (if I remember correctly) of the articles provided?

I’m pretty sure we’ve always been able to exclude down to the article level, the issue was that there was a limit of what percentage of articles I can exclude, so for example if I wanted to only include 5-10 articles related to a subject (take Duo or iOS as an example) then I was not able to do so. ALL of the DUO articles would automatically go live after 1 day, so my bot had access to far more information than was relevant to our implementation.