Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3160 Ideas

    JHarlowe
    JHarloweConnector

    Command K (⌘K) Search Result Ranking and PrioritizationSubmitted

    Area: Inbox / Command K Shortcut Bar Summary:Command K search results lack intelligent ranking when performing frequent actions such as setting ticket states. Results do not prioritize based on usage frequency, exact text match, or relevance, creating unnecessary friction for agents who rely on this workflow multiple times per day. Current Behavior:When using Command K to set a ticket status (e.g., "Waiting on Customer"), the search results behave inconsistently. For months, searching "waiting on" returned "Waiting on Customer" as the top result. Over time, newly created items have appeared at the top of the results list with no apparent sorting logic, pushing frequently used actions further down. Additionally, even when the full text "Waiting on Customer" is entered, four other results are prioritized above the exact match. The result order also appears to shift depending on what is typed, producing unpredictable outcomes.  Ideal Behavior:Command K search results should apply intelligent ranking that accounts for exact text matches, usage frequency, and recency. At minimum, typing the full name of a ticket state should surface that exact match as the top result. Ideally, agents should also have the ability to pin or prioritize frequently used actions within Command K. Business Impact:Support agents set ticket statuses numerous times per day. The current static, non-adaptive result ordering adds cumulative friction to a core workflow, reducing efficiency across the team. As workspaces scale with custom ticket states, this issue will continue to compound. 

    Peter SchöllNew Participant

    Legal Footer/Impressum for Ticket Notification Emails (GDPR/Compliance Requirement)Submitted

    Problem/Use Case:As a company operating in Germany and the EU, we are legally required to include an "Impressum" (legal disclosure) in ALL business emails, including transactional emails like ticket notifications.Currently, Intercom allows customization of email footers for marketing emails and some other templates, but ticket notification emails cannot be customized. This creates a significant compliance gap, as German law (§5 TMG) and EU regulations require legal information in all business communications, regardless of whether they are marketing or transactional emails.Current Limitation:Ticket email templates are standardized and cannot be modified No option to add company legal information (Impressum) to ticket notification footers This affects all ticket-related emails sent from Intercom to customersRequested Feature:Add the ability to customize the footer of ticket notification emails to include:Company legal information (Impressum) Customizable footer text fields Support for multi-brand configurations with different legal footers per brandWhy This Matters:Legal Compliance: German §5 TMG and similar EU regulations mandate legal disclosures in all business emails Risk Mitigation: Operating without proper legal disclosures can result in costly warnings ("Abmahnungen") and fines Professional Communication: Customers expect proper legal information in all business correspondence Competitive Disadvantage: Other support platforms (Zendesk, Freshdesk) offer this functionalitySuggested Implementation:Similar to the existing functionality for other email templates, add a customizable footer section in: Settings > Workspace > Brands > [Brand Name] > Ticket Email FooterThis should include:Rich text editor for legal information Variable support for dynamic content Preview functionality Per-brand configuration for multi-brand workspacesImpact:This feature would enable EU-based companies to use Intercom's ticket system in full legal compliance and remove a significant barrier for adoption in European markets.

    Ability to find where an article is linked in other articleSubmitted

    The problem: There's no way to see the backlinks of a Help Center article — i.e., which other articles contain internal links that reference it. The internal links between our articles are invisible to us as authors: we can create them, but we can never look them up.Why it matters most — safe archiving: When we archive or delete an article today, we have no way to know which live articles still link to it. Every archive action risks silently leaving broken links across the Help Center, and we only find out when a customer clicks one. The same blindness affects renaming or merging articles, running content audits, and understanding the ripple effect before rewriting an article that other content depends on.The request: A "Referenced by" view for each article — a list of every article that links to it. Natural places for it: a panel in the article editor, a column or filter in the Articles list, or at minimum a warning when archiving/deleting an article that other articles still link to it ("3 articles link here — review before archiving").Implementation note: tracking links by Article ID rather than URL would keep the index accurate even when titles or URLs change.This is a standard link-management capability in most content platforms (wikis and CMSs typically call it backlinks or "what links here"), and the underlying data already exists in the article content — it just isn't exposed to us. It would make maintaining a large, interconnected Help Center dramatically safer. Thanks for considering!