Workflows

We have some team members that are not on Intercom all the time. However, some message do need their input. It would be great to be able to slack teammate when they are mentioned @____ in the notes.And also, when the chat is assigned to the person.

 Yesterday and today we experienced two inbound phone calls in a short period where the phonecalls entered the Hold and assign call step and remained In queue.No available teammate was automatically offered the call, even though atleast one teammate was active and could immediately answer the call manually.Can someone of Intercom check the backend routing logs to determine why no teammate was selected for automatic assignment for these conversations? I've already tried to figure out what might have gone wrong, based on the logging I am thinking it might have something to do with the away status and how we have configured our workflow, but no clear reason could be determined.We have enabled Show team composition in conversation event log, but no team composition events are written to the conversation timeline for new inbound calls. Is there any prerequisite for this feature, or is it expected to work for all Phone conversations?We compared a successful inbound call with a failed inbound

I am no longer able to highlight text to copy it. It unhighlights too quickly. I never had this problem before I started seeing little floating icons for Co Pilot next to everything I highlight. Now that it’s there, nothing stays highlighted long enough for me to even press control + c

Hi everyone,I’ve been working on integrating the Intercom Messenger into a custom web application, and I’ve run into a specific technical hurdle that I’m hoping the community can help with.I am currently using a delta vietnam setup to execute some background scripts and handle task automation within the site's environment. While everything works perfectly on the desktop version, I’ve noticed that when this executor is active in a mobile web view, the Intercom Messenger launcher fails to initialize. It seems like there might be a conflict between how the script executor manages the DOM and the window.Intercom boot sequence.I’m seeing a couple of related issues as well:I'm not sure if the asynchronous loading of the script executor is competing for resources with the Intercom snippet, or if it's potentially masking the user identity variables needed for a successful boot. Has anyone else used a delta vietnam community workflow or a similar third-party script manager alongside the Interco

We would love to see an option that allows callers to remain in the queue without having to make an active IVR selection.In our market, the most common expectation is simply to wait for an answer. Requiring callers to press a key to continue waiting can create unnecessary friction and may lead to confusion or abandoned calls.An option to let callers stay in the queue automatically, while still offering callback or other choices as optional alternatives, would create a more natural and user-friendly phone experience.Would anyone else find this useful?

When a ticket is created from a contact form submission containing the customer's full query, Fin currently does not respond and the ticket closes due to inactivity because Fin is waiting for a new customer message. Is there a way to configure Fin or a Procedure to treat the ticket's submitted content as the triggering message, so Fin responds without requiring the customer to send anything further?

Hi all, we just turned on the Suggest Help Articles Task Bot for both users and leads and in the first week of use we are finding its article suggestions to be way off. It seems to be suggesting just our oldest/highest viewed articles without taking into account keywords (see below for an example).  I've already read Intercom's "Let users help themselves with smart suggestions" and "Share articles to answer questions faster". I've done the suggestions about writing relevant articles with the words the customers are searching for.  The suggestion about -"When a customer gets in touch, you should send them a relevant article in your first reply to them. If they send you a second message before you reply Operator won’t learn from this." - really doesn't work for my company. When our users actually get to talk to a live agent they expect targeted, step-by-step support, not just guidance on where to find an article and especially not on the firs

Hi! We have two support teams in two different countries with a 14 hour 30 minute time difference and sometimes need to set up a workflow for our chats but have it only send to our customers in one region. (for example one country has a national holiday and is out of office but the other does not)We tried with a workflow set up; When customer visits a page-I added an Audience to this. Where the audience was set to Visitors, Users, and Leads ‘Country is X’. However, it shows no people match these rules yet in the audience menu. And this made it so the workflow did not trigger for anyone. What is the best way for us to set this up for the future where certain chat workflows trigger only for certain countries? 

Is it possible (or: what is the best way to...) run a small bit of code or show an iFrame in the messenger? For a certain case in a custom bot, if a user chooses a certain path, I want to show the user a quick calculator. The code is very simple - an HTML input, and about 5 lines of javascript. Is it possible to either put the code somewhere to show it in the bot? Or otherwise, can I use an iframe that shows a page where the calculator is hosted? Thanks

Today, teammates can reply to customer tickets and conversations from their email inbox. We’d like a workspace setting that disables teammate email replies, so teammates must reply only inside Intercom (Inbox). This helps prevent accidental customer-facing replies (for example, when someone thinks they’re adding an internal note) and ensures every response is clearly visible and auditable in one place.I’m not sure how best to do this today as haven’t been able to find the settings for this, we were able to do this super easily in Zendesk. Thank you!

Hi all,We're a regulated fintech app (Junior Stocks & Shares ISA) and have two distinct user types who might need support:1. Our main customers — parents who hold a JISA account with us2. Gifters — friends and family who are gifting money to a child's account but don't have an account themselvesWe'd like to add a support button within our gifting flow so gifters can reach us when they get stuck. But we want to make sure gifter conversations are kept separate from our main customer support queue.A few questions:• Can we configure multiple Messenger launchers that route to different inboxes or teams depending on where in the product they're triggered?• Can conversations be automatically tagged or routed based on which screen or page the Messenger was opened from?• Is it possible to create a separate Messenger experience for users who aren't logged in or don't have an account?• Can we set up routing rules to ensure gifter conversations never land in the same inbox as customer queries?

I’ve been thinking about how customer support teams manage queries for content creation tools, especially those with a large non-technical user base. Free apps seem to generate a lot of repetitive questions like exporting issues, performance on different devices, or how to use certain editing features.From a support perspective, this raises a few questions:How much of these queries can realistically be handled through automation (chatbots, guided flows, etc.) without frustrating users? At what point does it make more sense to route users to a human agent instead of relying on automated responses? Has anyone here used Intercom to manage high-volume, feature-related queries like theseOpen to suggestions how others are balancing scalability with user experience in this kind of scenario.

We are using the trial version with Expert capabilities to assess if Intercom suits our needs. We want an AI agent to embed in our software products. This agent should provide level 1 support based on documentation content. If the agent cannot help, it should hand off to our Support and Product Team in Jira Service Desk by calling a data connector to create a new ticket via the Atlassian API.The challenge we face is that there seems to be no way to set a Title and Description or copy the conversation into attributes for the data connector.Is there a way to achieve this? We are not going to use Intercom Inbox, as our support team only will interact with our customers via Jira Service Desk.  using Message Body, just the first user´s message is returned, other attributes from Conversation category doesn´t seems to be working for a data connection. 

How can I reassign a closed conversation without reopening it?Currently, if a conversation is assigned to Person A and its status is Closed, reassigning it to Person B automatically changes the status back to Open.Is there a way to keep the conversation Closed while still changing the assignee?

Using Intercom as a wishlist Our team is looking for a way to collect feature requests and feedback from our users. We have used third-party apps in the past, but we want to stray away from them for a number of reasons. My idea is to use Intercom for this. Our users would be able to select an option 'I have a wish/feature request' and build a workflow around that. My question to the community is: does anyone have experience with this?  I am looking for tips, best practices and advice. The most important key points are:Convenience Users should easily drop their ideas with our team Overview Ideas/feedback/requests need to be grouped and segmented Automated Minimal teammate interference. Fin and automations should do all the work Public roadmap and public ideas are not what we're after.Open to your suggestions 😄

We utilise auto translate in workflows, and on welcome, we share a message and offer the visitor options to select based on why they contact us, these selections in turn determine the path of the flow that is followed.  The issue is, The welcome message itself is sent in the detected language (browser or location, however this is being picked up), but, the choices (buttons) are displayed in the workspace default language, which is English. This means that we are contacted from say a Spanish or German customer, we send a localised welcome message, and present the options in English, this makes no sense.  Other than setting up individual workflows per language, is there a way to resolve this, if not, I would suggest that the same logic is followed for button translation and those are sent in the same language as the welcome message at the very least.  From research, the button translation comes once the language attribute is “locked in” by FIN, but that doesn’t seem to make much sense to

Hey all,Fin just let me know that data connector fields can’t really be used in a workflow- only through a procedure. I can run the data connector function through a workflow, but then I can’t actually access any of the fields that data connector found to further the conversation. The answer Fin gave me is that this can only be accessed via a procedure.Is this the case? If so, I don’t understand why this functionality would be locked behind Fin procedures- there’s nothing fancy going on with this API call that requires AI.   

Hello team,Do Intercom have to option to change the sound for the ring when receiving the phone calls?Thank you

B2B SaaS company here. As it stands, when someone wants to add more seats to their shop, they have to chat in, we send them off to their CSM, they add the information to hubspot and send the customer off to finance, and then they send them to dev to add additional seats on the customer’s site.There has to be an automated way to do this, no? I totally welcome all thoughts here. thank you!

Hi Intercom team and community,I’m paginating through a company segment using the /companies endpoint and I’m seeing exact duplicate company records appearing on multiple pages.For example:GET https://api.intercom.io/companies?segment_id=xyz&per_page=60GET https://api.intercom.io/companies?segment_id=xyz&per_page=60&page=2Some of the same company records show up in both the page 1 and page 2 responses. Items are not updated between paginated queries.This makes it difficult to reliably process the full dataset without extra deduplication logic.Is this expected behavior for the Companies API? And is there a recommended way to retrieve a segment’s companies without duplicates across pages?

I was looking at functionality which points out and flags potential duplicate conversations and I was wondering if it was possible to either..Extend its existing functionality to do other arbitrary things (like tagging/closing conversations, sending webhooks, etc..). Maybe Intercom provides an interface or API to do this though I haven’t seen it. Reproduce this duplicate conversation flagging behavior without necessarily having direct access to Intercom’s own implementation (unless Intercom is willing to provide access to this). I’m guessing there might be a set of APIs that could make this possible but using them might introduce delays in the system that could result in unattended side-effects/race conditions.

Hello everyone,I would like to ask for your support and ideas to help resolve an issue I have been facing for some time regarding our service SLAs.We currently work with different SLAs depending on the type of request. In many cases, a ticket that starts as a general inquiry ends up becoming an error or incident, so I need to change the SLA to the one applied to errors, since it allows more time for resolution.However, in the SLA configuration, I set the system to disregard the time when the ticket is snoozed or waiting for the customer. The issue arises at the moment I change the SLA to another one: the period that was previously disregarded while the ticket was paused is no longer excluded in the new SLA. Instead, the system starts counting from the original opening date without applying any discount for the paused time.This has a direct impact on our reports, as it makes the SLA appear much more delayed than it actually is. It also reduces the available time to handle the ticket pro

Hi everyone,When support volume suddenly spikes, I’ve noticed it becomes harder to keep response times consistent, even with automation and routing in place. Conversations pile up quickly, and it’s not always clear which steps should be handled automatically versus manually.This came up in a discussion where someone mentioned structuring execution logic outside the main tool, like deltaexector.com, which made me think more broadly about handling load and prioritization. How do you usually manage high-volume periods without sacrificing response quality or burning out the team?Do you lean more on automation, temporary rules, or external helpers to keep things moving smoothly? Would love to hear what’s worked for others.

Hello,Currently, our team primarily uses conversations for the majority of our Intercom interactions, and Fin triages all incoming cases first. We would like to create a process wherein any time a conversation is escalated from Fin to a human team, it is also converted to a ticket. This is because our Fin deployment is at a point where if anything is escalated, it is likely complex and will take time to resolve.This doesn’t seem to be possible with existing workflows, since the “convert to ticket” action only works when a customer sends their first message. We also do not want all emails to be converted to tickets - Fin handles both email and chat. The conversion should only happen when there’s an escalation.Has anyone in a similar situation found a good solution to streamline this process?