Pioneer: A summit where CX leaders redefine what's possible
Fin & Helpdesk Q&A
Recently active
Hi Team,Coming from tools like n8n, the Intercom workflow canvas feels very "stiff". I get that the grid keeps things aligned, but it actually makes organizing complex shops harder than it needs to be.The Problem: Right now, you can’t manually group nodes or add much whitespace. This forces everything into long horizontal chains that are hard to read at a glance. To keep my screen clean, I’m forced to make dozens of Reusable Workflows just to avoid a messy canvas.The Solution: We need a "middle ground". Keep the snap-to-grid so things stay professional, but let us move nodes further apart or group them vertically.Why this helps:Faster QA: You can physically separate "Sales" paths from "Payment" paths to see how the logic flows.Easier Training: It’s easier to spot where a Handover is failing if the nodes aren't all bunched together.Better Organization: Solo managers can organize their "brainstorming" nodes away from their "live" nodes.If we can organize our logic visually, we can build
Hi there! I’m trying to test a use case, but no luck so far, so I wanted o see if any of you tried something similar. Use case: I need Fin to override the user’s initial inquiry IF Fin detects a Health check issue on the user’s account. I have the data connector set up, and I added a When/If/then guidance. So far, this guidance is only triggered if the user asks a direct question about their account health status. Here’s a screenshot of the rule:
Issue DescriptionWe're experiencing signal handler conflicts between Firebase Crashlytics and Intercom SDK in our app. During app initialization, we see multiple warnings in the console:[Crashlytics] The signal SIGABRT has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGBUS has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGFPE has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGILL has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGSEGV has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGSYS has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This w
Today, Intercom auto replies (Messenger and email) only support static text or expected reply times based on historical data (e.g. 7-day median first response time). There’s currently no way to adjust these messages based on real-time backlog or queue volume.Feature request:Allow auto replies to use dynamic variables tied to live operational data—specifically backlog size or queue depth—to communicate a more accurate estimated response time.Example use case:If backlog is low → “We typically reply within ~1 hour.”If backlog is high → “We’re experiencing higher volume and expect to reply within ~24 hours.”Why this matters: Sets clearer expectations during traffic spikes Reduces follow-up messages like “Are you there?” Improves customer trust and transparency Helps teams avoid manually updating auto replies during busy periods Suggested implementation ideas (flexible): Variables such as {{estimated_reply_time}} driven by backlog thresholds Rules like “If open conversations > X,
I can create a tracker ticket and link user raised conversations. Can add a note that I can then copy down to all linked conversations.How could I add a comment on the tracker (parent) that actually creates that same note as an email in all the linked conversations?
I want to be able to set the redetect on closure for Fin and for teammates separately. For example, I want to be able to set up an attribute to be redetected upon Fin closure but not teammate closure. The reasoning here is that we want to rely on Fin to set the attribute when a human is not involved, but when a human is involved, we want to trust the human.
Hello Intercom Community!I’ve been building complex automated shops using Fin and Workflows, and I’ve noticed a significant limitation in the current "Let Fin handle" node. Once a user is inside the Fin flow, it often feels like a "dead end" for automation. Currently, Fin can only resolve the chat or escalate to a teammate.The Problem: There is currently no built-in way for Fin to guide users back to previous paths or nodes within the same conversation flow once the AI is active. For example, if a user finishes browsing product details with Fin but wants to go back to the main menu buttons to start a different process, they are stuck unless a human intervenes.The Proposed Feature: "Automation Loop-Back" I would love to see an option within Fin's guidance or node settings that allows for a "Start Over" or "Go Back" trigger.Key Functionality: A specific command in Fin's guidance (e.g., "If the user wants to start over, hand back to [Node Name]") that re-triggers a previous part of the wo
I’ve noticed FIN closing some conversations because the user didn’t explicitly confirm escalation, even though the conditions for escalation were met. The rules I set were: Escalate if the user shows negative or neutral sentiment. Escalate when the user provides all required information. Escalate when the user requests escalation. The issue is that when a user provides all the information and FIN sends the escalation message “An agent will be with you soon,” it later follows with “Is there anything else I can help you with?”If the user responds with something like “No,” FIN ignores the first escalation message and treats the user’s “No” as a signal to close the chat. Instead of keeping the ticket open for an agent, it ends the conversation.
Hi everyone, We’re seeing Fin frequently sending a follow-up message after responses, like:“Did that answer your question?” / “Was this helpful?” In many cases it happens almost after every message, and it can feel repetitive for customers. Is there a way to control the frequency of this follow-up (reduce it, change when it appears, or disable it)? We’d like more control so it doesn’t trigger too often.
Our database is not linked to Intercom and we cannot upload a list of users because we deal with PHI so need to limit contact information to those we correspond with, so ALL contacts are leads. We have many, many duplicate leads and need to be able to merge them so all of their conversations (phone, emails, tickets, etc) are together.
The problem is two fold, this ticket focuses on the second point below:Intercom only allows the merge of duplicate leads into users (which will get it’s own ticket) Currently a lead is only changed to a user if the system detects an account has been created, or if we import a list of users. We do not currently have our database linked to Intercom and deal with PHI so it is important we keep data sharing to as needed, so importing a full list isn’t ideal.We should be able to manually change leads to users so that we can then merge duplicate leads into the matching user.
Very often, mostly, we need to check report for the previous month, and so every time need manually select it from the date rangePlease, add Past month option to the date range in drop down menu for reports
It would be great to see some reporting improvements for articles. Article view by language. We are now supporting 7 additional languages in our Knowledge Base. It would be helpful to measure the success of these articles by seeing how many users are viewing the articles in French or Italian, etc. Article views by customer. Perhaps this exists already but I can’t find a way to see the number of views by customers to see if an article is being utilized to help customers that are writing in with specific problems.
Would be great to be able to color code inbox by statuses, so you can quickly view an inbox and see the status of all items.
As can propose Zendesk, it would be more efficient and easier to organize the macros, if we were able to create a single macro, for different languages.
I want to be able to quickly snooze conversations as I respond, but 1 day is too short, and a week too long. I would like to be able to set up for my user profile so that I can choose my default snooze times available in the send and snooze menu.
Please can some improvements be made to the Help Centre’s search functionality? Currently it isn’t really up to industry standard and is providing a poor user experience• It doesn’t pick on synonyms/different terminology - so without keyword-stuffing (which is bad practice and poor UX), content gets missed. Already raised by someone else here, here and here a year ago and still an issue - especially when it comes to typos, Fin can detect these so the HC should be able to as well. Some typos appear to be accounted for but not all - we should be able to customise this.• Similarly, if we have a standardised/approved way of spelling/styling a term, this is the only one we use within our content for consistency - however users might spell it differently. Their spelling is valid (and not a typo necessarily) but doesn’t match our brand-approved spelling, and so articles don’t surface for them. Eg. “multisite”, “multi-site”, “multi site” are all grammatically appropriate, but we only use the h
There is a property that the SDK adds to requests to Intercom. It is called anonymous_session . It appears to keep the API calls to Intercom working beyond the JWT expiry. :Why does this keep authentication alive? Is there a way we can disable it to have more control over the amount of time the API is accessible.
I am seeing a persistent error when trying to save and set live a specific, large inbound workflow in Intercom. Trigger: When customer opens a new conversation in the Messenger for Web, audience = Leads and Users. Symptoms: UI shows: “We couldn't set this workflow live. Send us a message and we'll do our best to help out.” at the top of the builder. Network tab shows the PUT request to /ember/matching_system/rulesets/{id} returning 502 Bad Gateway (nginx) when saving/setting live this workflow. The ruleset payload shows an ID, links, etc., but predicate_group, client_predicate_group, and default_predicate_group are empty arrays. Troubleshooting already done No red paths or visible validation errors anywhere in the workflow builder. Clicked Save and close first every time before trying Set live. Saving is also not working now. Before it was working file Tried: Incognito / private windows and multiple browsers. Clearing cookies and hard refresh. D
Many companies are now providing llms.txt for their documentation to make it more efficient for agents to consume content. It’s an index of publicly available markdown files. See, for example, https://cloudinary.com/documentation/llms.txt. If Fin supported this as a content source (or even just markdown files as a source) it would really help us, as the markdown files contain all code examples, and expand content that’s in collapsed sections - content that’s not accessible directly from the HTML.
We’re trying to use the CSV filtering feature in the outbound chat to match phone numbers with our audience. But the process (tagging) takes way too long, 1+ hour for just 1 user, and still shows 0 people in the tags list. On the other hand, using the name as the matching attribute took only ~3min for the same user. I don’t think this is a format issue because the CSV file was created in notepad not Excel (which uses scientific notations). The Phone attribute is a text.
Ive noticed that my macros will sometimes be available for use and sometimes not. nots sure why this is as the settings allow for it to be used as new conversation, replying and notes.
Hey team! Renee here - lead CSM at Storylane 👋Resurfacing this request since it continues to come up regularly with our Storylane customers.Intercom help center articles currently don’t support embedded images, HTML, or iframes, which makes it difficult for teams to automate or streamline self-serve education. As a result, teams are forced to rely on workarounds like links, GIFs, or video uploads instead of keeping richer, interactive content directly in articles.This remains a blocker for onboarding, feature education, and support deflection, and it’s coming up across dozens of teams (40+ have flagged this to us directly) - not just edge cases.We also noticed the recent Supademo ↔ Intercom integration, which shows that deeper interactive content experiences are possible within the Intercom ecosystem. Many of our customers are asking for similar flexibility directly within Articles.Would love to know if broader support like this is on the roadmap, and happy to share more details if he
I’m working with Intercom tooltips and want to show or hide them conditionally from my web UI.I have a toggle button in my frontend that allows users to manually turn tooltips on or off. Based on this toggle, I want to control the visibility of Intercom tooltips.What I’ve done so far: In Intercom, I configured the tooltip rule as: learn_mode == true On the frontend, when the toggle button is clicked, I call: Intercom('update', { learn_mode: true }); // or false The goal is: learn_mode = true → show tooltips learn_mode = false → hide tooltips Issue:The Intercom('update') call does not seem to trigger the tooltip. The tooltip does not appear or disappear as expected when toggling the button.Question:What could be the possible reasons why the Intercom('update') call is not triggering the tooltip, and what should I check to ensure the tooltip renders correctly based on the custom attribute?
We have customers using different spellings, typos, etc .of words while searching for content in our help centre and not finding our content as a result. How can I add common alternatives to word in an article or the backend, to ensure our customers always find what they’re looking for even if they are using different language to us? This is not related to SEO but and solutions welcome.E.g : a customer searching for a Wi-Fi connectivity article types in wifi and nothing comes up. or a customer types in TRV (thermostatic radiator valve) and nothing comes up because we use ‘Smart Radiator Thermostat’.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.