Popular Topics

Hi all — I'm doing some research on how teams measure AI resolution quality, and there's one thing I can't find anyone talking about.My understanding of the billing mechanic: a conversation counts as resolved either when the customer confirms it helped, or when they stop responding without asking for a human. The second case is the interesting one. Intercom does deduct the resolution if the customer reopens *that conversation* later, even across billing periods, which seems like a genuinely fair correction.But it only catches people who come back to the same thread. If someone reads Fin's answer, decides it didn't help, and emails support@ three days later — or calls, or starts a fresh chat — that's a new conversation. Nothing connects it to the original, and from what I can tell there's no way to see that pattern from inside Intercom, because Intercom can only see the Intercom channel.So my question: **has anyone here actually joined their email or phone support data against Fin's res

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

Hello, I’m experiencing a problem where the Intercom chat does not open when a user taps on a push notification on iOS. I have implemented the Intercom React Native plugin as per the documentation, and the messaging functionality works perfectly. Notifications are received correctly, but tapping on them does not open the chat as expected. Environment Details: • Platform: iOS• React Native Version: 0.74• Intercom React Native Plugin Version: 8.1.0 Problem Description: • The Intercom messenger is fully integrated into my app, and users can send and receive messages without any issues.• Push notifications from Intercom are successfully delivered to the device.• According to the documentation, tapping on a push notification should automatically open the relevant chat within the app. However, this is not happening on iOS.• When I tap on a push notification while the app is closed, the app opens but does not display the chat. Instead, it remains on the previous screen or the home screen.• I

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.

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!

 We've had a difficult experience with Fin since the start. We never received any real onboarding or guidance, so we set everything up on our own.Later, our plan turned out to be too small, and we were billed roughly double in overage charges. We tried repeatedly to contact sales to upgrade to a plan that fit our volume, but never got a response.Our company has since decided to move to another provider. For several weeks now we've been trying to cancel, but there's no self-service cancel option, and it seems the only way is for someone at Fin to process it. Our messages through every channel have gone unanswered.We'd really prefer to resolve this directly, but if we can't get a response soon we'll have to consider a consumer protection complaint and legal options.Has anyone dealt with this? Is there a specific contact, form, or process that actually worked for you to cancel?

Hello,Does anyone have experience with the Intercom - Telegram connection?Any insights would help a lot. Thanks, Dilara 

Hi everyone,I work with the Vasy team, and we talk to retail store owners about their billing setups every week. One thing keeps coming up: people often pick a system for its long feature list, then use only a few of those features day to day.So I’d like to ask this community what you really need from POS billing software for retail.

Hi guys,As far as I know, currently there is no option for sending Whatsapp templates via REST API (correct me if I’m wrong). Whatsapp don’t allow sending messages via their API directly if the number is already connected to your system. That leave us without options in order to have only 1 single point of contact number for receiving user’s questions and being able to automate templates for our users. Other competitors (like Messagebird) already allow to send whatsapp templates via their API.So the question is, is there any plan to allow this in your API? Is there any ETA? This feature is quite important and if there is no plan to implement it would make customers contemplate switching providers. Thanks in advance.