Active since last visit

Hello everyone.I’m researching ways to improve social media marketing results and would like advice from experienced users. My goal is to increase engagement, manage campaigns efficiently, and understand which services provide reliable performance without risking account quality.I have seen many different providers mentioned online, but the reviews are mixed and often outdated. Recently, I came across the term telegram smm panel and became curious about how it compares with other marketing solutions.Does it offer measurable benefits, transparent reporting, and good customer support? What features, pricing factors, and potential risks should I consider before choosing a provider for long-term growth?

Hi,We’re struggling with Fin’s behavior outside office hours, and at this point it’s becoming a critical issue for us. We’ve been in contact with support, they are looking into it. We’d really like to hear if anyone in the forum has tips or experience with the same issue. Expected behaviorFin should run 24/7 Answer what it can Not escalate when we are closed Inform the customer to return during opening hours if needed Continue the conversation and close it after inactivity What is happening1. Conversations are escalated anywayFin sends the away message But still creates an open “unassigned” conversation These pile up into a backlog we explicitly do not want 2. Fin stops respondingThe Fin step is skipped completely Customers often receive the away message twice The conversation just stopsThis creates a very poor and confusing experience. 3. Conversations never return to Fin Previously:Fin continued after the away message Conversations were handled and automatically closedNow:Conversatio

Hi Intercom community 👋We're mid-deployment of Fin and have run into two issues I'd love input on - both from the community and from Intercom's side.1.Rule slot competition - scaling concernWe've noticed that rules are not being consistently retrieved during conversations, even when written with "ALWAYS" phrasing. This is a real problem for us.Some context:- The Fin Academy stated Fin can use up to 100 rules in a single reply- In practice, we're seeing what appears to be a 10–15 rule competition limit per reply- We're only in phase 1 of our deployment - we have 3 additional product areas to support, each requiring their own specific rules- Our sales contact from intercom indicated that the rules limit could be increased if neededMy questions:1. What is the actual enforced limit on rule retrieval per reply?2. If the per-reply competition slot is the real ceiling, does raising the total rules cap actually make a difference?3. Is there a recommended architecture for scaling Guidance rule

We would like more control over what is presented in the AI Summary for inbound phone calls.Today, the AI Summary for inbound calls is automatically generated and cannot be customized. It would be very valuable if admins could influence or enrich the generated summary based on captured attributes during the call.Example use cases: Identification number Store number Customer ID Order number Selected menu option / routing path If these attributes are captured during the conversation or workflow, it would be extremely helpful to: Include them automatically in the AI Summary Control how they are formatted/presented Prioritize important operational data at the top of the summary Example:“Customer called regarding invoice issue. Store number: 12345678. Routed via Billing queue.”This would make inbound call summaries much more actionable for support teams and reduce the need to manually listen back to calls or search for key identifiers.

When a Banner is active in Intercom, teams should have the option to make its content available to Fin as a knowledge source. When the Banner is paused or deleted, that content should be automatically removed from Fin's knowledge base without any manual steps.The problemBanners are commonly used to communicate important product changes, outages, or announcements. In practice, many customers dismiss or skim banners without fully absorbing the information. This generates avoidable support volume — customers contact support asking questions the banner already answered.Fin has no visibility into active banner content today, so it cannot answer these questions accurately or consistently, even when the information is current and relevant.There are existing workarounds — such as creating a snippet or article with the same content — but these require manual cleanup after the banner is removed. Without that cleanup, outdated information remains in Fin's knowledge base, which creates a different

We are testing Custom MCP with OAuth for a multi-tenant SaaS use case.Observed behavior: after one admin completes the OAuth flow, all Fin conversations appear to call our MCP server with the same OAuth token, even when the current conversation belongs to another customer/account.Can you confirm:Is Custom MCP OAuth stored at the Intercom workspace / connector level? Does Intercom support per-contact or per-company OAuth grants for Custom MCP? Can Fin trigger an OAuth authorization flow for the current end customer during a conversation? Can Custom MCP tools receive Intercom User Tokens from auth_tokens, or are User Tokens only supported by standard Data connectors? Does every MCP tool call include a stable Intercom workspace/contact/company identifier in metadata or only via configured tool input parameters? Is there a supported way to send a dynamic Authorization header per current Messenger user for Custom MCP? If not, is the recommended design to use standard Data connectors with Us

We have a number of products with a lot of overlapping terminology, and a lot of audiences that overlap with other audiences. This has made it difficult to target the information Fin uses very specifically. We have been considering setting audiences up using conversation data instead of just user data, but I’m having a hard time understanding if/how that would work. We have a new conversation attribute that would be selected and help define the audience for that conversation. But is that effective? If the customer asked another question in the same conversation, or had chosen something incorrectly, could the audience for that conversation ever be changed? Open to any suggestions here on how this could work, or what better options might be. 

It appears new features are regularly deployed without testing against multilingual use cases, we now have Procedures, and Recommendations incompatible with our workspace, seemingly due to multilingual articles.Great example of "garbage in - garbage out"If your database isn't ready for AI, funny things will happen, and I suspect the Articles database has some poor architecture in the relation to parent pages against their multilingual pages.Fin AI poorly executes against multilingual, time and time again. I am losing confidence that Intercom's multilingual articles are being considered in the new deployments of products.Recommendations breaks with multilingual, Procedures break with multilingual. Hoping this is fixed soon!

Hi everyone,We’re using Fin in Hebrew, but we keep seeing cases where Fin adds random English words inside Hebrew replies, even when those words do not appear in our Help Center articles or snippets.We also had a more serious case where Fin inserted Japanese/Chinese-looking characters into a Hebrew customer-facing reply.We already added clear Guidance telling Fin to reply fully in Hebrew and avoid English unless it is a brand name, URL, product name, or a required term. The issue still happens.Intercom Support suggested using Guidance and mentioned the multilingual glossary, but also clarified that the glossary does not apply to AI-generated replies.Has anyone using Fin in Hebrew or another non-English language found a reliable way to prevent this?Is this something Guidance can actually solve, or is this a current limitation of Fin?This is affecting customer trust, so any practical advice would be appreciated.

We have 100+ physical audio technology products (along with manuals for all of them). Additionally many of them have similar names. First, we need Fin AI to differentiate these products. Second we need to have Fin AI be able to do troubleshooting and give product recommendations. What would be the best practice for getting Fin AI to differentiate our products, and not make any up.Additionally, for troubleshooting, are we best off letting Fin-AI just try to handle it, or should we create procedures that run customers through their problem. Let’s say we choose procedures, how should I make sure Fin AI uses the relevant content (correct manual) for every device? 

Hello Intercom Community!We have been live with Fin for just over a year now. We began small with a subset of beta users, then went live with all users on our Cloud platform on January 1st 2026. While there are bumps and dissenters, overall the reception was positive and we saw steady growth/use AND witnessed a direct decline in the number of support cases, which is one of the primary goals.HOWEVER. We seemed to have plateaued and are now seeing a change in Customer behavior as users are actively avoiding Fin: while the number of daily chats remains about the same (as we are adding new users weekly), we have seen a steady increase in our support call and email volume over the last 2-3 months (see the below chart which clearly shows this shift in behavior; Fin is replacing the ‘In-app’ support channel, but notice how the Call and Email channels are now steadily increasing).Note: We currently have Fin setup to only act as a ‘first line of defense’ on questions, and he does NOT interact 

I want to ask how people feel about the Support in that specific interaction, and how they feel about our product overall. I can’t add two CSATs with intercom because one overrides the next. Is there an App you recommend to get this feel? 

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?

Hi everyone, I’m developing a Morse Code Translator website that converts text into Morse code and decodes Morse code back into readable text using an external API. The website supports real-time translation while users type, but I’m experiencing problems with API performance and response handling during continuous input activity.The main issue is that rapid requests sometimes cause delayed responses, incomplete translations, or timeout errors. In some cases, older API responses overwrite newer ones, creating inconsistent output on the frontend. I’m also facing occasional rate-limiting and CORS-related issues while handling multiple asynchronous requests through JavaScript Fetch API.I’d like to know the best approach for optimizing real-time API requests in this kind of application. Should I use debouncing, throttling, or request cancellation to improve performance? I’m also looking for recommendations on managing async requests efficiently and reducing unnecessary API calls while keep

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!

The current dark, blurry, transparent background in the main conversation area makes messages hard to read and feels distracting. Please add a setting to let us choose a solid background color for the larger chat box where the conversation happens, so we can improve readability and match our site’s design.

Hello everyone,I am facing an issue with Intercom Push Notification when it is a cold start (App is terminated, you receive a Push Notification and this notification will wake the App). While testing on Simulator that, if i am running my app from Xcode, terminate the App (on Simulator, not on Xcode), send a message to my test user, wait the push notification, receive it, tap on it but when i tap on it, Intercom Messenger does not opens the modal chat, it keeps me on my WorkListView (WorkList is a subview of RootView, that appears after SplashViews finish animation and transit to WorkListView).I have already made installation (API Key, API ID and Push Notifications are enabled on Settings > Channel > Messenger > Install > Install for Mobiles), Apple Developer is already configured, when i open the Messenger on my App, i can send and receive messages. When App is open but in background i am able to receive and wake the app in the correct modal Intercom window chat, but only t

 Hey community,Trying to connect Intercom to our Discord server and hitting this error:"This bot can't join more servers as it has not been verified or is requesting gateway intents it has not been verified for."Fin confirmed the bot is pending Discord verification and there's no workaround. Raised it with Engineering Support, they confirmed it's a known bug, created a ticket, no ETA.A few questions:Is anyone successfully using the Discord integration right now? Was there a point where it worked and stopped, or has it never worked? Any workaround — e.g. does the server need to be a verified/community Discord server?Seems like a critical gap given Intercom is promoting it as a supported channel. Curious if others are affected.

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.

St. Augustine Furniture | Contemporary Designer Furniture Ponte Vedra | High-End Home Décor Store Near Jacksonville & Ponte Vedra: Discover our furniture showroom in St. Augustine, where designer furniture, curated home decor, and inspiring interior design come together for an exciting shopping experience. Serving St. Augustine, Jacksonville, Ponte Vedra, and beyond, each selection is crafted to elevate your space.

When uploading pdf/docx files, what is the best method to ensure that as much information as possible it kept? The initial PDF manuals are 100+ pages, and it seems to destroy any formatting there, and Fin AI seemingly has trouble reading it. I tried multiple methods. The most success came from converting to a markdown file using Claude, and downloading that as a PDF. However, that got rid of a lot of spaces (especially where there are charts), and only 2-3 headers actually got written as headers.

Fin AI will always give suggestions when a customer asks a question. Let’s say the customer asks about a device (we have physical products that require a little technical knowledge), Fin AI always responds something along the lines “What do you want to know? (for example: this thing, that thing, many other things) You might be able to do this or that”I would like to to answer the customer’s question and not give extra information unless absolutely relevant. However, no matter what guidance I give, it will not stop this behavior.

Hi,I’m using the Intercom Messenger SDK in a React application and I’m trying to pass contextual data onto the conversation as conversation attributes.For example, I want to set values such as:workspace_name workspace_id current_url subscription_plan item_id item_title item_urlThese values are specific to the conversation the user is starting, as a user may be in different workspaces or different parts of the application at different times, so storing this as user attributes is not appropriate because the values can change from conversation to conversation.Fin suggested updating user attributes via the SDK, but that does not solve the problem for us. We need the data attached to the conversation itself, so it can be used reliably in Workflows, Inbox, and downstream connectors.It feels like the Messenger SDK should support setting conversation attributes when opening or creating a conversation. I’d prefer not to make a separate REST API call to update the conversation after it has been

 Hi everyone,I am opening this feature request to address a recent and highly crucial update from Meta’s WhatsApp Business Platform ecosystem: the official support for WhatsApp Coexistence.During my interactions with the Intercom support team, there seems to be a misconception that using the WhatsApp Business App and the Cloud API simultaneously on the same phone number is either unofficial or a workaround. I want to clarify that this is now a fully official feature documented and supported by Meta, and having Intercom support it natively would be a massive game-changer for many businesses.What is WhatsApp Coexistence?Meta now officially allows businesses to register and use the same phone number concurrently across the WhatsApp Business App (mobile/web) and the WhatsApp Business Platform (Cloud API).When configured correctly via Cloud API, this setup enables: The Best of Both Worlds: Centralized multi-agent support inside Intercom via the API, while maintaining the ability to make/rec

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?