Fin Product Area

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.

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?

We have unique URLs for every page for a user. For example, User A home page URL is: toddleapp.com/platform/32476/unitPlansUser B home page URL is: toddleapp.com/platform/99172/unitPlans Will product tour work here?

Hi everyone,I'm hoping someone has run into this before.We're currently migrating our internal Knowledge Base into Intercom for Fin/CoPilot, but we're not manually creating each article in Intercom. Instead, we're uploading our existing documentation from Google Docs (exported as .docx) or as PDFs. We don't use Notion, Guru, or Confluence.The problem is that every upload loses a lot of its formatting, making the articles much harder for agents—and Fin/CoPilot—to read.I've already tried pretty much everything I can think of: Using Normal text only (no Heading 1, Heading 2, etc.) Using bold text instead of Word heading styles Keeping section labels (Purpose, Process, Before You Begin, etc.) as bold text on their own line Using bold for step titles (e.g. Step 1: Verify the order) with normal text underneath Keeping formatting very simple with basic bullet points Uploading both .docx and PDF versions The formatting still gets stripped or flattened during import.Has anyone success

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?

ive added the intercom chat widgte to my website, but it isnt appearing on the page. the website loads normally and ive checked that the intercom code in included. when i open the website link, the chat icon doent appear, is there a setting or url-related issue i should check?

 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

Fin doesn't read your knowledge base the way a person does. It reads structure, tags, and outcomes. Get those wrong during migration, and resolution rate suffers from day one — even if every article technically "moved."Across Intercom's customer base, Fin averages a 67% resolution rate. Top-performing teams hit 80% or higher. The gap between those two numbers usually comes down to migration quality, not the model.How Fin actually reads your knowledge baseFin doesn't treat your help center as a flat pile of articles. It uses hierarchy — Collection, Section, Article — to understand scope and context before it answers.Most help desks only support a three-level structure. Intercom allows a simplified Collection > Article path with no Section in between. That's fine natively. It's a problem in migration: if your source platform's categories don't map cleanly onto that structure, a migration tool has to guess, usually by dropping orphaned articles into a default folder. That default bucke

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.

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.

After a lot of testing, iterations, and working through the Intercom review process, I’m happy to share that ChatShield is now officially listed on the Intercom App Store. 🎉 ChatShield monitors customer support conversations across the workspace and helps teams surface conversations that may deserve human review whether the response came from an AI agent or a human support agent. It looks for things like: Unsupported promises or commitments Potential privacy/data issues Incorrect policy claims AI representation issues Potentially risky financial or compliance-related responses The goal isn't to replace human review or legal/compliance teams. It's simply to help teams find the conversations that are worth looking at instead of manually checking everything. This is still an early-stage product, so I'm especially interested in hearing from Intercom teams using AI or automation in customer support: How are you currently checking whether your AI/support conversations contain risky response

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?

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?  

We connected a POST API to SendGrid within our email workflow to capture FIN's response to users and store it as audit evidence in forwarded emails. However, we haven't found any parameter or attribute that exposes FIN's response text.Is there a way to create a custom attribute to pass this value, or do you recommend an alternative method to capture it? ​@Nathan Sudds 

Sharing how we're using Slack side conversations, plus one problem I'm hoping someone can confirm or work around.What we've builtOur technical support team has a private internal Slack channel with an always-on AI agent sitting in it (built on Claude, running in our own agent framework). There's no trigger word or slash command — you just start a new thread in the channel and the agent replies in that thread. It has read access to our internal systems (Jira/Confluence, GitHub, Sentry, our own product data), so answers come back grounded in real context rather than generic. It's become the fastest way for the team to get a sanity check mid-ticket.From Intercom, we can open a Slack side conversation on a ticket and post a question straight into that channel. That half works perfectly — the question lands, and the agent answers in the thread.The gapOnly human replies flow back into the side conversation in Intercom. The agent's replies never appear. I'm assuming that's because they're pos

We've all spent time improving Fin's knowledge, testing answers and looking at resolution rates.But I'm curious about what happens after Fin actually sends the answer.Say Fin tells a customer:“Yes, you can get a full refund.”…but your actual policy doesn't allow it.Or it gives an answer that sounds completely normal, but contains something your team shouldn't be promising.How are you catching those cases today?Manual QA? Monitors? Sampling conversations? Customer complaints? Or do they mostly get missed?I'm particularly interested in teams running Fin at meaningful volume. How are you handling this in practice?

Hey everyone 👋As Fin handles more customer conversations, I'm curious how teams are checking the actual responses being sent to customers.Not just whether Fin resolved the conversation but whether the response itself could create a problem.For example:promising a refund or exception that isn't actually allowedgiving incorrect pricing or policy informationmaking a commitment the business can't honorexposing sensitive customer informationgiving inappropriate financial or medical advicemissing an important AI disclosureThe difficult cases aren't necessarily obvious. A response can look perfectly reasonable on its own but become risky when you look at the customer's situation and the company's policies.How are you handling this today?Manual sampling? QA? Fin's monitoring tools? Internal rules? Something else?I'm working on this problem myself and would genuinely like to understand how other Intercom teams are approaching it.

I have great difficulties managing the Brand appearance once chat goes to email, due to the fact that I can only sign up with one email adress.  When I turn off using my own email Intercom will still show my workspace name in the generated email Even if it says "Viktor from Brand 1" or "Viktor from Brand 2" The email adress is still limited to one domain or Intercoms own. I cant be the only one working with multibrand setup. How do I grow if I cant customise my brands. Any advice / tips /workarounds?  Did not get lucky in Customer Support (BTW I have the possibility to edit different brand styles)

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.

Hi All, I’m wondering if there’s a report we can generate to see how many unique users sent us messages?I want to compare adoption between 2022 and 2023. Your help putting this together would be appreciated. Thanks! Michael

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?

Hi all,I'm building a labeling/tagging system for a fintech support team in Intercom and want to start simple, then expand.Context:Small support team handling inbound fintech queries (payments mostly) Using tags only for now (no custom attributes yet) Eventual goal: pipe tagged conversation data into a data warehouse for reporting/analysisWhat I'm looking for:Examples of tag taxonomies others have used for support (fintech) Is it ok to use inly tags and automated topics?  Pitfalls to avoid — tag sprawl, inconsistent application by agents, etc.Happy to share what I land on once it's live, in case it helps others in the same boat. Thanks in advance!

I'm evaluating Intercom because I'm thinking of switching from Freshworks (Freshdesk+Freshchat).My WhatsApp number is linked to Freshworks. If I switch to Intercom, can I unlink it and link it to Intercom instead? Gustavo

We’re going to stop using Fin AI. It’s a shame because the product itself is really good, but the pricing isn’t suited to marketplace business models like ours.With margins of around €1 per user per month (incl. VAT) and high volumes, the cost quickly becomes unsustainable.If possible, it would be great to share this feedback with your product teams internally — there’s likely a broader pricing vs. business model fit issue for marketplaces.