Hy ​@Malachi Hopoate Paul Here  

Fin doesn't provide an in-product way for users or teammates to directly tag outdated or incorrect content (like Help Center articles or Custom Answers) from within the conversation UI itself.

While there’s no native tagging flow yet, here’s a common workaround that some teams use:

1. Use Internal Notes: If a teammate or user identifies inaccurate Fin content during a conversation, they can leave an internal note flagging:

   • The issue spotted

   • The specific source (e.g., article link or Custom Answer title)

   • Suggested correction (if known)

2. Link to Content: Folks can then use that internal note to quickly jump to and update the original Help Center article or Custom Answer.

3. Assign to Content Owner: You could route those flagged conversations to a specific Inbox or teammate responsible for content QA, using a tag like needs-content-review.

You're not alone in wanting this! Many teams are looking for a “Mark as inaccurate” button or workflow directly inside the Fin answer. This would ideally:

• Capture the flagged text

• Show where it was sourced from

• Let editors jump straight to fix it

This is something we’ve shared with our product team, and your use case adds great weight. I’ll make sure it’s logged with your workspace attached for context.

Thank you for this response, ​@Paul Byrne! Do you by chance have links to those articles that would help me set up that inbox?  Also, is there a customer facing roadmap that users can view? 

Best,
Malachi

Hey ​@Malachi Hopoate, this came up for us too. We ended up using internal notes for now, similar to what Paul described, and then routed those tagged conversations to a content review queue.

We also used eesel to help sync and keep track of which articles were flagged and needed updates in Intercom. It made the process of finding and fixing outdated info a bit smoother for us.