Compare

Finvs Callvu

Fin, formerly Intercom and now part of Salesforce, is an AI customer service agent that answers questions and runs Procedures to take actions such as refunds and exchanges across chat, email and voice. Callvu is the Completion and Compliance Layer: when a support conversation becomes a regulated request, Callvu runs it end to end through the back office to the system of record with a deterministic orchestrator, enforcing every regulation on every step. Fin can be one of the doors where a Callvu process starts.

At a glance

Runtime compliance enforcement

FinPartial.
CallvuYes.

Front-to-back-office handoff

FinPartial.
CallvuYes, end to end: prefill from the core, classify the work, chase and verify documents, route decisions to the Decision Desk and write back to the system of record.

The fair version

What Fin is built for.Sourced from their own pages.

Intercom renamed itself Fin in May 2026 [1], and Salesforce completed its acquisition of Fin in September 2026 [2]. The Fin AI Agent answers and resolves customer requests across chat, email, voice and messaging [3]. Procedures are multi-step workflows written in natural language, with optional deterministic branching, code conditions and code steps [4], that call external systems through data connectors to get or update records [5], process refunds and create exchanges [6], and can pause for a teammate's approval [7]. Fin positions these deterministic controls for compliance-sensitive processes such as dispute resolution, KYC guidance and refunds, and logs every conversation, AI decision, handoff and trigger [13]. Fin says its Guidance does not strictly control behavior and is applied turn by turn [8]. It connects to other systems through REST API connectors, webhooks and MCP, and names no core banking or loan systems among its integrations [14]. Fin Voice runs on the phone [9], Fin works with Salesforce Service Cloud and other help desks [10], and Intercom achieved AIUC-1 certification [12]. Its financial services customers are mostly fintechs [11].

When to choose which

Two different jobs.Pick the one you need.

When to choose Fin

Choose Fin when the need is answering support questions and resolving routine requests from your help content and connected systems [3][5], across chat, email and voice [9], with low compliance risk in the conversation itself, on your existing help desk [10].

When to choose Callvu

Choose Callvu when support conversations lead to regulated requests that must be completed in the core, loan origination, policy admin or billing system. Callvu orchestrates the work, routes it by work type, skill and due date, applies rules and policies and manages every decision, and it runs the handoff in the same process with five moves: it prefills from what the core already knows, classifies each request the moment it lands, chases and verifies documents from customers and outside parties on a clock, routes decisions to the Decision Desk, and writes the result back by API.

Guardrails are not runtime enforcement. Fin processes refunds and exchanges through Procedures [6] and updates records through data connectors [5], with code steps for some actions [4], while its Guidance is applied turn by turn and does not strictly control behavior [8]. Guardrails limit and record what an AI does while it does the work. Even with guardrails, an AI that runs the process can write wrong data to the system of record, take a path that is not in the workflow, or act compliantly most of the time rather than every time. Callvu does not let AI run the process. A deterministic orchestrator decides every next step and enforces every control before the step runs; AI, yours or Callvu's, only starts a process or evaluates it. Every run is recorded in a Decision Trace and an Audit Trace.

Side by side

The verifiable facts.Nothing else.

Every cell about Fin is sourced from its own public pages. Runtime enforcement and the handoff lead the table because they are where the two differ most.

CapabilityCallvuFin
Primary roleCompletion and Compliance Layer between every front door and the system of recordAI customer service agent and help desk [3]
Runtime compliance enforcementYes. A deterministic orchestrator runs every step and decides the path; AI never runs the process. Every regulation and company policy is enforced on every step while the work runs, whether a person or an AI started it; a step that fails a control does not run. A Decision Trace and an Audit Trace for every runPartial. Procedures can include deterministic branching, code conditions and code steps, which Fin positions for compliance-sensitive processes such as dispute resolution, KYC guidance and refunds, and every conversation, AI decision and handoff is logged; natural-language steps stay flexible, and Fin says its Guidance does not strictly control behavior and is applied turn by turn [13]
Front-to-back-office handoffYes, end to end: prefill from the core, classify the work, chase and verify documents, route decisions to the Decision Desk and write back to the system of record. Back-office planning starts the moment the front end startsPartial. Procedures call external systems through data connectors, REST APIs, webhooks or MCP and can pause for a teammate's approval. No core banking or loan system integration is named, and document chase and verification are not documented [5]
AI guardrails vs deterministic executionDeterministic execution, not guardrails: AI never runs the process. A deterministic orchestrator executes every step and enforces every control before it runs, so nothing unchecked reaches the system of record and no step outside the workflow can happenFin processes refunds and exchanges through Procedures and can get or update records through data connectors [6]
Human decisionsEvery human decision in the Decision Desk, inside or outside the company, with the case's full activity log, only the allowed choices and the decision recorded in the Audit TraceProcedures can ask a teammate to approve an action before it runs [7]
Sensitive dataSensitive input never goes into an AI chat; consent, signature and sensitive data stay on a process-controlled screen handed over prefilledSecure capture of sensitive data is not described in Fin Voice documentation [9]
Help desk and CRMIntegrates with CRMs, cores, loan systems, insurance cores, telco BSS, Genesys and NICE CXone; more added per customerWorks with Intercom, Zendesk, Salesforce, HubSpot and Freshdesk; other systems connect through REST API connectors, webhooks or MCP [14]

Using both together

Keep what works.Add the layer that finishes it.

Fin can stay the support agent. When a conversation becomes a regulated request, Fin starts a Callvu process in the backend over MCP, or hands the customer a prefilled, process-controlled screen for consent, signature or sensitive data. Callvu runs the back-office work and the write back to the system of record. Callvu can also run the whole process on its own, from any door.

Proof

Live in production.At regulated enterprises.

FAQ

The questions buyers ask.Answered plainly.

Does Fin enforce compliance at runtime?
Fin Procedures can include deterministic branching, code conditions and code steps, which Fin positions for compliance-sensitive processes such as disputes, KYC guidance and refunds, log every conversation and AI decision, and can pause for a teammate's approval. Fin says its Guidance does not strictly control behavior and is applied turn by turn, and the AI agent conducts the conversation and moves through the procedure. In Callvu, a deterministic orchestrator decides the path and runs every step, AI never runs the process, and every regulation and company policy is enforced on every step before it executes.
Now that Salesforce owns Fin, does Callvu still work with it?
Yes. Callvu works with any AI agent and integrates with Salesforce. Fin can start a Callvu process in the backend over MCP or hand the customer a prefilled, process-controlled screen for consent, signature or sensitive data, and Callvu takes the regulated request through to the system of record.
Are code steps in AI agent procedures the same as deterministic execution?
Not quite. Code steps make individual actions reliable, but when an AI agent moves through the procedure, it can still skip a step, take a path that is not in the workflow, or write data the process did not intend. Callvu keeps the whole path deterministic: the orchestrator decides every next step and enforces every control before it runs.
What are alternatives to Fin for a bank or credit union?
Fin's named financial services customers are mostly fintechs. Banks and credit unions whose support requests must be completed in the core or the loan system use Callvu behind their AI agent, or Callvu AI chat, to run those requests deterministically end to end with a Decision Trace and an Audit Trace for every run.
How fast can Callvu go live behind an AI support agent?
Callvu builds the process for you and launches in a few weeks, with white-glove implementation included in the license. A proof of value runs on one of your own processes first.

See it on your process.

Bring one regulated process. We will show you the handoff and runtime enforcement on it.