Skip to main content

    Idea Pipeline

    5698 Ideas

    NEOGOV Tom
    NEOGOV TomContributor ⭐️

    Introduce Native Blog & Podcast CapabilitiesNew Idea

    I’d love to see the Gainsight platform evolve to support native blogs and podcasts directly within the platform — not just as linked external content, but as fully integrated community-driven media experiences.Communities today are more than Q&A forums — they are dynamic content ecosystems. Adding native blog and podcast capabilities would allow brands to centralize thought leadership, storytelling, and knowledge-sharing in a way that drives both engagement and long-term value.The OpportunityMost companies using community platforms today:> Publish blogs on their marketing website> Host podcasts externally (Spotify, Apple Podcasts, etc.)> Share links back into the community> Fragment engagement and analytics across toolsThis creates:> Disconnected conversations> Limited SEO compounding> Fragmented member journeys> Missed opportunities for structured knowledge captureBy introducing native blog and podcast functionality, Gainsight could enable customers to:> Host executive thought leadership directly in community> Publish customer stories and case studies> Feature subject-matter experts> Highlight superusers and advocates> Capture podcast conversations as searchable knowledgeThis strengthens the community as the central hub of engagement, not just a support channel.Why This Matters StrategicallyFrom a community lifecycle perspective:> Blogs drive rational engagement (deep reads, comments, shares).> Podcasts drive emotional and relational engagement.> Together, they increase both passive and active engagement behaviors.Integrated media also:> Improves SEO footprint> Extends time-on-platform> Encourages member-generated content> Provides new gamification opportunities (top contributor blog badge, featured guest recognition, etc.)This aligns beautifully with modern community orchestration models where content, conversation, and knowledge creation reinforce each other.What “Native” Could Look LikeBlog Capability> Dedicated blog content type> Rich formatting and embedded media> Author profiles tied to community reputation> Tagging aligned to existing knowledge taxonomy> Featured content carousel on homepage> Analytics integrated into community reportingPodcast Capability> Native audio hosting or embeddable player> Episode pages with:> Show notes> Time-stamped highlights> Comment threads> Downloadable transcripts> Ability to auto-generate searchable transcripts> Subscription/follow functionality> Featured guest badges tied to member profilesBusiness Benefits for Gainsight Customers> Centralized engagement hub> Reduced reliance on third-party publishing platforms> Stronger brand control> Unified analytics> Improved knowledge retention> Stronger community-to-advocacy pipelineThis would position Gainsight Community not just as a support forum — but as a full-scale community content platform.Phased Rollout SuggestionPhase 1: Native blog modulePhase 2: Podcast episode content type + transcript indexingPhase 3: Advanced media analytics + gamification integrationClosing ThoughtThe most successful communities are not just reactive (support-based) — they are narrative-driven.Giving customers the ability to publish blogs and podcasts directly inside the community platform transforms it into a living, searchable, multi-format knowledge ecosystem.I’d love to hear how others would use this capability.

    kumaranbcakContributor ⭐️⭐️⭐️⭐️⭐️

    The Object Dependency feature needs significant improvement to be truly useful for admins.New Idea

    The Object Dependency feature needs significant improvement to be truly useful for admins.First, the dependency view must allow filtering of dependent rules based on meaningful criteria such as: Active / Inactive Scheduled / Not Scheduled Read vs Write dependencies Without this, it’s extremely difficult to identify which rules are actually impacting an object versus those that merely reference it.Second, the Object Dependency feature still shows obsolete rules that no longer exist in the system, including older generation rules that pre-date the Horizon Rules Engine. This creates confusion and reduces trust in the dependency data, especially when we are performing cleanup or impact analysis.There is also a suggestion in this thread to rely on Analyzer, but unfortunately this is not a reliable alternative. In multiple cases, Analyzer does not surface correct or complete dependency information.For example:In our Gainsgiht instance, The “X” field on the Person object is actively used in several rulesEven after repeatedly refreshing the Data Flow Diagram, Analyzer does not show the respective rules at all. This is just one example among many.Additionally, earlier this week I attempted multiple times to refresh the Data Flow Diagram, but it did not refresh for at least four days, further limiting its usability.As admins, we need a reliable, accurate, and filterable way to identify dependencies before making changes to objects or fields. Today, neither Object Dependencies nor Analyzer fully meets that need.