Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    achadwickContributor ⭐️

    Help center and Community posts not appearing in Gainsight search results due to 5K character limitationReleased

    We recently discovered that a significant portion of our help center articles (housed in Zendesk) are not appearing in Gainsight federated search results, even when a user searches a direct keyword included in a live article. After connecting with the Gainsight support team, we have been told that this is due to a technical limitation with the Gainsight integration with Zendesk Knowledge only crawling up to 5,000 characters of plain text. This means when a user performs a search using a keyword that appears after 5k characters, the article will not appear in Gainsight federated search results at all (versus appearing with a lower rank). This limitation also extends to our Community platform (housed directly in Gainsight) which contradicts the information we received that the 5k character limitation is due to the integration. Regardless, our community and help center represent a significant volume of scaled support resources for our users that are not being surfaced. Accurate search results are a critical function of our scaled support ecosystem. To put this into perspective, the majority of our help center technical documentation (likely around 70% of 250 articles) have more than 5000 characters after html is stripped. It is not feasible for us to restructure our content strategy to exclusively contain short articles. This limitation increases the likelihood users do not find available answers which negatively impacts our user experience. It decreases the trust in our scaled support and undermines our efforts to enable users with more efficient self-serve options.  Where we do not expect Gainsight to compare with search giants like Google (that crawl over 15 million characters of plain text per page), expecting a higher character limit than 5,000 is reasonable. Please consider prioritizing an update that enables more characters to be crawled.

    Sripamidi
    SripamidiContributor ⭐️

    JO EnhancementNew Idea

    Enhancing Journey Orchestrator: Bring Back Query Updates & Support for Image FieldsHello Gainsight Community, We would like to request two key improvements in Journey Orchestrator (JO) that would greatly enhance flexibility and efficiency for Gainsight admins.Reintroducing the Ability to Update Queries in Published JO ProgramsPreviously, JO allowed admins to modify filters and query builder settings even after a program was published, enabling quick adjustments based on evolving internal needs.However, following the latest release, this functionality has been removed. While Gainsight has introduced more complex configuration options, the removal of this essential capability has made even minor updates significantly more time-consuming. Admins are now required to rebuild entire programs from scratch, leading to:• Increased time and effort for minor modifications• Greater risk of errors when reconfiguring queries due to need to filter out on going participants• Reduced agility in responding to business needs Supporting Image Fields in JO ProgramsWe currently have an ability to include images in email templates, with the option to tokenize fields such as a user’s profile picture. However, there is currently no option to bring image-type fields into the query builder, preventing these images from being dynamically mapped within JO programs.Why this enhancement is valuable:• Enables more personalized and visually engaging communications• Provides consistency with Gainsight’s existing image tokenization feature• Expands customization options for customer-facing emails We believe these updates would significantly improve Journey Orchestrator’s usability and efficiency. If you agree, please upvote this post and share your feedback in the comments. Your support will help demonstrate the value of these enhancements to Gainsight’s product team. Thank you!Sri