Unanswered questions

I see that there is an MCP available for US accounts, any idea when will that be available for Europe? 

Hi, Sending some feedback on the MCP integration from a developer use case perspective. We've ran into some major gaps/roadblocks when using the MCP: 1. Expose created_at filtering in search_conversations. The underlying API supports date filtering but the MCP tool doesn't expose it. Agents scoped to a time window have to paginate all historical results and apply the cutoff manually.2. Expose source.body text search in search_conversations. Again, supported by the API but not exposed in the MCP. Forces agents doing content-based retrieval to call get_conversation on every result individually.3. Add source.subject filtering to search_conversations. Not sure if this exists in the underlying API — if it does, same ask as above. If not, it's a genuine gap: for email-based workflows, subject line is the most reliable signal for identifying conversation origin.4. fetch drops source.subject from its output. get_conversation returns it correctly; fetch doesn't include it in its summary. Forces

We’re looking for insight from companies that manage multiple subscriptions per customer in Stripe.In our case, each account has three separate subscriptions: Base plan Email plan Teams plan Each of these also has multiple plan levels, and every customer technically has all three subscriptions (either free or paid).Right now, the Stripe integration appears to pull only one random subscription, which makes it difficult to reliably identify a customer’s actual plan levels across all products.How are you configuring your Stripe integration to correctly identify all subscription plans for a customer, rather than just one? Are you using specific metadata, workarounds, or a particular integration setup to handle this?For context, we are looking to use Procedures to perform account actions inside Stripe, but need to be able to accurately make changes to all plans.

We are a small team looking to maximize our efficiency with Intercom. We want to streamline our customer support and communication processes, but we're cautious about over complicating things with too many features. Find Out What are the best ways to set up workflows in Intercom that are simple yet effective for a small team? Are there any must-use features or strategies we should implement to keep things running smoothly? Additionally, how can we ensure our team remains organized and responsive while minimizing manual tasks? Any tips or information from others in similar situations would be greatly appreciated!

RTA Fine Check is an online service that helps drivers in Dubai and the UAE easily view, verify, and pay their traffic fines. Managed by the Roads and Transport Authority (RTA), this service makes it simple to track fines like speeding tickets or parking violations from anywhere. With RTA Fine Check, motorists can save time, avoid late fees, and keep their driving record clear through a fast and hassle-free process.

We are using the Intercom helpcenter and in the “header” section of the helpcenter, we added a link to a place where customers can login. Aim is that after a succesful login, the visitor creates conversations in the messenger as authenticated (JWT) users.Our problem now is that all the links in the helpcenter have:Target attribute with value “_blank” And rel attributes with value “noopener noreferrer”Is there a way to change this? Reason: I want to use the referer as a callback redirect url after succesful login. By instructing the browser not to add the referer, I cannot do this.  

When teammates are out of office (planned or unexpectedly), how are you handling their conversations that become unsnoozed? We use the Reassign Replies option to handle customer that reply to conversations assigned to an OOO teammate, but we’re struggling to know what to do with conversations that become unsnoozed without having someone monitor the inbox to keep it tidy.  We don’t want to use a workflow for when a customer has become unresponsive, because sometimes we’re waiting on an update from another team (like engineering). If you have solutions for this problem, too, I’m all ears. Should we do a back office ticket if we are waiting on the engineering team?  Thanks in advance for any suggestions! 

Hi everyone 👋We’re currently exploring how to automate our carrier loss/damage claims workflow using Fin AI and would really value input from anyone who has implemented something similar.ContextWe manage parcel claims (e.g. Royal Mail and other carriers) on behalf of merchants. Today, this process involves significant manual review, validation, routing, and follow-ups. Our goal is to reduce manual workload while maintaining a strong audit trail and strict compliance with carrier policies.What we’d like to automate: Collect structured claim data (tracking number, order number, carrier, reason, invoice, proof of sale, damage photos, etc.) Validate required fields and supporting documents Dynamically enforce carrier-specific rules (claim windows, liability caps, required evidence) Route complete claims to the right internal team or BPO Automatically follow up if information is missing Provide SLA-based status updates Support appeal flows if claims are rejected We’ve seen exam

We are currently attempting to test deployment of Fin for Zendesk Messaging and are encountering some issues where the Zendesk messaging widget is blank. We have tried multiple audience configurations with no luck.Why is the widget blank despite seemingly meeting the audience conditions and the deployment of Fin being live? Example of a conversation log in Fin of this:   When someone does not match the audience for Fin, shouldn’t they still experience the Zendesk Messenger/AI Bot or are they completely locked out of any messaging experience?

Hi!One of our customers uses Intercom, and in order to create a pipeline between our backend and their order processing workflow, we created an API account in Intercom which we set to our company’s email. The customer now wants to have full control of the API account, without having to fiddle with changing the API token. Will the API token remain functional if the API account’s email is changed? Thanks!

We have two Help Centers in our workspace:1. GreenPal Help Center — help.yourgreenpal.com (working fine, no issues)2. GreenPal Pros Help Center — pros-help.yourgreenpal.com (recurring issue)Problem:When we set the Pros Help Center to HTTPS (quick setup), it works initially but after some time it automatically reverts back to HTTPS (manual setup) and shows as "Not Live." We have to manually go back in and re-enable quick setup each time this happens.The main Help Center (help.yourgreenpal.com) has been on HTTPS quick setup for a long time with no issues.DNS Configuration (verified correct):- CNAME for pros-help.yourgreenpal.com points to us.intercomhelpcenter.com- Set to DNS only (no Cloudflare proxy)- Cloudflare SSL mode: Full (Strict)- No CAA records blocking certificate issuance- No conflicting SSL certificates at the DNS levelNote: Since both CNAMEs are DNS only, Cloudflare is not in the traffic path for either Help Center — so Full (Strict) mode should not affect certificate provis

Hi there — I’m wondering if anyone can share best practices for setting expectations in the Messenger that customers are not always in a real-time live chat with a support agent. As many of you probably experience, our agents often help multiple customers at once or may be briefly unavailable. However, some customers assume it’s a live chat and will send repeated messages asking if we’re there if we don’t respond right away. I imagine there must be a good way to set expectations through automated messages or Messenger settings, but I’m not sure where to start. Any suggestions would be greatly appreciated!

 This really annoys me;Why can I View and Bulk Edit the Fin Permissions of Articles in the view-all-articles screen, but I cannot view or bulk edit the Visibility Audience of the Article??Also, Why dosen’t Visibility Audience utilise the preset Fin Audiences, which are super useful, I have to manually configure entire collections of articles, the same rule sets each time, if that rule ever updates, I cannot easily find those articles, or edit the rules!Super infuriating, this set up is not a serious help centre for multi-country companies with variations of policy per user group.

Fin autofills ticket descriptions and titles, but in the language of the customer. This is a good feature for customer-facing tickets, but our 2nd line support are only speaking English. We need to be able to set the language of Fin’s auto descriptions. 

We’re migrating from Zendesk to Intercom.In our App, we have notes that preserve certain actions and any associated Zendesk tickets with URLs to that ticket, like https://{workspace}.zendesk.com/agent/tickets/12345.We’d like to record a direct URL to a ticket in the same fashion with Intercom. However, it’s not immediately apparent what that URL would look like.If I have just created an Intercom ticket via the API with id 12345, what would the URL to that ticket look like?

Fin Voice: Option to view what document or guidance the Fin Voice is using when answer the clients inquiry (same with email and chat). 

We have two Help Centers in our workspace:1. GreenPal Help Center — help.yourgreenpal.com (working fine, no issues)2. GreenPal Pros Help Center — pros-help.yourgreenpal.com (recurring issue)Problem:When we set the Pros Help Center to HTTPS (quick setup), it works initially but after some time it automatically reverts back to HTTPS (manual setup) and shows as "Not Live." We have to manually go back in and re-enable quick setup each time this happens.The main Help Center (help.yourgreenpal.com) has been on HTTPS quick setup for a long time with no issues.DNS Configuration (verified correct):- CNAME for pros-help.yourgreenpal.com points to us.intercomhelpcenter.com- Set to DNS only (no Cloudflare proxy)- Cloudflare SSL mode: Full (Strict)- No CAA records blocking certificate issuance- No conflicting SSL certificates at the DNS levelNote: Since both CNAMEs are DNS only, Cloudflare is not in the traffic path for either Help Center — so Full (Strict) mode should not affect certificate provis

Hi there,I've been looking through Intercom documentation, and it seems like there's something called a Custom Channel and an event called "custom channel base event." However, when I dig a little deeper, it seems that’s somehow connected to Fin?Not trying to integrate a conversation with the Fin chatbot; rather, I am looking to use my own pipeline for our users to interact with my customer service team in Inbox.What I'm looking to do is integrate my custom app as a custom channel in Inbox so that our team can interact through our own managed integration via API.Does anyone know:How to access this capability? If this feature is gated? Whether usage of this feature is billable or if it is included in the standard subscription tier?Thank you!

A gold bracelet is a timeless piece of jewellery that adds elegance and style to any look. From classic designs to modern styles, a bracelet is perfect for daily wear as well as special occasions. At Sirius Jewels, we offer beautifully crafted gold bracelet collections that combine quality, luxury, and stunning design to suit every jewellery lover.  

A gold bracelet is one of the most elegant and popular pieces of jewelry worn by people all around the world. Gold has always been associated with luxury, beauty, and tradition. Because of its timeless appeal, gold jewelry continues to remain fashionable in every generation.  

Our workflows are fully set up in a non‑English language, with auto‑translate turned off. Fin detects the user’s language correctly, and the reply buttons display in the intended language — but the message text itself is being translated into English for the end‑user.From the backend side, the workflow appears completely normal in the language it was created in — the issue occurs only customer‑facing.This issue is currently preventing us from rolling Fin out in all 7 of our support languages, even though we’re very satisfied with Fin’s performance in English so far.Intercom support confirmed our setup is correct and has logged an internal ticket, but priority depends on whether others are affected.Is anyone else experiencing this?Would be great to know if this is impacting other workspaces too.Thanks! 🙏Ticket ID #79157183 

There is a vulnerability not fixed even in latest Intercom Android SDK 17.4.2:org.msgpack:msgpack-core should be 0.9.11 or greater|    +--- io.intercom.android:intercom-sdk-base:17.4.2|    |    +--- io.ably:ably-android:1.5.0|    |    |    +--- io.ably:network-client-okhttp:1.5.0|    |    |    |    +--- io.ably:network-client-core:1.5.0|    |    |    |    \--- com.squareup.okhttp3:okhttp:4.12.0 (*)|    |    |    +--- org.msgpack:msgpack-core:0.8.11Could you please update io.ably:ably-android to latest 1.6.1 to see if it fixes the vulnerability?Thanks!More Infoorg.msgpack:msgpack-core(Maven)< 0.9.110.9.11SummaryAffected Components:org.msgpack.core.MessageUnpacker.readPayload()org.msgpack.core.MessageUnpacker.unpackValue()org.msgpack.value.ExtensionValue.getData()A denial-of-service vulnerability exists in MessagePack for Java when deserializing .msgpack files containing EXT32 objects with attacker-controlled payload lengths. While MessagePack-Java parses extension headers lazily, it

Our company offers software which contains databases our end users need for their work. The databases sometimes use difficult terminology that is hard to interpret for our users. In an attempt to improve the ‘readability’ of the databases, I have recently uploaded a bunch of ‘metadata’ associated with the most used databases in our software - breaking FIN as a result.Prior to starting the upload December 2025, I had contact multiple times with my Intercom account manager to determine the ‘optimal’ way to upload a large amount of qualitative (text) data to Intercom. The data on our end originally is stored in JSON format - a format we can’t directly upload directly to Intercom. After some discussions, we opted to split the JSON file into smaller .txt files, which we manually uploaded as ‘snippets’ to Intercom. We have spent a considerable amount of time setting this up. Now the system is ‘stuck’ since Christmas 2025, with no viable solution yet in place. No new content we upload is inge