Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    518 Ideas

    Chris CammarataNew Participant

    Allow grouping of simulations for regression testing proceduresSubmitted

    We've started using simulations more as a way to regression test our procedures. Every time we make edits (adding guidance, removing edge-case handling, tightening up logic, etc.), we go back and re-run the simulations that are relevant to that procedure to make sure nothing broke in the process.The problem is there's currently no way to organize or categorize simulations by what they're actually testing. As we build out more and more of them, it's getting really hard to know at a glance what's already covered for a given procedure, which ones we should be re-running after a specific edit, or whether a simulation even exists for the scenario we're trying to test. Right now we're stuck scrolling through one long undifferentiated list, and more than once we've ended up recreating a simulation that already existed simply because we couldn't find it.The ask: let us group simulations into folders within the sidebar where the current suite of simulations lives (the Simulations tab in the procedure's testing panel). Ideally these folders would be tied to a specific procedure or issue. This would let us:See at a glance what's covered/tested for a given procedure without having to hunt through the full list Quickly pull up and re-run the right batch of simulations whenever we edit that procedure, or just run the full suite for that group in one go Stop recreating duplicate simulations because we couldn't locate the one we already hadA couple of things that would make this even more useful:Auto-suggested folder placement based on which procedure a simulation was created under, since that context already exists at creation time, rather than having to manually file every simulation ourselves Last-run status and timestamp visible at the folder level, so we can tell at a glance which simulations are already verified against the latest edit vs. stale, without opening each one individuallyThis would also help us stay within our daily usage limits. Right now, not being able to find and reuse existing simulations means we end up spinning up new ones more often than we need to, which burns through our daily allotment faster than it should. Being able to see status at a glance would cut down on that further, since we wouldn't need to re-run something just to check if it's already been verified.We've been finding simulations more and more valuable for this kind of ongoing regression testing as our procedures get more complex, so anything that makes them easier to manage and reuse would go a long way. Bulk actions (archiving or deleting superseded simulations) would also be a nice addition down the line, since one-off tests tend to pile up as procedures evolve.

    AchiniNew Participant

    Feature Request : Support for Multiple Webhooks per WorkspaceSubmitted

    Currently, a single Intercom app can only be configured with one webhook endpoint. This becomes a significant limitation for organizations that operate across multiple environments and regions.In our case, we run live instances in both the US and EU regions, plus separate Staging and UAT environments — four environments in total, each needing its own webhook endpoint to receive and process Intercom conversation events (we feed conversation attributes back into our systems via webhook data).Since only one webhook can be plugged into an app, the current workaround is to create four separate Intercom apps, one per environment/region. This is difficult to maintain: any configuration change has to be manually repeated across all four apps, which is time-consuming and error-prone, and increases the risk of inconsistent setups between environments.This is a common pattern for SaaS products that maintain multiple environments (e.g., UAT, Production) across multiple regions (e.g., US, EU). Requiring a separate app per environment/region just to support multiple webhooks adds unnecessary operational overhead.Requested functionality:Support for multiple webhook endpoints within a single Intercom app, so that one app can route events to different endpoints (e.g., one per environment or region) without needing to duplicate the entire app setup.We are currently blocked by this limitation and would appreciate knowing if this capability is already planned, or if not, that it be considered given how common this multi-region/multi-environment setup is for enterprise customers

    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.