Loading…
Intercom
Customer communications platform providing messaging, support, help center, and AI-powered customer service tools.
- 101 posts summarised
- latest
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
From their blog
Latest articles
Speed-to-lead is a solved problem
The post argues that “speed-to-lead” is no longer the central sales constraint because AI Agents can start conversations with website prospects immediately, at any hour and in any language. It describes how shift scheduling, routing delays, CRM batch processing, and unavailable SDRs created response gaps, with Fin’s former SLA targets set at one hour for best-fit leads and forty-eight hours for others. An Agent can combine immediate engagement with qualification, discovery, and an initial demo moment in one continuous conversation, filtering low-fit leads and handing teams richer context. This shifts SDR work toward phone-based selling, relationship building, complex deal navigation, and multi-threaded stakeholder engagement. The post says teams should measure completion, qualification, contact capture, meetings, pipeline, and conversation satisfaction; Fin reports S2 pipeline volume up 77% year-on-year since enabling Fin for Sales in July.
What really matters when evaluating AI Agents for customer service?
Evaluating an AI Agent for customer service requires more than measuring accuracy, resolution rates, containment, or benchmark performance on curated datasets. A credible proof of concept should reproduce real support conditions, including multi-turn, vague, sensitive, multilingual, rephrased, and multi-source queries, while testing recovery, task tracking, and human handoffs. It should also assess the customer experience: natural, on-brand tone, trust, graceful uncertainty, and seamless transitions can differ even when quantitative scores match. Finally, teams should examine whether conversations can be reviewed for gaps, how quickly knowledge and behavior can be updated, and how the vendor supports ongoing improvement. The resulting POC demonstrates not only that the Agent works now, but that it can support long-term operational success after launch.
How we develop pricing and packaging at Fin
Pricing and packaging at Fin is treated as a cross-functional research, forecasting, and strategic problem rather than a finishing step. When new monetization is needed, the process starts with qualitative buyer research to define a pricing model and metric; for Fin, that produced value-based pricing tied to “outcomes,” each defined as the AI Agent successfully handling a customer service query. Quantitative willingness-to-pay studies using Gabor-Granger and Van Westendorp then indicate demand across price points, but do not establish a perfect price. Modeling combines those signals with discounting, usage, segment variation, attach rates, margins, sales capacity, competitor pricing, and finance forecasts to recommend a price alongside ARR and adoption scenarios before executive sign-off. The approach is iterative and applied selectively, while expanding products and capabilities create an ongoing need to review whether the pricing system remains coherent and aligned with delivered value.
Ready for your busiest day: How we scale
Fin describes how its customer service platform is designed to absorb high-volume events while preserving customer isolation, availability, and operational control. At daily peaks, it handles over 150,000 customer requests per second and more than 70,000 asynchronous requests per second; its source-of-truth data spans 128 Vitess shards, while Elasticsearch supports over 650TB, 1.7 trillion documents, and peaks above 40,000 requests per second. The architecture favors AWS primitives, Vitess managed by PlanetScale, online and incremental migrations, fair queues, feature flags, heartbeat metrics, and automatic rollback, with roughly 250 production ships per workday and merge-to-production time under 10 minutes. The stated conclusion is that scale depends less on headline capacity than on clear scaling levers, tenant fairness, customer-outcome monitoring, reversible change, and routine infrastructure improvement without planned customer-impacting downtime.
Agents can do the work
Agent evaluations often ask what an AI Agent can do, but the larger constraint may be whether an organization is structured to let it act. Across organizations in energy, healthcare, ecommerce, gaming, financial services, and property management, teams found that Agents could often perform actions technically, but stalled on unreliable identification, inaccessible live data, or unreachable vendor systems. The post describes five readiness types—content, scope, procedural, data, and execution—and says deeper automation depends on documented processes, trustworthy connected data, stable APIs, and clear ownership of risk. Teams that lacked these foundations often redesigned toward guiding users rather than executing changes, while teams with standardized operations could trigger tightly controlled actions. The unresolved question is how readiness develops, since the gaps may involve undocumented procedures, fragmented systems, missing APIs, or infrastructure and accountability investments beyond buying a more capable Agent.
Operator: A look under the hood
Operator is a customer-operations Agent built to help teams understand, manage, and improve customer experience across workspaces. The post distinguishes a production Agent from a prototype that simply gives an LLM API access and a system prompt, describing more than 50 purpose-built tools and 10 skills for data retrieval, reporting, investigation, and operational tasks. Its intelligence layer combines semantic search tuned against millions of support conversations, workspace-specific attribute awareness, and encoded reasoning, while the action layer supports configuration and content changes through reviewable diffs requiring explicit approval. A hybrid conversational and graphical interface presents charts, dashboards, and structured proposals within the existing platform. The post argues that read-only custom tools can be built in weeks, but production reliability, safe actions, multi-tenant isolation, graceful degradation, and ongoing maintenance require substantially greater investment.
Meet Operator: An Agent for your customer operations
Operator is an agent for customer operations that works across Fin and the Intercom helpdesk, addressing the ongoing effort required to manage AI and human support work. It can analyze operational data and conversation samples, explain metric changes and root causes, maintain help-center content from briefs, and identify content gaps with localized drafts. Operator can also debug Fin conversations, propose configuration fixes, build Procedures and other automations, run simulation tests, and support incident response and rep management. Its purpose-built tools and proposal system present structured diffs for review, editing, and approval before changes go live; the announcement says more than 200 early users are trying it and that it is available in early access.
The ultimate guide to knowledge management for your Sales Agent
AI-powered inbound sales depends on knowledge management: accurate, current information about products, pricing, plans, qualification, and routing gives a Sales Agent the context to answer questions and guide buyers. The guide describes knowledge management as creating, organizing, sharing, and maintaining business knowledge, while emphasizing content such as product FAQs, pricing overviews, competitor battlecards, case studies, and internal sales materials. It recommends finding gaps through recurring questions, buyer objections, search data, and disengaged conversations; then writing machine-friendly content with simple language, consistent terminology, explanatory context, scannable formatting, and text accompanying images or video. Connecting the Agent to CRM and enrichment systems keeps data and context connected, while ongoing reviews help content evolve from conversation insights and reduce repetitive work for sales teams. It presents knowledge management as a continuous sales function whose cumulative improvements can support faster responses, better qualification, and more focused human selling.
Today Intercom becomes Fin
Intercom is changing its company name to Fin while retaining Intercom for its customer service software platform, including the recently launched Intercom 2 rebuild. The company says all 1,400 employees are now employed by Fin, named after its leading customer agent platform, which it says is about to become the largest part of the business. The change follows three years of promoting the service agent category under Fin, often with Intercom in the background, and reflects a belief that established brands carry baggage when repositioning. The CEO argues that newcomers benefited from having no prior market position to explain, despite Intercom’s claim of superior technology, and presents the renaming as part of a broader transformation spanning culture, pricing, products, and investment priorities.
How we turned support into a revenue engine at Intercom
After Fin improved resolution rates and efficiency at Intercom, support gained capacity and began testing a consultative role focused on customer value and company goals. The team generated campaign ideas through a support town hall, then assigned a small volunteer group to proactively help self-serve customers with Fin trials, optimization, and adoption. Volunteers were trained to probe customer context rather than only resolve immediate issues, while sales and success teams provided guidance on timing and outreach. Over six months, engaged accounts grew roughly twice as fast in usage and expansion as accounts contacted without a response; the team also tracked resolutions, automation, and influenced expansion ARR. The initiative expanded into cross-functional partnerships and a ~16-person volunteer group, positioning support as a contributor to adoption, retention, and expansion revenue.
Building outcome-based pricing for Fin for Sales
Fin for Sales uses outcome-based pricing built around qualified pipeline rather than activity: customers pay $10 per qualified lead, with qualification criteria defined by the customer. The model reflects Fin’s role in engaging prospects, gathering information, evaluating them against those criteria, and routing high-intent buyers to sales representatives. The team rejected revenue-share pricing because attribution would include factors outside Fin’s control, while measuring closed revenue would require deep CRM integrations and slow implementation. Disqualifications and support queries are priced at $1, matching the stated service pricing, while the higher qualified-lead price represents pipeline creation. The company says customer research across several pricing models favored outcome-aligned pricing, and cites early customer feedback reporting at least ten times the value.
Announcing Fin for Ecommerce: Fin’s next role as a Customer Agent
Fin for Ecommerce is a new Customer Agent role for Shopify merchants, combining shopping assistance with ecommerce support before and after purchase. It helps shoppers discover products through conversational questions, live browsing context, catalog retrieval, comparisons, complementary recommendations, cart updates, and checkout guidance, while handling returns, refunds, exchanges, order changes, tracking, and shipping questions in the same conversation. The system uses Fin Apex 1.0 with an ecommerce retrieval engine and connects to Shopify to sync products, variants, content, order data, inventory, and APIs. Merchants can add Messenger and set Fin live in minutes without manual training; Shopify API integrations also let Fin use Procedures for complex requests, with drafts based on account data and company policies for review. The announcement positions Fin as a single Agent spanning discovery, purchase, and post-purchase support, with named ecommerce brands already using it.
AI is the answer to the sales growth-without-headcount problem
Sales leaders have treated pipeline growth as constrained by headcount, making a 30% increase appear to require 30% more people. The post presents Intercom’s use of Fin, its Customer Agent, for inbound sales as a separate pipeline source rather than merely an efficiency layer for SDRs, with its own metrics, targets, and owner. Fin engages inbound prospects instantly, qualifies and routes high-intent visitors, and keeps lower-intent prospects warm, while SDRs focus on phone qualification, relationship-building, and helping trial users realize value. Drawing on customer-service implementation, the operating model includes dedicated AI ownership and continuous optimization against meetings, pipeline, and revenue. The conclusion is that AI can raise the pipeline ceiling above current headcount capacity, although the constraint shifts to how well the Agent understands the product, customers, and demand qualification.
Introducing the Sales Agent Blueprint
The Sales Agent Blueprint is a newly announced guide for sales, revenue, and AI transformation leaders seeking to launch and scale AI for inbound sales. It addresses manual inbound workflows in which leads wait in queues, making outcomes depend on team timing and capacity rather than buyer intent, and describes agents that engage buyers, qualify leads, and route high-intent opportunities in real time. The first available track, “Launch it,” covers understanding Sales Agents, building a business case, deciding whether to buy or build, evaluating performance with a five-step framework, planning deployment, and continuously training, testing, deploying, and optimizing the system. A second track, “Scale it,” is coming soon and will focus on redesigning the buyer journey, AI-first systems and ownership models, and pipeline generation and scaling.
Announcing Fin for Sales: A new role for Fin Customer Agent
Fin for Sales is a new role for Fin Customer Agent that handles inbound sales from initial engagement through qualification, routing, and conversion. It starts conversations across messenger and email, uses page context and smart suggestions, and applies playbooks, knowledge, enrichment, and memory to answer questions, handle objections, and personalize discovery. Fin qualifies prospects in real time by collecting details about use case, budget, fit, and timing, syncing structured context and conversation history to a CRM, and directing leads to sales teams or self-serve paths. It can book meetings through Chili Piper or Calendly, initiate trials or subscriptions, and hand off an AI-generated summary to representatives. The announcement reports early results including Fellow booking 18 previously unreachable meetings in January at around 48% conversion, while positioning Fin for Sales as part of a shared Customer Agent platform.
AI is approving our pull requests: Here’s how we made it safe
Intercom describes how it uses an AI PR review Agent to approve some pull requests amid a workflow where more than 93% are Agent-driven and engineers deploy hundreds of times daily. The system decomposes review into specialist sub-Agents that assess problem descriptions, intent alignment, safety, logic, best practices, and execution paths, while applying Intercom-specific guidance and enforcing smaller changes. In a pilot of more than 100 PRs, AI-approved changes had zero reverts and approval time improved 6–16 times at the 75th percentile; in four rollout weeks, 497 PRs went fully autonomous. Reported revert rates were lower for AI-authored than human-authored code in both backend and frontend comparisons, though the source says zero reverts will not necessarily persist. The process remains auditable, allows human review requests, and keeps the shipping engineer accountable for production behavior and rollback.
The hardest percentages
Complex customer-support queries are relatively infrequent but consume disproportionate handling time and shape customers’ memories of service, especially when they require action across systems. The post distinguishes informational, personalized, and action-led queries, then positions Fin Procedures as a way to automate complex cases through configurable multi-step processes using natural-language SOPs, branching logic, data connectors, and AI-powered simulations. Since managed-availability launch, Procedures has handled more than 1.5 million conversations across hundreds of apps, with volume doubling month over month; a randomized 5% holdout found CSAT 28.93% higher when Procedures ran. The product is available to all 8,000+ Fin customers and adds review, failure reporting, rollback, connector monitoring, email simulation, and Agent in the Loop checkpoints for human approval or missing integrations.
From swarms to product: Turning customer signals into scalable features
Intercom’s Fin teams use cross-functional swarms to identify customer needs while helping customers increase automation and understand the product. In these high-touch engagements, engineers, data scientists, and a product manager analyze conversations, APIs, Procedures, and workflows, using fast feedback to test configuration changes and estimate achievable automation; one manual taxonomy analysis took more than half a day and predicted a 70% rate that the customer achieved. Cockpit then encodes swarm patterns into repeatable workflows, letting customer success managers and Sales assess automation potential, diagnose issues, and suggest next actions across accounts without repeated data-science involvement. It also tests whether ideas generalize before product development. Patterns that prove broadly useful, robust, and scalable can move into product features such as the automation taxonomy in Insights and CX Score, which measures conversation quality; unlike Cockpit, product features must work for every customer without configuration.
Never stop disrupting yourself; introducing the Fin API platform
Fin API platform launch makes the models powering its customer-agent system available through APIs, with contracts starting at $250k annually. It says Fin currently resolves over 2M customer issues weekly across brands and runs on models trained by its AI group. Last week’s Apex announcement is described as a specialized customer-service LLM that beat frontier models from Anthropic and OpenAI in six-month production tests on resolution rate, latency, hallucination rate, and cost. Customers can choose the Fin Agent Platform, Fin Agent API, or direct access to Apex and related models for bespoke, specialized agents. The rationale is customer demand and a broader expectation that software differentiation will shift from features and interfaces toward agents built on differentiated AI.
Announcing Fin Apex: The age of vertical models is here
Fin announces Apex 1.0, a custom model trained by its AI Group for customer-service conversations, replacing frontier-lab models as the core answering model for nearly all English-language chat and email traffic. The post says Apex improves resolution, speed, hallucination rates, and cost, citing one gaming customer’s resolution rate rising from 68% to 75% overnight and describing a 22% reduction in unresolved conversations. Its development relies on proprietary evaluations and billions of human and agent interaction data points generated by Fin’s resolution engine, creating a training flywheel for further domain-specific improvement. The launch is presented as evidence that customer-service applications may need to become full-stack AI companies rather than relying on shared general-purpose models. It also argues that frontier labs face pressure to offer cheaper specialized models as post-training and task-specific data become more important.
Topics they write about
All topics →Weekly digest
The best engineering reads, once a week.