Clarifier · Fin product split · Post-rebrand (May 12, 2026)
Fin Customer Service vs Fin Sales Agent: Two Roles, One Platform
Fin runs two distinct roles on one cross-workflow agent platform: Fin Customer Service (also called Fin Customer Agent — handles inbound support resolution) and Fin Sales Agent (Fin for Sales — handles inbound sales qualification + meeting booking on your marketing site). Same agent intelligence, shared knowledge base, shared customer context — different workflow + outcome + deployment surface. This page is the clarifier that the marketing pages don't do well: where each role lives, what each costs, how the shared-knowledge architecture beats single-workflow AI vendors, and when to deploy one or both.
Side-by-side: what splits, what stays the same
Eight dimensions. The dimensions that differ are workflow shape; the dimensions that stay constant are agent intelligence + pricing + the shared-knowledge architecture.
| Dimension | Fin Customer Service | Fin Sales Agent |
|---|---|---|
| Workflow | Inbound customer support conversations — product questions, troubleshooting, refunds, order updates, account changes | Inbound sales conversations on your marketing site — qualification, pricing questions, demo booking, sales handoff with context |
| Who initiates the conversation | Existing customer (logged in or identified) with a service need | Prospect (anonymous or known visitor) with a sales intent signal |
| Primary outcome | Resolution — issue closed end-to-end without human handoff (40-60% rate at typical deployments) | Meeting booked OR qualified handoff with context — Fin for Sales reports close rates near 50% for qualified inbound conversations |
| Knowledge sources | Help center, internal documentation, past resolved tickets, product API (account data, order status, subscription state), playbook rules | Same shared knowledge base (this is the architectural distinction) + sales playbook rules, qualification scorecards, pricing logic, meeting routing rules |
| Where it lives | Help center, in-app messenger, post-login support surface, escalation flows into Intercom 2 / Zendesk / SFDC inbox | Marketing site (homepage, pricing page, product pages), pre-login chat, lead capture surfaces, handoff to Chili Piper / Calendly / SFDC |
| Pricing | Per resolution (~$0.99 per conversation closed end-to-end) | Per resolution (same pricing model) — Fin for Sales conversations that close without human handoff are billed the same way |
| Handoff destination | Human support agents in your helpdesk inbox | Sales reps with full conversation context, qualification data, meeting pre-booked when possible |
| GA timing | GA for 3+ years (launched as Intercom Fin in 2023) | GA April 2026 — newer addition; Fin for Sales is the sales-workflow role on the same agent platform |
Why it's one platform, not two products
The architectural choice that makes Fin distinct from single-workflow AI vendors: both roles share knowledge, customer context, and playbook layers. Four structural shares:
- Shared knowledge base: Both roles read from the same knowledge sources — help center, internal docs, past tickets, product API. A prospect asking 'what does pricing look like for 50 users with SOC 2 compliance' and a customer asking 'why was my account downgraded to the 50-user tier' both hit the same KB layer. The agent doesn't context-switch between knowledge silos.
- Shared customer context: Once a prospect becomes a customer, Fin retains the conversation history across roles. The customer-service agent knows the prospect asked about SOC 2 compliance during the sales motion; the sales agent knows the customer escalated a support ticket last quarter. Context is shared inside one agent identity, not split across vendor tools.
- Shared playbook layer: Playbook rules (qualification scorecards, refund eligibility, escalation triggers, account-tier behaviors) live in one place. The customer-service role sees the sales playbook rules; the sales role sees the support escalation rules. Cross-workflow consistency.
- One vendor relationship, two billing line items: Both roles bill per resolution from the same Fin contract. The line items are separate (Customer Agent resolutions vs Sales Agent resolutions are tracked distinctly), but you sign one vendor agreement, manage one set of admin controls, and the resolutions roll up to one Fin invoice. You don't run two separate AI agent procurements.
The competitive implication: single-workflow AI vendors (Ada is support-only; Drift / Qualified are sales-chat-only) can't deliver this shared-context shape. A team running Drift on the marketing site + Ada on support has knowledge drift between vendors, fragmented customer context, two vendor relationships. Fin's cross-workflow agent is the architectural moat.
Who needs which role
Your motion shape determines the deployment. Five common profiles:
| Profile | Recommended deployment | Why |
|---|---|---|
| High-volume B2C / ecommerce support team | Fin Customer Agent — primary | Order tracking, returns, shipping updates, account issues. Support conversation volume swamps human capacity. Fin Customer Agent handles the resolvable fraction; sales role secondary or skip if you don't run a sales motion. |
| B2B SaaS with inbound demo flow + support load | Both roles, deployed jointly | Marketing site needs Fin for Sales (qualifying prospects, booking demos, handling pricing questions on /pricing). Logged-in app + help center needs Fin Customer Agent (resolving support tickets). Same agent platform, deployed in both surfaces — the cross-workflow agent thesis in practice. |
| Outbound-heavy B2B sales (PLG-light, sales-led) | Fin for Sales — primary | Heavy inbound qualification load through marketing site. Fin for Sales handles qualifying prospects, answering product questions, booking SDR / AE meetings with context. Customer Agent secondary if support volume is light. |
| Enterprise CX org with mature ITSM / customer-success motion | Fin Customer Agent — primary; Customer Success extension | Support workflow is the primary spend. Fin extends into customer-success workflow (onboarding nudges, feature discovery, renewal-window conversations) on the same knowledge layer. Sales role only if you run inbound sales motions. |
| Solo founder / very small team with inbound chat | Fin for Sales — try first | Marketing-site inbound chat is the highest-leverage surface for a small team. Fin for Sales qualifies prospects + books meetings without you watching chat all day. Customer Agent secondary as support load grows. |
The pricing math for both roles
Both roles bill per resolution at the same rate (~$0.99/resolution at typical volumes, negotiable at scale). Sample numbers for a B2B SaaS deploying both:
- Sales Agent on marketing site: 2,000 inbound chats/mo × 60% resolution = 1,200 resolutions × $0.99 = ~$1,188/mo.
- Customer Service in help center + in-app: 8,000 support conversations/mo × 50% resolution = 4,000 resolutions × $0.99 = ~$3,960/mo.
- Combined Fin bill: ~$5,148/mo or ~$62K/yr.
- If bundled on Intercom 2: + helpdesk seats at $99/agent × 10 agents = $990/mo additional. Total ~$6,138/mo.
- Compare against: Loaded cost of human-only handling for these volumes ($50-150K/mo at typical CS / sales-ops math). Even the more conservative comparison clears the human-cost line meaningfully.
The per-resolution model means buying both roles doesn't add fixed cost — you only pay for outcomes Fin actually delivers. Procurement-friendly: same vendor contract, two line items, predictable scaling with resolution volume.
What the rebrand changed (and didn't)
On May 12, 2026, the company formerly known as Intercom rebranded to Fin. The strategic signal is meaningful; the operational impact on the two roles is zero. Full rebrand context at /intercom-becomes-fin. What stays unchanged: both roles continue as separate product lines on the same cross-workflow agent platform, same per-resolution pricing, same deployment shapes, same integration partners. What changes: the corporate brand on procurement paperwork (Fin, not Intercom), the marketing positioning (the company brand now matches the agent product), and the IPO signaling (renaming the company after the agent product reads as pre-IPO positioning).
Sources
- Fin (the company / product homepage)
- Intercom: Announcing Fin for Sales (April 24, 2026 — sales-role GA announcement)
- Eoghan McCabe: Today Intercom Becomes Fin (May 12, 2026 — rebrand)
FAQ
No — they are two distinct roles on the same agent platform. Fin Customer Service (also called Fin Customer Agent) handles inbound customer support conversations — product questions, troubleshooting, refunds, order updates, account changes. Fin Sales Agent (Fin for Sales) handles inbound sales conversations on your marketing site — qualification, pricing questions, demo booking, sales handoff. Same underlying agent infrastructure, different workflow + outcome + deployment surface. Both bill per resolution; you can deploy one or both depending on your motion.
Three structural differences. (1) Where it lives — Customer Service runs inside your in-app messenger and help center; Sales Agent runs on your marketing site, pricing page, product pages. (2) Who initiates — Customer Service is for existing customers (logged in or identified); Sales Agent is for prospects (anonymous or known visitors). (3) Primary outcome — Customer Service measures end-to-end resolution rate; Sales Agent measures qualified meetings booked + qualified handoffs. Same agent intelligence, different workflow shape.
You can deploy either role standalone or both jointly. Most B2C / ecommerce teams start with Customer Service for the support volume. B2B SaaS teams often deploy both — Sales Agent on the marketing site, Customer Service in-app. Solo founders / very small teams sometimes start with Sales Agent first (marketing-site inbound is the highest-leverage surface for a lean team). Pricing is per resolution for either role, so you only pay for outcomes Fin actually delivers — buying both doesn't add fixed cost.
Architectural decision: shared knowledge layer + shared customer context across workflows. A prospect asking a product question during a sales conversation needs the same answer a customer would get for the same question in support. Splitting that across two vendors (a sales chatbot + a customer service AI) creates knowledge drift — answers diverge over time, customer experience fragments. Fin's cross-workflow agent thesis is that one agent identity should span the full customer lifecycle. The competitive moat against single-workflow AI vendors (Ada is support-only; Drift / Qualified are sales-chat-only) is the cross-workflow agent shape.
Drift and Qualified are inbound conversational marketing platforms — built for B2B sales-led motion with strong ABM / Salesforce integration. Fin Sales Agent is the sales-workflow role of the cross-workflow Fin agent platform. Differences: (1) Fin Sales Agent shares knowledge + customer context with Fin Customer Agent — Drift / Qualified are standalone sales tools. (2) Drift / Qualified have deeper ABM playbook tooling (account-based campaigns, intent data integration, advanced routing); Fin Sales Agent is simpler + more autonomous-resolution-focused. (3) Pricing — Drift / Qualified are per seat / per user; Fin is per resolution. For high-AI-ambition cross-workflow teams, Fin wins. For deep ABM-heavy sales-only motions on Salesforce, Drift / Qualified are still credible. Full breakdown at /fin-vs-drift.
All four are AI customer agent platforms — but with different scopes. Fin Customer Service is the support-workflow role of the cross-workflow Fin platform (also runs sales, ecom, success). Ada is the enterprise CX AI incumbent, support-focused with deepest enterprise track record. Decagon is the action-taking-agent specialist, support-focused. Sierra is Bret Taylor's company, support-focused with brand-voice consistency emphasis. For cross-workflow deployments → Fin. For support-only at enterprise scale → Ada credible. For action-heavy support workflows → Decagon. Full breakdown at /best-ai-customer-agents-2026.
No — the rebrand was corporate, not product. Both Fin Customer Service and Fin Sales Agent continue with the same product surface, same pricing model, same deployment shape. What changed: the parent company is now called Fin (rebranded from Intercom on May 12, 2026), and the corporate brand now matches the agent product. Procurement paperwork will update at next renewal; the products themselves are unchanged. Read /intercom-becomes-fin for the full rebrand context.
Sample math for a B2B SaaS with both roles deployed: (1) Marketing site has 2,000 inbound chat conversations/mo, Fin for Sales resolves 60% (1,200 resolutions) — sales role bill at ~$0.99 × 1,200 = $1,188/mo. (2) Help center + in-app messenger has 8,000 support conversations/mo, Fin Customer Service resolves 50% (4,000 resolutions) — service role bill at ~$0.99 × 4,000 = $3,960/mo. Combined Fin bill: ~$5,148/mo or ~$62K/yr. Layer Intercom 2 helpdesk seats on top (if you bundle): $99/seat × 10 agents = $990/mo. Compare against loaded cost of human-only handling for these volumes ($50-150K/mo at typical CS team math). Get quotes for your specific volumes — published rates are negotiable at scale.
Yes — both roles deploy independently. Fin Customer Service can run on Zendesk (or Intercom 2, Salesforce Service Cloud, Help Scout, Front via API) handling support conversations. Fin Sales Agent runs on your marketing site as a standalone deployment (no helpdesk required for the sales role — the marketing site is the surface). Shared knowledge layer + shared customer context still apply across the two deployments — the agents talk to each other inside the Fin platform. Common pattern for Zendesk-anchored teams: Fin Customer Service on Zendesk + Fin Sales Agent on marketing site, no Intercom 2 needed.
Run StackScan. The overlap engine catches the most common redundancy patterns: (1) Fin Sales Agent + Drift / Qualified on the marketing site — pick one. (2) Fin Customer Service + legacy chatbot (HubSpot Chat, native helpdesk bots) — retire the chatbot. (3) Fin Sales Agent + outbound SDR tools doing inbound triage — Fin handles inbound, free up the outbound tools for actual outbound. Modeled annual recoverable spend per overlap candidate. $25 per actionable decision, $249 cap.
Related reading
- What is Fin? — the full vendor explainer
- Intercom becomes Fin — the rebrand context
- Fin for Sales review — the operator perspective on the sales role
- Fin vs Drift — sales-role head-to-head
- Fin vs Ada — customer-service-role head-to-head
- Fin vs Decagon — customer-service-role head-to-head
- Fin vs Zendesk AI — vs incumbent helpdesk AI
- Fin vs Salesforce Agentforce — vs SFDC-native agent
- Best AI customer agents 2026 — full category hub
- The StackSwap Operator Playbook — 10 Claude skills covering the full GTM motion. Free ICP Builder + $99 bundle.
Canonical URL: https://stackswap.ai/fin-customer-service-vs-fin-sales-agent. Disclosure: StackSwap has no commercial relationship with Fin (formerly Intercom). Sourced from publicly available announcements, vendor documentation, and third-party coverage.