Skip to main content

Give Fin context about your customers using Data

Choose which customer attributes Fin can read, test them before they go live, and measure how personalization affects Fin's answers.

Customer attributes are what you already know about a person, like their name, email, or location. Fin reads them at the start of every conversation, so answers are personalized from the first message.

Use this article to choose which customer attributes Fin can read, test them before they go live, and measure how personalization affects Fin's answers.

Note: The Data Hub is currently in open beta. Features and functionality may change as we continue to develop this product.


Using Fin Data to personalize answers

The Data page (Train > Data) is where you choose which customer attributes Fin can read at the start of a conversation to personalize its answers. For example, Fin can tailor an answer to a customer's plan or region when those values are available as attributes.

The Data page has two tabs:

  • Data attributes: the customer fields Fin can read, such as People and Company data

  • Data connectors: the connections that let Fin read and write data in external systems

The customer profile and the Preview panel on the right side of the Data page let you pick a contact in the Testing as field. The page then shows the attribute values Fin would see for that contact.


Where do Data page attributes come from?

Data page attributes include the fields synced from your connected helpdesk or CRM. For example, with Fin for Salesforce, Salesforce Contact and Account fields are synced as People and Company data, and you can then enable them for Fin on the Data page.

To learn how data syncs, see:


Choose which attributes Fin can use

Each attribute on the Data page has a Fin status that controls whether Fin can use the attribute in conversations. The Fin status has three states:

Fin status

What it means for Fin

Enabled

Fin can reference the attribute in live conversations

Test

Fin can reference the attribute in test conversations only, such as the preview

Disabled

Fin can't reference the attribute

To set the Fin status of an attribute:

  1. Go to Train > Data, and open the Data attributes tab.

  2. Use the search bar or filters to find the attribute.

  3. Click the attribute to open its settings sheet.

  4. Add a Description. An attribute needs a Description before you can enable it.

  5. Set the Fin status to Test to try the attribute in the preview, or to Enabled to let Fin use it in live conversations.

After you enable an attribute, Fin references it in the next qualifying conversation. A qualifying conversation is one on a supported channel with a verified customer, as described in the identity verification section below.


Configure the attribute settings

The attribute settings sheet has these sections for each attribute on the Data page:

Section

What it does

Description

Explains what the attribute represents so Fin can interpret it. Required before you can enable the attribute.

Details

Shows 5 fields: Name (the attribute's name); Object type (for example, Company or People); Format (for example, Text or Date); Coverage (the share of customers (or companies, for Company attributes) with a value for this attribute, shown as "—" when it isn't available); and Referenced by Fin (the number of conversations where Fin referenced this attribute in its answer in the last 28 days).

Data transformation

Changes how the attribute's value reaches Fin. Choose Mapping or Code.

Audience

Choose which customers Fin uses this attribute for when personalizing answers. The default is Everyone.

Other guidance

Holds Instruct Fin to keep this value private and How Fin should use this attribute.

How data transformation works for an attribute

Data transformation changes an attribute's value before Fin reads it. You can choose Mapping or Code.

Note: Code transformations run on real conversations only. Their results aren't shown in the customer profile or the Preview panel on the Data page.

Keep an attribute value private from customers

To keep an attribute value private, turn on Instruct Fin to keep this value private in the Other guidance section. Fin can still use the value as context, but it's told not to share the value with the customer. This option is in Beta, and it isn't guaranteed that Fin never shares the value.

Tell Fin how to use an attribute

To give Fin direct instructions about an attribute, add them in How Fin should use this attribute in the Other guidance section. Fin performs best when each attribute has a clear Description and any data transformation it needs.


When does Fin use personalized attributes, and how does identity verification apply?

Fin uses personalized attributes only when the customer's identity is verified on the channel, and only on the channels listed below. Identity verification confirms who a customer is before Fin accesses their data. The Fin Messenger uses personalized attributes when Messenger user verification is set up.

Channel

What you need for Fin to use personalized attributes

Fin Messenger on web

Messenger security enforced, with JWT user authentication

Fin Messenger on iOS and Android

The secure SDK (software development kit)

Fin Agent API (application programming interface)

Identified users

Note:

  • Fin doesn't use personalized attributes on helpdesk ticket channels, such as Salesforce Cases, Zendesk tickets, Freshdesk tickets, or HubSpot tickets.

  • Fin uses personalized attributes only when the conversation has exactly one customer participant.

  • The Preview panel and the customer profile show attribute values whether or not a customer is verified. Testing there doesn't confirm that a live channel is verified.


Measure the impact of personalized attributes on Fin

To measure how personalized attributes affect Fin's performance, use these options:

Option

What it shows

Report filter

Filters your reports to conversations where Fin referenced personalized attributes

Conversation event

Shows "Fin referenced personalized attributes" in the event log of a specific conversation, so you can confirm Fin used attributes there


FAQs

Who can configure the Data page?

Teammates whose Fin AI Agent & Automation permission lets them change Fin configuration can configure attributes on the Data page, including the Fin status. Adding or editing an attribute's Description also needs the Can manage workspace data permission.

Why isn't Fin tailoring its answers based on my customer data?

Fin might not tailor its answers to customer data for several common reasons:

  • Unsupported channel or unverified customer: Fin doesn't use personalized attributes on helpdesk ticket channels, or when the customer's identity isn't verified on the channel

  • More than one customer participant: Fin uses personalized attributes only when the conversation has exactly one customer participant

  • Messy data: Fin can't confidently connect the attribute's values to your content and other settings

  • Conflicting configuration: Fin prioritizes an escalation rule or procedure over the data

  • Complex use case: Fin needs a procedure to solve the use case reliably

If Fin still doesn't use an attribute as expected, add more direct instructions in How Fin should use this attribute in the attribute settings sheet.

Will Fin use outdated customer data?

Fin uses the attribute values available for the customer when the conversation starts, so Fin can use outdated data if the values in your synced helpdesk or CRM are outdated. To stop Fin from using an attribute you don't trust, set its Fin status to Disabled on the Data page. The Details section shows each attribute's coverage to help you decide.

How do I write one article that covers different types of customers?

When one article mixes details for different types of customers, add a plain-language callout to that section that names the customer type. For example, use this when a feature is available only on a certain plan. Name the customer type exactly as it appears in the synced data, so Fin can match it to the customer's attributes.

For example, if the synced Plan attribute has the value "Enterprise", write: "Note: This section applies to customers on the Enterprise plan."

This approach avoids restricting the whole article with an audience rule and avoids splitting the article into several versions. Use an audience rule only when an entire article should be exclusive to one segment of customers.


💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts


Did this answer your question?