Move your team from Intercom Fin to Forethought.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Forethought — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Intercom Fin is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Forethought AI Copilot provides a real-time sidebar for human agents — summarizing tickets, drafting replies, and surfacing KB articles while the agent works. Fin Procedures configure Fin's own AI behavior step-by-step, but Intercom also offers a separate Copilot feature (AI Copilot for human inbox) that is the direct equivalent. When moving from Forethought Copilot to Intercom: connect Intercom to the same helpdesk the agents use; Intercom's Inbox AI Copilot surfaces in the agent's Intercom inbox view. Export your Forethought Copilot's frequently-used response templates and suggested replies, then seed the same content into Intercom's Macros and Knowledge Base so the AI Copilot can reference them. Moving in reverse: install Forethought's sidebar in your existing helpdesk (Zendesk, Salesforce, Freshworks) via their native integration — Copilot appears automatically on ticket open. Migrate your Intercom macro/response library into the Forethought-connected knowledge base (Confluence, Notion, or the native KB) to power suggestions.
- Warning: Forethought AI Copilot surfaces inside the agent's existing helpdesk (Zendesk, Salesforce, Freshworks sidebar) — no helpdesk migration required. Intercom's AI Copilot for human agents requires agents to work within the Intercom inbox itself, which may demand a helpdesk workflow change.
- Warning: Knowledge gap flagging (Discover/Insights) is a separate Forethought module; Intercom's equivalent insight features are gated to the Pro analytics add-on ($99/month for 1,000 conversations).
- Warning: Forethought Copilot's deeper AI-surfaced insights (knowledge gap flags, next-best-action) are gated to Professional and Enterprise tiers.
Both products deploy an AI agent that autonomously resolves customer conversations across chat, email, and voice without human involvement. To move from Forethought Solve to Fin: export your Autoflows (download JSON from the Forethought dashboard) to document the intent-action logic, then recreate the same coverage as Fin Procedures in the Fin admin interface — each Autoflow maps to a Procedure with step-by-step guidance and @handoff commands. Point Fin at the same knowledge base sources you had connected in Forethought (Confluence, Notion, Zendesk Help Center, etc.) and connect your helpdesk via Fin's pre-built connector. To move the reverse direction (Fin → Forethought Solve): export Procedures as documentation, then build equivalent Autoflows in the Forethought no-code builder. Migrate knowledge connectors by adding the same sources in the Forethought dashboard under Integrations. Run parallel on both bots for 1–2 weeks against a subset of traffic to validate resolution rates before cutting over fully.
- Warning: Fin bills $0.99 per resolved conversation (outcome-based); Forethought Solve is seat/plan-based. A high-volume team that resolves 10,000 conversations/month pays ~$9,900 in Fin resolution fees — model your volume against Forethought's flat plan costs before switching.
- Warning: Forethought Solve covers voice on Professional and Enterprise plans; Fin voice requires a separate sales engagement with specialized pricing not listed publicly.
- Warning: Forethought's Autoflows support multilingual handling on all tiers; Fin's multilingual coverage specifics are not disclosed in public docs — verify during trial.
Forethought integrates with 70+ platforms (Zendesk, Salesforce, ServiceNow, HubSpot, Freshworks, Intercom, Confluence, Notion, Shopify, and more); Fin offers pre-built connectors for Salesforce Service Cloud, Freshdesk/Freshchat, and HubSpot Service Hub, plus MCP/API data connectors for Shopify, Stripe, Linear, and custom systems. Moving from Forethought to Fin: audit your active Forethought integrations in the dashboard and identify which connectors Fin covers natively. For covered helpdesks (Salesforce, Freshdesk, HubSpot), set up Fin's pre-built connector (2–5 minutes each); for knowledge sources currently feeding Forethought (Confluence, Notion, Guru), migrate content to the Fin-connected KB or use the Fin API connector. For connectors Fin lacks natively (ServiceNow, Kustomer, Genesys, RingCentral), plan for custom API integration (30 min to several hours per connector) or evaluate whether those workflows can be replaced by Fin Procedures. Moving from Fin to Forethought: Forethought supports all three of Fin's pre-built helpdesk targets plus significantly more, so connector coverage expands; configure in the Forethought Integrations dashboard.
- Warning: Fin's pre-built helpdesk connectors are limited to Salesforce Service Cloud, Freshdesk/Freshchat, and HubSpot Service Hub. Teams on Zendesk, ServiceNow, Kustomer, or Jira will need custom API integrations, whereas Forethought supports all of these natively with no-code connectors.
- Warning: Forethought's call center integrations (Genesys, Amazon Connect, RingCentral, Five9, 8x8, Cisco) have no announced equivalent in Fin's connector library — voice channel in Fin requires separate sales engagement.
- Warning: Fin data connectors use OAuth 2.0 with granular access controls; Forethought's connector auth model is not detailed in public docs — verify security requirements during proof-of-concept.
Forethought Discover Agent scans ticket history to surface knowledge gaps, recurring unanswered questions, and automation opportunities, then proposes draft KB articles. Fin Analytics surfaces resolution rates, outcome distributions (Resolution/Handoff/Disqualification/Qualification), and per-conversation cost data. Moving from Forethought Discover to Fin Analytics: before cutover, export Discover's Insights Dashboard findings (knowledge gaps, proposed KB articles) and action any outstanding KB article drafts — Fin will not retroactively identify gaps from old ticket history. After launching Fin, use Fin's built-in reports to track resolution rates and outcome mix; for deeper gap analysis (up to 1,000 conversations/month), add the Intercom Pro analytics add-on. Moving from Fin Analytics to Forethought Discover: Forethought Discover processes your existing ticket history from the connected helpdesk — no separate data export needed. Enterprise users get automated Autoflow gap generation and knowledge article creation directly from detected gaps.
- Warning: Fin's deep conversation analysis (Pro add-on) is capped at 1,000 conversations/month for $99/month; Forethought Discover's coverage scales with your ticket volume without a published conversation cap.
- Warning: Forethought Discover's automated KB article and Autoflow gap generation is an Enterprise-only feature; Professional tier surfaces insights but requires manual follow-through.
- Warning: Fin Analytics does not retroactively audit historical ticket quality against rubrics the way Forethought QA Agent does — these are different analytics surfaces covering different workflows.
Forethought Triage Agent classifies and routes inbound tickets before a human touches them; Fin's escalation-and-handoff system routes conversations to specific teams or agents when the AI cannot or should not resolve. Moving from Forethought Triage to Fin: document your current routing rules (which intents go to which team/queue) from the Forethought dashboard, then recreate the same logic as Fin escalation rules and @handoff commands inside each Fin Procedure. Fin's frustration-detection triggers cover emotion-based escalation automatically; explicit topic-based routing must be encoded per Procedure. Moving from Fin to Forethought Triage: export your Procedure escalation configs as reference, then configure Forethought Triage in the dashboard using out-of-the-box models (Team plan) or train custom handoff models on your ticket history (Professional/Enterprise). Connect Forethought to the same helpdesk (Zendesk, Salesforce, ServiceNow) so it can apply tags and assignments upstream before tickets enter the queue.
- Warning: Forethought Triage runs pre-queue — it classifies tickets before any agent sees them, including tickets that will be human-handled from the start. Fin escalation is post-attempt — it only triggers after Fin has tried and decided it cannot resolve. These are different insertion points; you may need both layers if you have complex routing for human-only ticket types.
- Warning: Custom handoff models trained on your own data require Forethought Professional or Enterprise; the Team plan uses generic out-of-the-box models that may misclassify domain-specific intents.
- Warning: Fin Procedure Handoff (an escalation to a team via a configured procedure) is a billable outcome at $0.99; default frustration or human-request escalations are not billed.