Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3479 Ideas

    Evie LynchNew Participant

    Feature request: let Fin add a colleague into a conversation and continue it over emailSubmitted

    When Fin identifies that a conversation needs a specific person, I want it to be able to add that person into the conversation directly, with the thread continuing over email outside of Intercom. Fin makes the introduction, the customer and my colleague are both on the thread, and they carry on together from there.Think of it as Fin brokering a warm handoff: "I've looped in Hannah from our team, she'll take it from here" and from that point it's a normal email thread between the lead and Hannah, with the conversation history attached.Our use caseNew business leads come through Fin on our help centre. We've set up a procedure so Fin collects the lead's name, email and company. The person who follows up is a BDR who works out of email, not Intercom.What we want is simple: Fin finishes qualifying, adds the BDR into the conversation, and the whole thing continues as an email thread between the lead and the BDR. No copy-pasting details, no relay through another team, no dead end where the lead is told "someone will be in touch."Today that handoff isn't possible. Conversations can only be assigned or mentioned inside Intercom, and notifications only reach Slack channels or Intercom users. The conversation can't leave the platform with a new human participant on it.What we're not asking forNot Fin for Sales. Our account manager has already advised our inbound lead volume doesn't justify setting it up, and we agree. This isn't a qualification or playbook problem, it's a handoff problem, and it applies beyond sales: finance, legal, and partner contacts all sit outside Intercom too. Not a notification. An FYI email about the conversation still leaves the lead sitting in a closed chat. We want the person added into the conversation so it continues with them on it.

    MsfteDADNew Participant

    Screen reader is not announcing author's name and number of articles on the tiles in windows.Submitted

    Test Environment:OS: Windows 11 version 25H2 (OS Build 26200.7271)Browser: Edge (Version 151.0.4129.15)Screen Reader: NVDA (2025.3.2)URL: https://help.enlyft.com/en/ User Impact:Screen reader users miss the author's name and article count, causing loss of important context needed to understand each tile. This makes it harder for them to choose the right content and affects efficient navigation. Pre-Requisites:Enable NVDA Repro Steps:Open the URL: https://help.enlyft.com/en/ in edge browser in windows. 'Enlyft Knowledge Base' page will appear. Press tab key to navigate to the tile. Verify whether screen reader is announcing author's name and number of articles on the tiles in windows or not.Actual Result:Screen reader is not announcing author's name and number of articles on the tiles in windows.NVDA announces: Getting started An introduction to Enlyft core concept and tools to help you begin your journey. Link Refer Attachment:Screen reader is not announcing author's name and number of articles on the tiles in windows.png Screen reader is not announcing author's name and number of articles on the tiles in windows.mp4 Expected result:Screen reader should announce author's name and number of articles on the tiles in windows.NVDA announces: Getting started An introduction to Enlyft core concept and tools to help you begin your journey. By Tara 3 Articles Link

    Daniel Acevedo
    Daniel AcevedoNew Participant

    Allow Workflows to recognise when a teammate changes the team assignment for a customer ticketSubmitted

    We use the Team conversation attribute to control which Contact Category values are available to teammates. This ensures each team inbox only displays the categories relevant to the team handling the contact.This currently works for normal conversations, but not for customer tickets that are manually reassigned between team inboxes.When a teammate changes the team assignment for an existing customer ticket, the available Contact Category values remain linked to the previously assigned team. The teammate receiving the ticket is therefore unable to select the correct category for the new team.Allowing the category to be selected before the conversation is converted into a ticket does not fully solve the issue, because the customer ticket may be reassigned after it has already been created.Requested improvement- Allow Workflows to recognise when a teammate changes the assigned team for an existing customer ticket.- Refresh Team-dependent Contact Category values after the team assignment changes.- Alternatively, provide a customer ticket Workflow trigger specifically for assigned team changes.ExampleA customer ticket is initially assigned to Team A and is later reassigned to Team B. After the teammate changes the assigned team, the available Contact Category values should refresh to display Team B’s categories rather than continuing to display Team A’s values.Why this matters- Teammates can categorise reassigned customer tickets accurately.- Tickets do not retain outdated categories from the previously assigned team.- Team-specific contact-driver reporting remains reliable.- Attribute dependency logic works consistently across conversations and customer tickets.