Conversation imports lets you sync your ticket/case history directly into your Fin workspace. This can be used to provide Fin Insights, generate content which increases Fin's resolution rate, and give Fin Copilot access to previous conversations.
Key benefits
Fin uses conversation history to deliver deeper insights about your customer queries.
Fin can generate suggestions for improving its content by examining your conversation history.
Conversation history can be used by Copilot to help your agents find answers they have given in the past.
Set up the synchronization of ticket/case history
Go to Train > Content.
Select Zendesk ticket history / Case history from Salesforce.
Enable the toggle to sync history.
Choose to Sync all or Sync a selection and then filter conversation history based on attributes.
You can also let Fin Copilot look for answers using your conversation history when you enable Copilot can use conversation history. When helping your agents answer questions, Copilot will look through your teams’ conversation history to find previous answers. This can be limited to specific teammate conversations (e.g. your more tenured support agents).
Wait for the initial sync to complete (up to 10,000 conversations will be imported first, it can take up to 5 hours to complete).
Managing conversation imports
Once connected, the system will automatically sync your conversations once daily. Here's what gets imported:
Closed conversations that involved a teammate.
Maximum of 10,000 conversations per sync.
Conversations with teammate and Fin involvement will be updated with any missing conversation details.
Note:
You can toggle off the sync at any point. This stops future imports but won't delete conversations already brought into your Fin workspace.
Synchronization of ticket history does not include Zendesk side conversations.
How Salesforce case history sync works
Case history sync needs a production Salesforce connection. If only a sandbox is connected, the toggle stays greyed out until you add your production org.
With Sync all selected:
The first sync imports up to 10,000 closed cases that were last updated in the past 30 days.
Each daily sync after that imports cases closed or updated since the previous sync.
The sync doesn't work back through older history over time. Cases last updated before the first 30-day window aren't imported.
Only closed cases linked to a Contact are imported. Cases with no emails, comments or posts are skipped. Each sync imports the 10,000 most recently updated cases that match.
Sync cases from further back
To import cases from before the 30-day window, choose Sync a selection and add a Created Date filter, for example Created Date less than 180 days ago. A Created Date filter replaces the 30-day window. A Closed Date filter doesn't, so it still only imports the last 30 days.
Keep these limits in mind:
The 10,000 limit applies to each sync, not to the whole date range. If your range holds more than 10,000 cases, only the 10,000 most recently updated are imported.
With a date filter, each daily sync reads the whole range again. Cases already imported are updated, not duplicated.
Saving a filter starts a new sync straight away and cancels any sync that's already running. A sync of up to 10,000 cases can take up to 5 hours, so wait for it to finish before you change the filter again.
Salesforce API usage
Case history sync uses your Salesforce API allowance, but not one call per case. Each sync runs a query that returns cases with their emails, comments and posts in pages. A sync of 10,000 cases typically uses about 700 to 1,000 API calls, depending on how many emails and comments each case has. Daily syncs after the first usually use far fewer.
FAQs
Will Fin conversations be counted twice?
No, the importer is smart enough to skip conversations that Fin was already involved in, so you won't see duplicates.
Can I respond to synced tickets/cases?
Synced tickets/cases are read-only. You can drill down and review them for analysis, but you can't respond directly from your Fin workspace.
Can I train Fin using historical tickets or cases?
Fin AI Agent is currently designed to use your knowledge base as its source of truth for answering questions. However, it can learn from historical conversations through AI-powered suggestions. These suggestions help improve Fin's performance by identifying unresolved conversations, comparing them to human replies, and highlighting what needs to be fixed.
Additionally, Fin Copilot can use historical conversation data to generate answer suggestions for teammates. Copilot only uses conversations created in the last 4 months, so older imported cases are kept as records but aren't used by Copilot.
What happens to Fin conversations routed to teammates?
When these conversations are closed in your support platform (e.g. Zendesk or Salesforce), they'll sync to Fin on the next daily update with all the missing conversation details included.
Can I control which ticket/case history is synced?
Yes, you can filter by Zendesk or Salesforce attributes to ensure only relevant tickets/cases are imported.
How often do tickets/cases sync?
Tickets or cases will sync once daily automatically. The system looks for closed conversations that involved a teammate, up to a maximum of 10,000 per sync.
What happens if I disable the ticket/case history sync?
Disabling the ticket/case history sync will stop new conversation imports but will not remove previously imported conversations from your Fin workspace. These past conversations remain indexed to maintain reporting accuracy.
Currently, Fin does not support automatic deletion of previously synced data. If this poses a privacy concern, please contact us directly so we can review the retained data and discuss options.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts



