Product Request: Customizable Article Reaction Workflow Trigger | Community
Skip to main content
Submitted

Product Request: Customizable Article Reaction Workflow Trigger

Related products:Fin & AI
  • June 11, 2026
  • 0 replies
  • 38 views

Matej Bosnjak

 

Hello Intercom community, 
 

When a customer clicks 😞 or 😐 on a Help Center article, Intercom automatically opens a conversation and sends a built-in reply:
German:

"Schade, dass du die benötigte Antwort nicht finden konntest. Möchtest du das Team noch einmal um Hilfe bitten?"

English:
‘It's a shame you couldn't find the answer you were looking for. Would you like to ask the team for help again?’

There is currently no way to:

  • Edit or replace this default message

  • Trigger a Workflow at the moment of the reaction

The "customer sends first message" workflow trigger never fires in this context because the built-in reaction flow opens the conversation automatically and takes over before any workflow can run.

Who is affected

 

Any team that:

  • Uses Fin AI Agent as their primary support agent

  • Wants to collect structured feedback on why articles fail

  • Cares about brand tone consistency across all customer touchpoints

What we want

 

Option A - Editable reaction reply text Allow admins to customize the default message that appears when a customer reacts negatively to an article - either globally or per Help Center.

Option B - Dedicated Workflow trigger for article reactions Add a new Workflow trigger: "Customer reacts to article" (with filter options for 😞 / 😐 / 😃) that fires immediately when the reaction happens - before any conversation is opened.

Ideal Workflow this would unlock

  1. Customer clicks 😞 or 😐 on an article

  2. A customizable message appears asking why the article didn't help

  3. Structured reply buttons are offered (e.g. "Too technical", "Missing information", "Didn't match my situation", "Something else")

  4. A short free-text follow-up is collected based on the button selected

  5. A closing message confirms the team will review the article

  6. The conversation is assigned to a teammate internally for action

Why this matters

  • Catches missing or unclear content early - before it turns into a support ticket

  • Provides structured data on why articles fail, rather than just a reaction count with no context

  • Enables teams to close the feedback loop and improve content proactively

  • Ensures a consistent brand tone across all Fin and Messenger interactions

Current workaround

None available. The built-in reaction flow cannot be overridden or customized.

Thank you for your cooperation. 

Best regards

Matej - reev
Senior Customer Support Manager