Unanswered questions

I can create a callout text block for use as Dynamic Content; however, I can’t change its colour in the same way I can when inserting the callout as regular text.

Connector bug for your reportSymptom: create_article and update_article fail with "This connector requires additional permissions. The user needs to reconnect it from connector settings." Reconnecting doesn't help, because it isn't a real permissions problem. Cause: I bisected it. Any body containing the literal string ${env:<anything>} is rejected, even ${env:MY_SERVICE_TOKEN}. Size, HTML, tables, JSON, ${IPAAS_API_KEY} and ${input:…} all pass on their own, but the full draft stayed rejected until the ${env: string was removed. Why it hit you: it only triggers on content like Cursor's config syntax. Any article documenting that fails, and the error points you at the wrong fix. Workaround I used: writing the placeholder as ${env:IPAAS_API_KEY}. Intercom decodes it, and the read-back showed the stored text as a literal ${env:IPAAS_API_KEY}. I applied the same encoding to the VS Code ${input:…} placeholder as a precaution, without testing it separately. I got past a gateway

For businesses that support mobile users, SIM registration can generate a surprising number of customer questions.Customers may ask things like: How do I check whether my SIM is registered? What information do I need for registration? What should I do if my registration details are incorrect? Does changing phones affect my SIM registration? Where can I find the latest registration requirements? I'm curious how other teams are handling these questions in Intercom.Are you using Fin, saved replies, Help Center articles, or custom workflows to answer SIM-registration questions? I'm particularly interested in how teams keep these answers accurate when requirements or procedures change.I've also been looking at the information that customers typically need when checking TM SIM registration and found this resource useful as a reference: https://tmsimregister.ph/ez99-tm/For anyone supporting customers in this area, what approach has worked best for reducing repetitive SIM-registration

Enable users to view a public article in the Help Center while logged in, and via a direct link without being logged in, without having to duplicate the article→ Users : can view the article through the Help Center if they are connected→ Can also view the article through a direct link our team shares before they sign in or if they are not logged in 

Hi,We’re experiencing an issue with the Calendly integration inside the Intercom Messenger on iOS.The Calendly app is installed and configured in our Intercom workspace. The booking flow opens correctly and allows the user to select a date/time and enter their details, but submitting the Calendly form fails.Xcode shows the following error:[Intercom] ERROR - Tried to submit messenger sheet but there was a network error - HTTP Error: 400 bad requestThe same Intercom message and Calendly flow works on Android and proceeds past this step.Environment:Intercom iOS SDK: 19.8.2 Installed via Swift Package Manager (intercom-ios-sp) Flutter app using intercom_flutter Calendly native Intercom integrationWe also updated the Intercom Flutter plugin/native SDK, but the issue persists.Has anyone encountered this with Calendly Messenger Sheets on iOS, or is this a known issue with the current iOS SDK?

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?

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?

Hi everyone, I’m working on improving the schema markup on my website, but I’m not sure if I’m using the right structured data for all of my pages. I’d like to know which schema types are most useful for content-focused websites and how to avoid common validation errors. Any tips or recommended tools for testing schema markup would be appreciated.I’m working on a manga website called Manga Hive so advice for content and manga-related pages would be especially helpful.

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?  

Hi everyone, it's Jahir from Analysis Vault. Over the years, I've realized that one of the best ways to deepen my own learning is by giving back to the community. I'm not here to pitch any services—just wanted to say a quick hello and let you know I plan to share any useful insights I come across.I know many of you here are highly experienced, so I welcome your feedback and corrections if I ever get something wrong. Likewise, if I spot a way to help you troubleshoot an issue, I'll be sure to chime in. Thanks!

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 

Hey Everyone, I just wondering some intercom users, I am working on Compliance Monitoring for Intercom users.

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