Skip to content
NagentNagent
Log inSign upHire your AI team
Atlas/Fin (Salesforce)
Vendor dossier / Customer experience

Fin (Salesforce)

Customer service AI agent acquired by Salesforce in September 2026; offered for connected helpdesks alongside Agentforce.

REVIEWED 23 SEPTEMBER 2026Sales / CXNO HANDS-ON BENCHMARK

What it is

Official-source notesCustomer experienceestablished

Fin supports connected helpdesks, actions and human transfer. Its billable outcomes include resolutions and configured procedure handoffs; a qualification has a different rate. [V1] [V2]

Documented means the statement is present in the cited material. Capability effectiveness, customer outcomes and security assurances have not been independently audited here.

Promoted use cases

  • Resolve customer questions and execute procedures
  • Escalate with context to a human team
  • Qualify prospects and route conversations

CX agents operate where answer quality and action correctness directly affect customers. A response that sounds useful can still be wrong, and a conversation marked resolved can reopen. The comparison should combine customer experience, transactional accuracy, human handoff, operational visibility and the exact commercial definition of an outcome.

Pricing and buying model

Published commercial evidence

$0.99 / outcome

External-helpdesk offer: 50 outcomes/month minimum. Qualifications $9.99; Intercom seats and add-ons separate.

Check current commercial source ↗

Budget for implementation, model and tool usage, data, human review and ongoing support. Credit units and outcome definitions differ between vendors. A missing numeric rate is marked unverified rather than replaced with an old third-party estimate.

Collaboration and governance

The pricing FAQ describes configurable limits and reporting. Evaluate actual outcome definitions, not the shorthand term resolution.

The relevant unit of control is permission to change an order, account or service record. Inspect who can propose, approve, execute, interrupt and audit that action. Shared seats, shared content and a shared live agent session are different capabilities; require a demonstration of the one your process needs.

Evaluate memory correction, permission revocation and release control for updated instructions. An improvement loop should preserve the original evidence, proposed change, test results and named approver. A safety or security badge alone cannot establish those workflow properties.

Review and customer evidence

Visible July 2026 G2 reviews praise quick rollout and reduced routine-support workload. Marianna A.’s review also flags routing challenges in its headline. The displayed sample is seller-invited and incentivized, and predates Salesforce’s September 2026 acquisition. Do not attribute its entire review base to the current Fin agent. Test escalations and billing against your own support cases.

Before relying on a testimonial, confirm the exact product, version, package, workload and baseline. Ask a relevant customer about setup effort, failed cases, ongoing manual work and support after launch. This dossier does not convert customer logos or vendor-hosted awards into independent proof.

Focused feature documentation

Focused documentation check · Sep 2026

Outcome definition and qualification are separate meters

Fin’s help center lists $0.99 per service outcome. Its pricing update says the metric evolved from “resolution” to “outcome,” with other forms of accepted work, while its startup page distinguishes sales qualifications at $9.99 each. The buyer should confirm current billable event definitions for its plan, including procedure handoffs and disqualifications. An outcome label is commercial taxonomy, not evidence of customer satisfaction.

For a CX and growth pilot, mix questions, return tasks and lead qualification. Track human handoff, reopened cases and whether a promised action really changed the downstream system. If legacy Intercom helpdesk seats or a Pro add-on are needed, include them in total cost instead of comparing the outcome price with an entire competing service stack.

Salesforce announced on 10 September 2026 that it had completed its acquisition of Fin, formerly Intercom. Fin continues to serve its own customers and works alongside Agentforce in the Salesforce portfolio; the announcement does not establish an automatic product merger or unified price. This atlas retains the original Fin comparison URL for continuity while labeling current ownership explicitly.

Primary sources: Official Salesforce acquisition close ↗ · Official pricing page ↗ · Official outcome pricing change ↗ · Official pricing FAQ ↗

Published documentation and public illustrations; account behaviour was not independently tested.

Visual source

A screenshot was not captured for this entry. Open the official visual source ↗. The absence of an image does not affect the evidence status of the sourced notes.

Fit, limitations and proof requests

Editorial assessment

Fin makes a useful commercial benchmark because billing units are explicit. Still, a handoff can be billable, so cost per independently accepted resolution needs its own measurement.

Priority question: How do we audit and dispute outcomes, especially procedure handoffs and conversations later reopened?

The evaluation owner should be the customer-experience and support-operations leads. Use durable, accurate resolutions with appropriate human escalation as the business target. Judge the solution in its own stack role: a cloud runtime, a specialist production tool and a managed AI team can be complementary purchases.

Use-case evaluation plan

Knowledge answer with a verifiable source

Provide a current policy, an obsolete policy and an ambiguous customer question. Require the agent to use the right version, identify uncertainty and avoid inventing exceptions. Ask a human reviewer to verify the answer without reading a long hidden history.

Measure: answer accuracy, source freshness and appropriate escalation.

A bounded customer action

Use a test customer, a low-risk transaction and an explicit action limit. Try a request outside that limit and a case with conflicting identity information. Verify the backend state after execution; a conversational confirmation alone is not evidence that the transaction succeeded.

Measure: correct state changes, blocked unauthorized actions and recoverability.

Learning from a failed resolution

Introduce a repeat contact after an apparently successful interaction. Ask the system to identify the failure, propose a policy or knowledge correction and show the evidence. Require a human owner to approve the change before it affects other customers, then replay similar cases.

Measure: reopen rate, correction quality, regression results and human workload.

Detailed comparison

Read the detailed Nagent vs Fin (Salesforce) guide for operating models, shared context, governance, cost, evidence gaps and a staged pilot.

Nagent vs Fin (Salesforce)

Sources and evidence register

Nagent · Multiplayer AI for growth teamsResearch: 21–29 September 2026 · Public-source analysis, no hands-on benchmark · Sources & method