Active since last visit

Product or tool name: Airia (https://airia.ai)Exact redirect URI to review:https://auth.airia.ai/OAuth/callbackMCP endpoints targeted: both https://mcp.intercom.com/mcp (US) and https://mcp.eu.intercom.com/mcp (EU). We have EU-hosted customers whose Intercom workspaces are on app.eu.intercom.com, so the EU endpoint is a requirement rather than a nice-to-have. Both authorization servers reject the URI today, so we'd need the allowlist entry on each. Use case and distribution model: Airia is a multi-tenant SaaS platform. Each end user authorizes their own Intercom workspace through OAuth 2.1 authorization code with PKCE (S256); tokens are held in our credential store, encrypted at rest, scoped to the authorizing user, and never shared between users or tenants. Registration is one client per tenant, with per-user authorization on top. Distribution is direct to our own enterprise customers, where Intercom appears as one connector in our integration library, not resold or white-labeled.We h

Hi, does anyone have a current workaround for syncing date fields from Salesforce to Intercom without the date shifting due to timezone differences?We’re sending renewal messaging from Intercom using a Renewal Date field mapped from Salesforce. Unfortunately, the date is syncing as one day earlier than the date in Salesforce. Intercom Support explained that this is because the sync occurs at UTC 0, which is causing the incorrect renewal date to appear in our customer notices.Has anyone found a way to prevent this timezone conversion? Or is the best workaround to create a secondary Renewal Date field in Salesforce that adds one day to the actual renewal date and map that field to Intercom instead?

Hi everyone,We’re trying to build an Intercom Data Connector that retrieves customer-specific data from our backend.Our backend API requires a user-specific access token. This token is generated only after the customer completes an OTP/authentication flow, and each customer receives a different token.The flow we want to support is: The customer completes OTP authentication. The OTP/auth connector returns a response containing: { "data": { "access_token": "..." }} A second connector should then call our recommendations API using that token in the Authorization header: Authorization: Bearer <data.access_token>The issue:When we try to pass the token dynamically in the connector header, for example:Authorization: Bearer {{accessToken}}or by using a value returned from a previous connector/action, our backend does not receive the Authorization header/token.The only setup that worked was using Intercom’s Authentication Token feature with a static Text token. However, this does n

Hi,I’m trying to connect Intercom to Marketo through the Marketo app from the Intercom app store.I have the Client, Secret ID and the API subdomain.I have this error message : “We couldn't save this app's settings. Try again in a minute”Is anyone have this issue?

Do you have any plans to support Icelandic in Intercom help center section? If so, is there an estimated timeline for when it might become available?

New Support Stack episode: I sat down with ​@Brian Branca , AI Conversation Designer at Fin, on when a Fin Procedure is actually the right tool (vs when your knowledge base should have handled it instead).A customer told Brian's team they'd hit a really high resolution rate, then added "by the way, we haven't added any procedures yet."We also got into Operator now it's generally available. It'll take you from a blank canvas to a first draft in a couple of minutes (it built eight conditionals and the sub-procedures for me while I did the thinking). What it can't know is what your customers actually expect from you, so that still all yours.Watch Brian's first episode now

We’re building a personalized onboarding experience using a Fin Procedure and two custom Data Connectors.The customer first receives this static welcome message through an Intercom Workflow:Hi, I’m an agent designed to help guide you through the product. I have a personalized suggestion for you. Would now be a good time to share it?When the customer responds with “Yes please,” Fin triggers the Procedure, retrieves their recent product activity and onboarding progress, and recommends one relevant action.Live test environmentThe experience can be tested here:https://twentycrm.demo.autoplay.ai/Suggested reproduction steps:Open the demo. Navigate between a few product areas, such as Companies, People, and Notes. Open the Intercom Messenger. Start a new conversation. Wait for the personalized-suggestion welcome message. Reply “Yes please.” Measure from Fin’s “I’ll look into that for you right away!” message until the personalized recommendation begins.Current Procedure structureThe Procedur

Test Environment:OS: Windows 11 version 25H2 (OS Build 26220.7523)Browser: Edge (Version 151.0.4129.15)Screen Reader: NVDA (2025.3.2), JAWS (2026.2512.50), NarratorURL: https://help.enlyft.com/en/articles/11242176-enlyft-web-browser-extension-download User Impact:Users who rely on screen readers cannot understand the purpose of the iframe because its name is not announced. This makes the video content inaccessible and prevents users from deciding whether to interact with it. Pre-Requisite:Turn on Screen Readers: NVDA: Ctrl + Alt + N JAWS: Ctrl + Alt + J Narrator: Ctrl + win + Enter Verbosity: NVDA: Default JAWS: Beginner, Highest Narrator: Default Repro Steps:Open the URL: https://help.enlyft.com/en/articles/11242176-enlyft-web-browser-extension-download in edge browser in windows. Press down arrow key to navigate to the YouTube video in browse mode. Verify whether Screen reader announces the name for iframe present on YouTube video in windows or not.Actual Result:Screen reader do

Test Environment:OS: Windows 11 version 25H2 (OS Build 26220.7271)Browser: Edge (Version 143.0.3650.75)Screen Reader: NVDA (2025.3.2), JAWS (2025.2508.120). NarratorURL: https://www.intercom.com/help/en/articles/9639255-getting-started-with-intercom User Impact:Screen reader users will miss the ‘Did this answer your question?’ label for feedback controls, making it unclear what the controls represent. This can lead to confusion and incorrect responses during feedback submission.Pre-Requisites:Enable NVDA Repro Steps:Open the URL: Getting started with Intercom | Intercom Help in edge browse in windows. Intercomm page will open. Press tab key to navigate to the Feedback controls. Verify whether Screen reader is announcing the 'Did this answer your question?' label for the feedback controls in windows or not.Actual Result:Screen reader is not announcing the 'Did this answer your question?' label for the feedback controls in windows.NVDA announces: Disappointed Reaction toggle button not p

Very much missing the endpoints for viewing/editing Fin guidance & escalation rules. We don’t want to do it via the UI, we want our internal AI agents to reason about how to adjust Fin. Currently sort-of can automate it via Playwright but that’s only a workaround.Endpoints for editing workflows would be good too.Any plans to add any of that in near future?

One of the biggest challenges in outbound sales is not generating leads — it’s following up with them consistently.Sales teams often have to call leads multiple times, check whether they are still interested, answer basic questions, and pass qualified leads to the right person. This can take a lot of time.AI voice agents can help automate this part of the process.For example, an AI voice agent can:Call new leads shortly after they submit an enquiry Follow up with leads who didn’t respond earlier Ask basic qualification questions Handle common queries Identify interested prospects Schedule a call or demo with the sales team Update the lead status in a CRMThe main benefit is consistent follow-up without making sales teams spend their entire day on repetitive calls.It doesn’t necessarily replace the sales team. Instead, it can handle the initial follow-up and let sales representatives focus more on qualified conversations.For businesses handling a large volume of outbound leads, this can

When viewing tickets in the Ticket Portal, users cannot filter to "all non-closed tickets" with the current filter UI.ProblemOnly one State filter can be applied at a time. After a State filter is set (e.g. "State is any"), State is no longer available under "+ Add filter" — only other variables appear. Users cannot combine or exclude multiple State values.ImpactMulti-ticket customers must scroll through closed tickets to find active ones.Requested behaviorOne of:Allow multiple State filters (include/exclude combinations), or A single filter option such as "Exclude closed/resolved", or A preset view for "Active tickets only"Environment: Ticket Portal, logged-in users with ticket history.

Hi Intercom team,We’d like to request support in the Intercom Android SDK for the new FCM registration flow based on Firebase Installation ID (FID):https://firebase.google.com/docs/cloud-messaging/android/get-started#enable-registration-via-firebase-installation-idFirebase Messaging 25.1.0+ introduces the new FID-based registration flow, including:firebase_messaging_installation_id_enabled=true FirebaseMessagingService.onRegistered(installationId) using FID instead of the legacy FCM registration tokenSince the Intercom Android SDK already uses Firebase Messaging 25.1.1, we’d like Intercom to support this new registration flow as well, including registering and handling FID for push notifications.Please consider adding full FID-based registration support to the Android SDK.

Hello! Since view columns are stored locally in the browser’s cache, and clearing the cache resets the view columns' data to default, I developed a Tampermonkey userscript for my team to preserve selected/ordered table columns per view. Yesterday and today, it seems tests (or changes) have been conducted that caused the userscript to stop working, and the columns keep getting reset to default.Yesterday morning, the localStorage key was split into multiple different keys, causing our userscript to stop working. After a few hours into our day shift, the original localStorage key came back, and the userscript was working again. Today, the same symptoms were witnessedIs it expected that these changes made it to our environments? I’m more than happy to share more information if needed.

We've had multiple instances now that calls come in (get added to a team) but no-one can pick-up the call. Is configured, and we see a button in the conversation, but when we click on it nothing happens. Has anyone else experience this?

Hi all,We're seeing an issue after conversations are handed off from Fin to Zendesk:Customer messages are successfully reaching Zendesk Conversations are being assigned to agents as expected Agents can reply from ZendeskHowever, the customer never receives the agent response in the Messenger widget. Instead, the widget remains stuck on: "Waiting for a teammate" The handoff itself appears to be working correctly, so the issue seems isolated to agent replies not syncing back to Messenger after the conversation is assigned. Has anyone encountered this before or have suggestions on where we should investigate? Screenshot attached for reference, thank you in advance!  

I'm having trouble sending audio messages to customers via WhatsApp. I'm receiving the following error message:WhatsApp could not accept this media. WhatsApp response: Audio file uploaded with mimetype as audio/ogg; codecs=opus, however on processing it is of type application/octet-stream. Please choose a different file. However, I am recording the audio directly through Intercom using the "voice note" feature. Is anyone else facing this same issue? What can be done in this case? I opened a support ticket with the Intercom team, but they mentioned that due to high demand, this isn't a priority at the moment unless more cases are reported.

In the last few weeks, it appears Intercom’s behavior around handling copy/pasted email addresses have changed and I really don’t like it. I’m trying to quickly fill out an email template and want to replace a few PLACEHOLDERS with a plain text email address like test@example.com. But now the current behavior instead of replacing the text with email is just adding a mailto: link. So instead of “test@example.com” it becomes “PLACEHOLDER” .I don’t think there’s any universe where adding a mailto link to my intercom message would ever be desired. This is causing me about 2 extra keystrokes to deal with and in aggregate it’s quite annoying behavior and unwanted.

self‑only performance view in Workforce  (So an agent will only see their performance an not the whole team) - I believe this is in progress as per conversations with the Workforce team but just looking for an update.

Getting intermittent hard bounces from Outlook/Microsoft recipients:```550 5.7.515 Access denied, sending domain HELP.HUEL.COM doesn't meet the required authentication level.SPF=Fail, DKIM=Pass, DMARC=Pass``` Setup: domain SPF managed via Sendmarc, mail sent through Intercom → Sparkpost EU. DMARC passes via DKIM alignment, so by DMARC's own rules this should be fine — but Microsoft is rejecting on SPF specifically.I’m being told by Intercom that this is just an accepted loss with not being able to respond to these customers.  Anyone else experience this?  

 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

Hi Intercom Team,We're hitting intermittent errors from the REST API that appear out of the blue — not correlated with our request rate or any code change on our side — and that succeed when we retry a short while later.The responses come back as HTML (nginx), not the usual JSON. Two examples:404 Not Found — GET /companies/scroll, x-request-id: 000fb95rqvhcl5nf9to0 403 Forbidden — seen previously (HTML, no x-request-id / x-ratelimit-limit headers)We've increased our retry/backoff, which recovers most occurrences, but some still fail outright.This looks like prior reports:https://community.intercom.com/api-webhooks-23/getting-404-502-and-504-error-from-api-at-the-first-time-then-success-after-retry-10039 https://community.intercom.com/api-webhooks-23/api-requests-are-returning-403-4656Any help here would be pretty appreciated. Happy to share timestamps and more request IDs.Thanks,Faruq