Active since last visit

We're currently experiencing compatibility issues when using Intercom alongside other push notification platforms, and we'd like to understand whether FID support is on your roadmap.If a migration is planned, could you share an estimated timeline?Thanks!

Few of our identified users on iOS see “Something went wrong” when user opens the Messenger.  Calling Intercom.logout() and then logging the user in again fixes it. We cannot reproduce it on demand, and no error reaches our app.EnvironmentIntercom iOS SDK via SPM - 19.5.7. Some affected builds were on 19.7.2. iOS version: > iOS 15 Identity verification: enabled. We call Intercom.setUserHash after loginUser(with:). Setup: setApiKey at launch, loginUser(with: ICMUserAttributes) with userId, email and company after sign-in, then Intercom.present() from a Settings → “Chat with us” row.ExpectedIntercom.present() shows the Messenger for a logged-in user.ActualThe Messenger opens with a “Something went wrong” error screen.ObservationsLogging out of our app (which calls Intercom.logout()) and logging back in fixes it loginUser’s completion handler returned no error that we could observe.Lifecycle, in the order our code runs itAt launch and after sign-in, we call Intercom.setApiKey(_:forAppI

We've recently been experiencing an issue with the Data Export API.The export jobs are submitted successfully, but when polling their status, the API returns in_progress a few times before eventually returning the following error:{ "errors": [ { "code": "service_unavailable", "message": "Sorry, the API service is temporarily unavailable" } ]}The transition from in_progress to this error often happens within just a few minutes.An example export job ID is 8ejdlg23rdolf8l2.This has been happening consistently with recent export request.

Hello,  We are starting out with intercom and struggling to verify outbound messaging, I used auto configuration and everything got updated in Cloudflare, but I am still seeing Warning on Outbound Messaging, here is what I am seeing https://ibb.co/s94ZrnSq (Not sure why I cannot upload image here)I can manually configure it in cloudflare, but I don’t know what are TXT record values, is there anyway to see those values so I can manually change in cloudflare?ThanksKets  

Hey Everyone!We have data of conversation, conversation parts, contact, and company to our datawarehouse, extracted using Intercom API.Now, we are trying to replicate one table that our client has built in the Intercom Reports which basically shows the conversation with bug tag across the companies. It’s a really basic table, containing the following columns:Conversation ID Company ID (from Company Standard Attribute) Company Name (from Company Standard Attribute) Conversation Tag Some more additional fieldsNow, we are able to create the most of the fields from the API data. However, we are facing the issue for the Company ID and Company Name.For example, in Intercom report table, a single conversation has 8 companies (as comma separated string) in the Company ID and Company Name. While in datawarehouse we have around ~52 companies.For the datawarehouse logic, we are using contact as the a bridge to map the conversation data with company. In datawarehouse the flow is Conversation → Con

When an agent starts a new outbound email (Inbox → + → Conversation → Email), the ID field in the sidebar shows “—” until the email is sent. Our agents need the reference number while writing the email, to log it in our back office. Today they have to send first and then go back to copy it.The only way to get an ID before sending is to create a Customer ticket first, which is much slower than a simple email.Request: give a new outbound email its conversation ID as soon as it’s started, and show it in the sidebar before sending, the way Freshdesk shows a ticket number from the start.

Why is there no option in workflow builder to Expand all paths, similar to Minimize all paths option?There is only Expand all paths in view, but we have to scroll horizontally and click on it several times to expand all the steps and have a complete overview.

Hi everyone, I'm running into an issue while configuring the Intercom Messenger widget to trigger based on dynamic session states. We recently added the standard JavaScript snippet across our website to offer quick help for users encountering setup or download issues, but the chat bubble frequently fails to load for visitors using specialized Chromium-based desktop wrappers.Alongside the initialization hiccup, user attributes like operating system and client build numbers are either delayed or drop out completely before reaching the conversation inbox. Has anyone experienced similar script conflicts or timing issues when running Intercom on a dynamic web application, and is there a recommended way to delay the boot script or adjust Content Security Policies to ensure stable tracking?

Hello everyone,I’m glad to be part of the Intercom Community. As a new member, I look forward to learning from other users, sharing ideas, and participating in discussions about customer communication, support experiences, and customer engagement.I believe that exchanging knowledge and real-world experiences can help us understand different challenges and find better solutions. I’ll make sure to follow the community guidelines, respect other members’ perspectives, and keep my contributions helpful and relevant.I’m excited to connect with fellow members, learn how they use Intercom in their daily work, and discover new ways to improve customer interactions.Thank you, and I look forward to learning and contributing to the community!

Hey everyone 👋 I'm an indie founder building ChatShield, a tool that helps support teams identify potentially risky conversations across their workspace not just AI chatbot replies, but human-agent conversations too. For example, an agent might accidentally promise an unauthorized refund, make an incorrect pricing commitment, or share information they shouldn't. I'm trying to understand how Intercom teams currently catch these issues. A few questions: - Do you manually review conversations, use internal QA, or have another process?- Are mistakes by human agents as much of a concern as AI-generated replies?- Would automated flagging of conversations for human review be useful to your team? I'd genuinely appreciate hearing how you're handling this today. I'm also looking for a few Intercom teams willing to test ChatShield and give honest feedback. Product: https://chatshield.cloud/ Thanks!

TextSpeed WhatsApp Business API helps businesses connect with customers through automated, secure and scalable WhatsApp communication. Use the API for notifications, customer support, promotional campaigns, order updates, authentication and chatbot conversations while creating personalized customer experiences at scale.

Product Design Services | OEM Engineering Partner | DFM & Hardware Engineering - DEM Manufacturing: An engineering extension of your team. Get U.S.-based product design services with custom electronics, hardware engineering, and DFM built in, moving you from concept to production faster.

It would be wonderful to have a Intercom native feature where you could set up a alert threshhold feature on a chart that informs dedicated stakeholders if the volume was hit (without requiring periodic review). Examples might be: - If CX score hits X% - If conversation volume exceeds X conversations - Etc. We have a lot of busy stakeholders managing multiple different tasks, and things can fall below the radar. But this way you could draw peoples attention, without them having to cut out time daily to review dashboards to check performance across different releases.

Hello,We use Intercom for customer support for our SaaS product and would like to be able to display the exact time under each message (for example, “3:50 PM” or “8:31 AM”), instead of the elapsed time (“16 hours ago,” “2 days ago”).We know that the date and time are visible when you hover over a message, but having to hover over every message makes it less convenient to review conversations, especially when trying to understand the time intervals between two replies.Would it be possible to add a setting that lets us choose between the current relative display and a permanent display of the exact date and time?Is this option already on your roadmap?Thank you!Wendy

Hi, we use Intercom’s Customer Portal. Our customers need to review and prioritize their tickets from the list without opening each ticket individually.Our main request is a Priority column alongside the existing Ticket state column. The portal currently says “All columns are visible,” but Priority is unavailable.We would also like these basic list features: Display customer-visible custom ticket attributes as columns. Filter and sort by priority and ticket state, including custom states such as “Work in progress.” Reorder and resize columns, and save the selected layout and filters. Show a short preview of the latest customer-visible update so customers can understand what changed. Ticket state and sorting by last updated are already available. However, a customer has also reported that filtering is not working. Could you help investigate that separately and confirm what examples or recordings you need?Please log the missing capabilities as product feedback and let us know wheth

hi,I was wonderig if there were plans to allow us to use the Free Salesforce Integrations licenses for integration between Salesforce and Fin.Thanks

Description:We run several brands in one workspace, with chat, email, overnight Fin coverage and multiple languages. These are the gaps we keep hitting, roughly in order of impact:Brands and what customers seeA customer-facing name per brand, separate from the internal brand name. Brand names must be unique, so ours include internal suffixes. That internal name then shows in the Messenger header, in the “[Teammate] from [Brand]” sender line of chat replies sent by email, and in the email footer. Setting a display name on the sending address doesn’t change it. Editable footer and wording on conversation notification emails without building a full custom template for every brand. Brand detection for BCC’d emails. Customers often email many companies at once and put our address in BCC. These arrive with the default brand, and workflows can’t set the brand automatically.Fin AI AgentControl over the transition line when a procedure starts (“Let me look into that for you…”). It’s sent before

Enable users to view a public article in the Help Center while logged in, and via a direct link without being logged in, without having to duplicate the article→ Users : can view the article through the Help Center if they are connected→ Can also view the article through a direct link our team shares before they sign in or if they are not logged in 

We recently integrated the Intercom Messenger widget on our support portal at cepcutapk.com to assist visitors with troubleshooting guides and template downloads. However, several mobile visitors browsing through our tutorials for capcut video projects are reporting that the chat launcher freezes completely or takes over ten seconds to render when loaded within Android in-app webviews.In addition to the UI lag, automated bot workflows fail to trigger during these sessions, and custom attributes passed via the JavaScript boot script seem to drop unexpectedly when users switch browser tabs. Has anyone experienced similar messenger initialization delays on content-heavy mobile sites, and is there a recommended deferral or initialization workaround to maintain performance?

Connector bug for your reportSymptom: create_article and update_article fail with "This connector requires additional permissions. The user needs to reconnect it from connector settings." Reconnecting doesn't help, because it isn't a real permissions problem. Cause: I bisected it. Any body containing the literal string ${env:<anything>} is rejected, even ${env:MY_SERVICE_TOKEN}. Size, HTML, tables, JSON, ${IPAAS_API_KEY} and ${input:…} all pass on their own, but the full draft stayed rejected until the ${env: string was removed. Why it hit you: it only triggers on content like Cursor's config syntax. Any article documenting that fails, and the error points you at the wrong fix. Workaround I used: writing the placeholder as ${env:IPAAS_API_KEY}. Intercom decodes it, and the read-back showed the stored text as a literal ${env:IPAAS_API_KEY}. I applied the same encoding to the VS Code ${input:…} placeholder as a precaution, without testing it separately. I got past a gateway

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?

When a caller has a hidden/private number, Intercom Phone cannot receive the caller ID and therefore has no phone number available for a callback.Today, these callers can still be presented with the option to request a callback, even though the callback cannot be completed. This creates a confusing customer experience and may lead customers to believe they will receive a callback that is technically impossible.I would like to suggest adding a condition/check before the queue-or-callback choice is presented. If no caller ID is available (anonymous/private number), the callback option should automatically be hidden and the caller should only be offered the option to remain in the queue.This would help avoid failed callback requests, reduce customer confusion, and create a more intuitive phone experience.

For teams doing this reconciliation today — is it entirely internal, or does anyone use an independent third party to verify a sample of Fin-reported resolutions against backend evidence?I’m especially curious where the Fin outcome has a commercial consequence: refunds, cancellations, account changes, or outcome-based billing.And when the backend evidence disagrees with the reported resolution, does that feed into what gets treated as a successful/billable outcome?

Hi,We’re experiencing an issue with the Calendly integration inside the Intercom Messenger on iOS.The Calendly app is installed and configured in our Intercom workspace. The booking flow opens correctly and allows the user to select a date/time and enter their details, but submitting the Calendly form fails.Xcode shows the following error:[Intercom] ERROR - Tried to submit messenger sheet but there was a network error - HTTP Error: 400 bad requestThe same Intercom message and Calendly flow works on Android and proceeds past this step.Environment:Intercom iOS SDK: 19.8.2 Installed via Swift Package Manager (intercom-ios-sp) Flutter app using intercom_flutter Calendly native Intercom integrationWe also updated the Intercom Flutter plugin/native SDK, but the issue persists.Has anyone encountered this with Calendly Messenger Sheets on iOS, or is this a known issue with the current iOS SDK?

The search bar on the modern Help Center template doesn't return results for queries under 3 characters. For example, searching "플랜" (plan) or "가격" (price) returns no results, while "플랜이" or "가격은" (the same root word with a particle attached) works fine.This minimum length may work reasonably for English, where 2-letter inputs are often low-signal, but it's overly restrictive for Korean, where 2-character words are frequently complete, high-value search terms. A language-aware minimum, or a lower threshold for CJK queries, would better serve non-English Help Centers.Could you let us know if this minimum length is configurable, or if there are plans to make it language-aware?