Better article context for Fin

Hi ​@Jay Reddy ! 

Do I understand correctly that your goal is to effectively nest Content and Sources Guidance under the articles themselves for easier maintenance? 

Hi ​@Aleksei O - yes, exactly. We’ve noticed that many of the “errors” are less about Fin providing incorrect information and more about a lack of contextual understanding. I think this largely comes from the way our articles are written from the perspective of the customer/contributor reading them.

For example, Fin sometimes doesn’t distinguish between an article intended for an existing customer versus one intended for a newly registered customer, even when the articles are clearly located within sections like “Getting Started” or “Account Maintenance” and explicitly reference new vs long-standing customers. While the content may be similar, the actions required can differ significantly.

From a Content and Source Guidance perspective, it would be far more convenient if we could define that context directly within the production of the article itself, rather than managing it separately through snippets and guidance layers.

This is just one example that could potentially be solved through customer start-date logic and audience segmentation. However, we don’t necessarily know when a customer transitions from “new” to “established,” since usage patterns vary by feature. Solving that through snippets alone would likely require much deeper backend connectivity and significantly more data sharing/context management.

The type of enhancement I’m thinking of is similar to how Intercom/Fin is developing AI Attributes — where values have internal descriptions explaining when they should appropriately apply, without exposing that information to end users.

So, when creating Help Centre content, it would be incredibly useful to have an additional internal-only section (perhaps another tab alongside “Data” in the right-hand pane) where teams could define contextual instructions, intended scenarios, operational nuances, and guidance directly against the article itself.
Ideally, id possible, anything entered there could auto sync to the existing guidance section, allowing for conflict detection or optimisation checks etc.