Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3479 Ideas

    Chris ClarkNew Participant

    Custom web Intercom element styling (Messenger, Product Tour, etc.)Submitted

    The current styling options for Intercom elements are very limited and do not allow consumers to effectively apply UI design systems and/or branding. In addition, the Intercom elements render within and `iframe` element and thus cannot be targeted directly by application styles. This, as in our case, means a dark-themed website cannot adjust the Intercom elements to match their existing UI styles - the elements always render with a white background, for example.This can be quite jarring for users as any given element from Intercom will likely be the brightest thing rendered anywhere on a given dark-themed site. We, for example, are trying to use product tours as new features are launched, but the mismatch between our UI and that of Intercom means we lose any level of design alignment between our platform and Intercom.This idea is meant to be a request to expand the number of styling options available for all Intercom elements embedded within a given project - particularly the messenger and product tours. Even just component background/divider/text/etc. colors would add a level of customization that would allow companies the ability to align Intercom with the UI/design of their own products much more effectively.This could be implemented as additional options in the “Styling” sections of the relevant components, or additional fields in the Javascript API attributes - the latter already provides some styling options such as `vertical_padding` and `action_color`.

    Ja/Ko D1 TLNew Participant

    Option to make the CSAT comment field mandatory for low ratings, with a configurable minimum lengthSubmitted

    Hi Intercom team What we'd likeAn admin-level setting that makes the CSAT comment field mandatory when a customer selects a rating at or below a configurable threshold. Today the comment box is always optional, so a large share of our low scores arrive with no explanation at all.Two settings would cover it:Require a comment for ratings below X — where X is set by the admin. We'd set it at 3, but other teams may only want it for 1–2. Minimum comment length — a configurable character minimum (e.g. 10), so a single dot or a space doesn't count as feedback.Expected behaviour on the customer sideThe customer taps a low rating, the comment field appears, and the submit button is disabled. The button stays disabled — with clear helper text such as "Please tell us what went wrong (at least 10 characters)" — until the minimum is met. Nothing is recorded until the comment is submitted, so the customer immediately understands why they can't proceed. Whitespace-only input and a single repeated character shouldn't satisfy the minimum. Helper/validation text should be editable and translatable, like other Messenger copy.Ideally this applies everywhere CSAT is collected: the Messenger conversation rating, workflow- and email-based CSAT surveys, and Fin resolution ratings. Consistency across channels matters — otherwise customers simply rate through whichever surface has no requirement.Why this matters to usUnexplained low scores are unactionable. We can't coach a teammate, fix a process, or follow up with a customer on "2 out of 5" and nothing else. CSAT feeds teammate performance metrics. An unexplained low rating directly affects someone's numbers, and we have no way to review whether it was fair. It skews reporting. A meaningful share of our satisfaction data carries no information at all, which makes the trend harder to trust when we present it internally. It discourages low-effort rating. Some customers click the lowest score reflexively, or repeatedly across conversations. A small amount of friction — you gave a 2, tell us why — filters out that noise, while genuinely dissatisfied customers are usually happy to explain.What wouldn't solve itWe're not asking for a way to exclude ratings from reports after the fact. Filtering a report doesn't change the score that was already recorded, and it still leaves us without the explanation we actually need. The value is entirely in the friction at the moment of rating: a rating that can't be submitted without a real comment is either explained, or not given at all.Functionally this looks like a contained change — a toggle plus a numeric field in the CSAT settings, and validation on the submit button — but it would significantly change how much we can do with our CSAT data.Thanks for considering it!

    Sandra W.New Participant

    Display Eligible Custom Answers in 'Show Conversation Events'Submitted

     **Category:** Feature Request | Fin AI Agent | Workflows## ProblemWhen reviewing conversations in the Inbox using "Show conversation events," we can see *when* a Custom Answer triggered, but we have no visibility into:- Which other Custom Answers were eligible to trigger for that conversation- Why a specific Custom Answer was selected over others- What the matching confidence level wasThis makes it difficult for support teams to:- Audit Custom Answer effectiveness- Identify gaps in Custom Answer coverage- Debug why a customer didn't receive the expected answer- Train and improve Custom Answers based on actual conversation context## Requested FeatureAdd a **"Custom Answer Triggers"** section to the conversation events timeline that displays:1. **Primary Match** — The Custom Answer that was sent (with matching score/confidence)2. **Eligible Alternatives** — Other Custom Answers that matched the customer's question (listed by relevance)3. **No Match** — When a question didn't trigger any Custom Answer, show why and suggest which Custom Answers could be created4. **Rejection Reason** — If a Custom Answer didn't trigger due to conditions (audience rules, timing, frequency limits), display the reason## Use CaseOur support team uses Custom Answers to automate common questions and improve Fin's resolution rate. Right now, we can only see that a Custom Answer fired, but not understand the matching logic or what alternatives existed. Having this visibility would help us:- Validate that the right answer was shown- Identify overlapping or redundant Custom Answers- Find opportunities to expand Custom Answer coverage- Improve our training data for better matching## Additional ContextThis aligns with Intercom's existing approach to transparency — similar to how "Troubleshoot Workflows" shows which workflow matched and why others didn't. Custom Answers deserve the same level of visibility for effective management.Would this be something the product team could consider? Happy to discuss further.Thanks!