Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3155 Ideas

    Nikki McLaughlin
    Nikki McLaughlinActive User

    Add LOCK Button to Testing Fin FeatureSubmitted

    First, I absolutely LOVE that we can test Fin before implementing changes in Production. This feature has been incredibly valuable and has made us much more confident in the quality of what we're deploying.One enhancement that would make the testing workflow even better would be the ability to lock completed test results.We've gone from training one or two people to training multiple support teams across two products. As a multi-brand company, we frequently update audiences and rerun answers during testing. The challenge is that if a batch has already been graded and comments have been added, rerunning the answers wipes out all of that work.A simple Lock/Unlock option for completed batches would help preserve grading and comments while still allowing teams to intentionally unlock a batch if they need to rerun or regrade it. I think this would be especially valuable for organizations that have multiple teams collaborating on testing.I also wanted to mention what appears to be a performance issue with the testing workspace.Even when working by myself, I noticed the server struggling to keep up after uploading eight batches. Yesterday, we had six team members testing simultaneously, and the grading functionality stopped working altogether—we could no longer mark responses as Good, Acceptable, or Poor, nor could we add comments. By this morning, everything was working normally again.For now, I'm planning to have our team stagger their testing sessions, but it may be worth investigating whether there are concurrency or capacity limitations in the testing environment. As more customers begin using the testing feature with larger teams, I could see this becoming a common challenge.Overall, we're really excited about this feature. These are just a couple of improvements that I think would make an already great testing experience even better.

    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.