Tag: Intercom

Deeper AI Integration, Clearer ROI: How Mature Deployments Redefine Support Economics

Over the last year, I’ve had the same conversation with a lot of support leaders.

They’ve deployed AI and are seeing initial efficiency gains, but want to push beyond these early results and achieve meaningful transformation.

When AI is first introduced, the gains show up quickly. Teams resolve higher volumes of queries, free up capacity, and deliver faster responses. But the real opportunity for impact extends well beyond those initial wins. As AI becomes more deeply integrated into support operations, taking on harder, more complex work, those results compound, new ways to create and measure value open up, and the economics of support change entirely. That shift is where I spend most of my time with leaders—turning early efficiency into durable business value.

This sits at the heart of “The 2026 Customer Service Transformation Report.” In this reflection, I explore how deeper integration compounds impact and why that makes business value easier to articulate across the organization—especially to finance and product peers who need to see outcomes, not just output.

The teams going deeper are seeing higher returns. The research shows that 62% of support teams have seen their customer service metrics improve since implementing AI, with early wins showing up most clearly in speed and efficiency. But for teams that have reached mature deployment (where AI is fully integrated into operations) that number jumps to 87%.

As AI programs advance, measurement confidence surges. This chart shows how ROI tracking rises from 35% in exploring to 70% in mature deployments—evidence of a widening execution gap in customer service.

The same pattern holds for the ability to measure ROI. Among teams in early exploration, just 35% say they can measure their return on AI investment, but for teams at the mature deployment stage, that rises to 70%. In my experience, this is the moment the conversation shifts from “is AI working?” to “how much leverage are we creating?”

As AI becomes more embedded in support workflows, what teams choose to measure starts to change. In the early stages of deployment, ROI is typically understood through improved customer response times, lower cost to serve, and freeing up capacity. Teams focus on how much time AI creates and whether it’s relieving pressure on the support organization. These signals help validate that the system is working, but they say little about how that capacity is ultimately used.

As deployments mature, measurement starts to reflect a different intent. Instead of stopping at time saved, teams look at where that capacity is reinvested—into higher value customer work and revenue-generating activities. ROI becomes less about relief and more about leverage. I encourage teams to set targets for capacity redeployment and tie them directly to activation, retention, and expansion outcomes.

The report data shows this clearly. Across all maturity stages, the most commonly cited measure of ROI is "time freed up that the support team can use to focus on value-adding activities for customers." But at mature deployment, that signal intensifies, with 73% of teams citing it, compared to 56% at early exploration.

Mature AI deployments reveal clearer ROI: teams report more time freed for value-adding customer work (73% vs 59%) and more hours redirected to revenue-generating tasks (56% vs 34%) than initial rollouts.

What’s also interesting is that 56% of mature teams say freed capacity is being directed toward revenue-generating activities, up from 34% at initial deployment. That’s a powerful indicator that AI is shifting from a cost narrative to a growth narrative.

The result is a shift in economic intent: from measuring what AI saves to demonstrating how the capacity it creates is reinvested to drive growth. As a product leader, I anchor this conversation in outcome-based metrics and clear counterfactuals: what would it have cost to deliver the same experience without AI?

As AI takes on more work, the question moves from “does it save money?” to “how does it change the economics of support?” Legacy support economics were built for linear growth: more customer tickets meant more headcount, more outsourcing, and more software costs. Success was measured through containment—the number of queries that didn’t reach human agents. These models worked when volume and effort were tightly linked, but AI doesn’t scale linearly, and it needs to be evaluated differently.

To sustain AI investment and expand its impact, teams need to move beyond cost-cutting narratives and build a clearer case for business value. When done right, AI goes far beyond improving support efficiency. It rewires the financial model, breaking the link between support costs and revenue growth, and turning support into a contributor to customer activation, retention, and lifetime value. This means treating your AI Agent as a new workforce capability that changes how your support function creates and captures value. Here’s what value looks like in an AI-first model:

Deeper AI integration decouples growth from headcount. This split chart shows support volume surging while team size plateaus, revealing how automation unlocks scale, reduces costs, and makes ROI easier to prove.

Human productivity: Your team focuses on more strategic areas, not the queue.

System improvement: Every resolved query makes the system smarter.

Revenue influence: Support becomes a lever for activation, retention, and growth.

Organizational agility: You scale service without scaling headcount.

Leaders are racing ahead with real AI in support. Explore the 2026 Customer Service Transformation Report to see where deployment is stalling, benchmark your team, and get practical steps to scale automation that delights.

How does this look in practice? Intercom offers a compelling example with Fin. What started as a focused effort to improve their customer support experience has become one of the clearest illustrations of what happens when AI is fully embraced across an organization.

Since 2022, Fin has helped Intercom absorb more than a 300% increase in customer demand while improving the consistency of delivery—including supporting new routes into support for trial customers and website visitors. Today, Fin is involved in 97% of their customers' conversations. Of those, it resolves 83.5% end-to-end, putting their overall automation rate at 81%.

That depth of deployment allowed Intercom to scale service without scaling headcount. Without Fin, they would have needed at least 100 additional support teammates to meet rising demand and service standards.

As Fin took on the majority of day-to-day volume, the human support team shifted toward consultative work—helping customers adopt Fin more deeply, succeed faster, and unlock more value from the platform. Intercom now tracks metrics like “direct revenue generated” and “expansion revenue influenced” to understand the impact of these consultative support activities. This repositioned support from a cost center to an active contributor to long-term growth.

The throughline from The 2026 Customer Service Transformation Report is that deployment depth makes a significant difference. Teams that are investing in deeply integrating AI are reshaping how support scales and contributes to growth. Value becomes clearer as AI takes on more work, and support leaders can articulate that value to the rest of the business.

The gap between these teams and those still in the early stages is widening. A select group of pioneers are setting a new bar for what AI-powered customer service can deliver, and understanding what they’re doing differently is the first step toward closing that gap. If you want to dive deeper into the data and frameworks, you can download the report here: https://www.intercom.com/customer-transformation-report?utm_source=blog&utm_medium=internal&utm_campaign=20260128-report-owned-2026cstransformationreport&utm_content=chapterseries_2

Inspired by this post on The Intercom Blog.

February 13, 2026
Build CX Scores You Can Defend: My 5-step playbook for transparent, trustworthy AI metrics

“You don’t have to trust the algorithm; you can see exactly why a conversation earned the score it did.”

We recently shared how we redesigned CX Score to deliver deeper, more actionable insights across every conversation. The most common follow-up from support leaders was simpler and incredibly important: “Can I trust it?” It’s the right question—and it’s the one I use as my own bar for whether a metric is ready for the C‑suite.

CS teams are the subject matter experts on customer experience. They understand the nuance of what customers feel, the context behind every interaction, and the difference between a technically resolved issue and a genuinely satisfied customer. I’ve learned, conversation by conversation, that any metric we ship has to capture that nuance at scale—or it doesn’t deserve to be used.

We built CX Score to give support teams a complete view of how their customers feel across every conversation. It surfaces what’s working, what’s not, and why—so leaders can communicate impact clearly and drive change across support, product, and the wider business.

A CX Score in action: repeated CSV export failures trigger a low score and customer frustration, while the AI agent clarifies next steps and gathers details—turning raw signals into actionable support insights.

Here’s exactly how I approached building a trustworthy metric that support leaders can inspect, explain, and defend.

1) It’s grounded in how support teams define quality. I started with how experienced support professionals actually evaluate conversations—collecting real examples of strong, mixed, and poor interactions across industries, identifying the specific factors that shape overall experience, and writing plain-English rules for each. The result: CX Score applies the same criteria a trained support professional would use, not generic LLM assumptions.

2) It’s aligned with human judgment. We created a dataset of thousands of real customer conversations spanning multiple industries, languages, channels, and agent types. Each was manually reviewed by experienced support professionals—with two reviewers per conversation where possible and disagreement resolution to create stable consensus labels. The result: CX Score is trained and tested to behave like an expert reviewer, not a language model making broad guesses.

A modern CX analytics view shows how conversations flow from chat, email, and mobile into AI assistance, then to resolutions and sentiment outcomes—turning messy support data into a single, defensible CX Score.

3) It’s engineered by AI specialists. CX Score isn’t a prompt attached to an LLM. It’s a production system built by Intercom’s AI Group: 37 ML scientists and 350 engineers whose full-time focus is AI for customer service. The system includes specialized handling for long transcripts, model configuration tailored for support language and subtle sentiment, prompt engineering designed to default to neutral when evidence is weak, and a multi-stage evaluation pipeline that checks for precision, consistency, and reliability. The result: A metric built by a team that understands LLM behavior in production support environments, where accuracy and consistency matter most.

4) It’s validated statistically, not qualitatively. Trust requires measurement, not vibes. We tested CX Score across standard ML metrics: Precision (when the model flags a negative experience, how often do humans agree?), recall (how many human-identified issues does it catch?), and F1 score (the balance between both). We set an explicit bar: F1 above 0.8, representing high agreement with human judgment. We reran these evaluations through every revision, checking for regressions or biases, and I focused especially on negative experiences, because a false negative hides a real problem. The result: CX Score meets a measurable standard before it ships—not a gut check, a statistical requirement.

5) It was battle-tested with real customers. Lab accuracy isn’t enough. Customer environments are messy: Varied ticket types, mixed languages, unpredictable edge cases. Before release, we ran a multi-phase field test—shadow-scoring conversations with both old and new models, validating sensible behavior across agent type and conversation length, then rolling out to a controlled customer group who confirmed the scores felt right, reasons were clear, and insights were actionable. The result: CX Score shipped because real teams told us it made sense in practice, not because it passed internal tests.

From conversation to clarity: this visual maps the drivers behind a CX Score. Explore how policy feedback, answer quality, and effort combine to produce defendable insights support leaders can act on.

The importance of explainability. One of the most critical choices I made was ensuring CX Score isn’t a black box. Every score comes with clear reasons, concrete excerpts, and a short explanation of what influenced the rating. This turns the metric into something you can inspect, audit, and explain to executives. You don’t have to trust the algorithm. You can see exactly why a conversation earned the score it did.

A metric that evolves with your business. Customer expectations shift. Products change. AI improves. A trustworthy metric can’t be static. CX Score evolves with the same commitments that shaped its redesign: Evaluate the real signals that shape customer experience, keep the logic simple and interpretable, and ensure leaders can make clear decisions from it. It’s built to be a durable source of truth across every conversation.

The takeaway. In a world where products look the same and AI can generate any interaction, customer experience is one of the few differentiators that actually matters. Support leaders have built that expertise conversation by conversation. What they’ve lacked is a measurement system that could validate it at scale—one that’s reliable enough to report to the C-suite, explainable enough to defend in strategy meetings, and rigorous enough to drive real decisions. That’s what CX Score is designed to be: A metric that reflects the reality support leaders see every day, backed by the technical rigor to make it credible everywhere else.

Want to see CX Score in your workspace? Ask your admin to enable it for your team, and start using explainable AI insights to improve customer experience and coach with confidence.

Inspired by this post on The Intercom Blog.

February 9, 2026
Turn Every Support Ticket into Product Truth: My Playbook for Data-Driven CX Wins

Support tickets are the rawest signal of product truth. Leading product teams at HighLevel, I’ve learned that the fastest way to build what customers value is to transform frontline conversations into a repeatable, data-driven system for discovery, prioritization, and execution.

What if your support and product teams could unlock CX insights to turn every ticket into strategic product intelligence? Explore how.

Here’s the operating system I rely on. First, I connect our support stack (think Intercom and our CRM integration) into a unified analytics platform so every conversation, tag, and resolution is queryable. I don’t just count tickets—I segment them by product area, customer segment, lifecycle stage, and revenue impact to reveal patterns that roadmaps can act on.

Next, we standardize a shared taxonomy. Agents apply concise, high-signal labels (problem type, severity, intent), and we augment that with AI-driven auto-tagging to reduce noise and improve recall. The result is trustworthy “voice of the customer” data that product managers and support leaders can both stand behind.

Prioritization then becomes rigorous and fair. I weight themes by severity, frequency, ARR exposure, and time-to-value, and tie them directly to outcomes vs output OKRs. Amplitude analytics helps me quantify impact—what’s breaking activation, what’s dragging conversion, what drives retention analysis—so the backlog reflects business outcomes, not opinions.

Discovery is continuous by design. Product trios (PM, design, engineering) run weekly reviews of the highest-signal themes, recruit users straight from recent tickets, and prototype solutions quickly. We validate ideas with A/B testing when appropriate and ship targeted in-app guides to reduce confusion before it becomes a ticket.

Crucially, we close the loop. When we release a fix or improvement, we notify affected customers and the agents who flagged the issue. We track downstream effects—ticket deflection, CSAT, feature adoption, and time-to-resolution—so everyone sees how customer support ai strategy accelerates product-led growth.

This approach also builds culture. Empowered product teams treat support as a strategic partner, not a cost center. Agents become co-creators of the roadmap, and PMs gain a steady stream of product discovery opportunities grounded in real user outcomes.

If you’re getting started, a simple 30-60-90 can help: in 30 days, unify the data and agree on taxonomy; in 60, instrument dashboards and adopt a weekly insights ritual; in 90, align priorities to OKRs, launch targeted fixes, and measure business impact. That’s how tickets turn into product truth—and how CX insights drive compounding wins.

Inspired by this post on Amplitude – Perspectives.

January 8, 2026
4 Proven Ways to Keep Employees Informed and Engaged—from Onboarding to Lasting Adoption

Keeping employees informed and engaged isn’t just a communications challenge—it’s a product challenge. When we treat internal tools like products with clear activation moments, measurable outcomes, and continuous discovery, adoption moves from hope to habit. Over the years, I’ve seen small changes in how we onboard, communicate, and measure compound into dramatically higher engagement, better compliance, and faster time-to-value.

“How to improve onboarding, compliance, and internal communications within your employee tools.” That question guides my approach end to end—from the moment someone logs in for the first time to the day they become an expert, championing best practices across their team.

First, I personalize onboarding to accelerate user activation. I map the critical first actions and design a lightweight sequence of product tours and in-app guides that surfaces only what matters right now. Progressive disclosure, clear UX writing, and thoughtful tooltip design reduce cognitive load. I measure time-to-first-value, A/B test checklist microcopy to remove friction, and use Intercom or Pendo to deliver contextual walkthroughs by role, location, and permission level. Amplitude analytics helps me validate that the guided path leads to the intended activation event and sustained usage.

Second, I make compliance effortless and measurable. Instead of long trainings, I embed micro-learnings and policy nudges directly in the flow of work, with just-in-time prompts and short, scenario-based confirmations. I segment by role to avoid alert fatigue and localize where regulations require nuance. Completion rates, quiz accuracy, and time-to-complete are tracked alongside qualitative feedback. When compliance messaging underperforms, I run A/B testing on tone, timing, and format, then iterate until adherence is both higher and faster.

Third, I orchestrate internal communications as lifecycle messaging—not announcements. Employees get targeted release notes, role-specific tips, and in-app reminders aligned to their stage: new, adopting, proficient, or champion. I avoid channel sprawl by making the primary source of truth available in the product, then reinforcing it via email or chat only when necessary. CRM integration and audience rules ensure relevance, while a champions network and office hours create human touchpoints that deepen trust and accelerate adoption.

Fourth, I close the loop with analytics and continuous discovery. I instrument key events and run retention analysis to understand which behaviors predict long-term engagement. I look at cohorts before and after a new guide or product tour, and I compare lift in user activation and feature adoption over 14-, 28-, and 90-day windows. Amplitude analytics provides the behavioral picture; surveys, interviews, and passive feedback widgets explain the why. Together, these inputs power a product-led growth approach for internal tools—observable, repeatable, and improvable.

When teams ask where to start, I pilot one persona, one workflow, and one high-value outcome. I define the activation event, instrument it, launch a single targeted in-app guide through Pendo or Intercom, and A/B test the onboarding microcopy. Two weeks later, I review retention cohorts and completion data, talk to users, and either scale the pattern or iterate. That cadence builds credibility quickly because it ties every communication to a measurable result.

The payoff is tangible: faster onboarding, higher compliance, clearer internal communications, and employees who feel supported rather than overwhelmed. With disciplined messaging, smart instrumentation, and ongoing discovery, we can turn internal tools into catalysts for performance—and transform engagement from a campaign into a culture.

Inspired by this post on Pendo – Best Practices.

January 6, 2026
AIUC-1 Certified: How Intercom Raises the Bar for Trustworthy, Enterprise-Ready AI Agents

I build products on the belief that trust is earned in every design decision and every deployment. Trust has always been a first principle at Intercom, from our early investments in security and privacy to the globally recognized certifications that shape our approach today.

As AI becomes more deeply embedded in customer-facing work, it’s essential that businesses can rely on systems that are safe, reliable, and governed to the highest standards. That’s why we’re proud to share that Intercom is now AIUC-1 certified, becoming one of the first companies to meet the world’s first standard designed specifically for AI Agents. For leaders navigating AI Strategy and AI risk management, this is more than a badge—it’s a measurable leap forward in governance and operational rigor.

AIUC-1 is the first certification tailored to the unique risks and challenges of AI Agents. It complements broader AI governance frameworks like ISO 42001 by focusing on enterprise-specific concerns like security, customer safety, system reliability, data and privacy, society, and accountability. In practice, this alignment helps us translate policy into deployable safeguards across cybersecurity, data governance, and regulatory compliance.

To achieve certification, organizations undergo independent third-party audits and quarterly adversarial testing across more than a thousand enterprise risk scenarios. This continuous technical evaluation ensures that AI systems remain robust against fast-evolving threats and that safeguards keep pace with rapid progress in the field. As a product leader, I welcome this level of scrutiny—it’s how we operationalize threat detection and response and make agentic AI dependable at scale.

AIUC-1 itself evolves every quarter, incorporating new research, threat patterns, and global best practices. The standard is shaped by the AIUC-1 Consortium, launched in November with more than 50 founding members who collectively handle tens of trillions of dollars in payments and serve over a billion people daily. Intercom is proud not only to be certified, but to be recognized as a founding technical contributor helping shape the development of the standard. That continuous, community-driven iteration mirrors how we build—measure, learn, and harden—so our customers benefit from real-world, enterprise-ready AI.

Intercom has decades of combined experience in security, compliance, and trust, and we’ve consistently demonstrated that robust governance and fast innovation can coexist. Achieving AIUC-1 certification reinforces that the same rigor we apply across our platform also extends to Fin, our AI Agent. I’ve seen first-hand how risk and procurement teams evaluate generative AI: they expect clarity, evidence, and controls. This certification delivers independent proof that our approach meets those expectations.

For our customers, this certification provides independent validation that Intercom’s AI systems are safe, resilient, and enterprise-ready. It confirms that our AI is tested regularly, built with strong safeguards, and aligned with the expectations of modern security and risk teams. It also signals our continued leadership in shaping responsible AI practices globally, ensuring our customers benefit from standards built for real-world use. In short, you can move faster with confidence—without compromising on governance.

Intercom has always approached trust as an ongoing commitment. AIUC-1 strengthens the foundation we’ve built across other frameworks and certifications, including SOC 2, ISO 27001, ISO 27701, ISO 27018, HIPAA, HDS, and ISO 42001. Together, these certifications create a comprehensive control fabric across privacy, security, and reliability—critical pillars for any enterprise deploying gen AI into production workflows.

As AI technology accelerates, we will continue to evolve our safeguards, deepen our governance practices, and contribute to the standards that shape responsible AI. Our promise is simple: to build AI that is not only powerful and efficient, but safe, transparent, and deserving of the trust our customers place in us. That’s how we turn innovation into durable value.

You can learn more about our certifications and access our security and compliance documentation through the Intercom Trust Center.

Get started with Fin and see how an AIUC-1 certified, enterprise-ready AI Agent can elevate your customer experience with confidence.

Inspired by this post on The Intercom Blog.

December 8, 2025
Stop Chasing New Users: The Surprising ROI of Win-Back Campaigns That Actually Work

Over the years, I’ve learned that the most overlooked growth lever isn’t a shiny new channel—it’s bringing back the customers we already earned. When I rebalanced budgets from top-of-funnel acquisition to reactivation, the payoff was faster, more predictable, and far more cost-efficient. Reactivation compounds because it’s built on trust, product familiarity, and data we already have.

Discover why reactivating dormant users delivers better ROI than new acquisition. Learn how to identify and bring back at-risk users via targeted campaigns.

Why does this work so well? Dormant users once saw enough value to sign up, activate, or even pay. The barriers to return are lower: familiarity reduces friction, time-to-value shrinks, and the cost to engage is a fraction of new-user CAC. In practice, I’ve seen win-back motions outperform new acquisition on payback time, expansion potential, and long-term retention—especially when we design the right triggers and messages.

My approach starts with rigorous retention analysis. I define the behaviors that signal risk—declining frequency, shrinking session depth, stalled onboarding milestones, or missed “aha” moments—and map them to lifecycle stages. Using a unified analytics platform with CRM integration, I can see who’s drifting, when, and why. That clarity is the foundation for precision reactivation.

On the tooling front, I lean on Amplitude analytics to surface cohorts and leading indicators, Pendo for in-app guides and nudges, and Intercom for lifecycle messaging and human-assisted outreach. The connective tissue is our CRM integration, which ensures we coordinate messages across email, in-app, and sales-assist without creating noise or duplication.

Segmentation is where win-back campaigns gain power. I group users by their last successful use case, plan tier, activation depth, and the specific friction they hit. Cohorts often include “stalled onboarding,” “lapsed power users,” and “trial expired with partial success.” Each segment gets a distinct path back to value—never a one-size-fits-all blast.

Targeted campaigns are then matched to the root cause. For stalled onboarding, I deploy product tours and in-app guides that remove a single key blocker. For lapsed power users, I emphasize newly shipped capabilities tied to their historical workflows. For price-sensitive cohorts, I test usage-based offers or limited-time boosts aligned to value realization, not discounting for its own sake. Every flow is A/B testing-driven and time-bound, with clear exit criteria.

Measurement goes beyond “did they log in.” I track reactivation rate, feature adoption depth, time-to-value, and near-term expansion signals. Holdout groups validate lift, and we set guardrails so campaigns don’t cannibalize healthy cohorts. Over time, these learnings inform product roadmap decisions—what to simplify, what to sunset, and where to invest to prevent churn in the first place.

Operationally, I embed win-back into product-led growth rhythms. Product, data, lifecycle marketing, and support align on weekly reviews, using shared dashboards to tune triggers and content. This creates a reliable growth engine that respects user intent and avoids the trap of overmessaging.

Finally, trust matters. I build reactivation with privacy-by-design principles, transparent value propositions, and easy opt-outs. The goal isn’t to “get the login”—it’s to restore momentum toward outcomes the user cares about.

If you’re feeling acquisition fatigue, shift a meaningful slice of budget and attention to reactivation. In my experience, it delivers faster wins, better unit economics, and a healthier product that keeps more of the customers you worked so hard to earn.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Own Your AI: 4 Essential Roles to Supercharge Support and Prevent Performance Drift by 2026

AI doesn’t fail because the model is bad, it fails because ownership is missing.

When someone truly owns your AI, everything changes. Resolution and automation rates climb, the system self-improves, and the customer experience transforms in ways a dashboard alone will never show you.

This is part three of our five-part series on customer service planning for 2026. We’ll be sharing all five editions on our blog and on LinkedIn.

If you’d rather have them emailed to you directly as they’re published, drop your details here.

Last week, we introduced the four roles that make AI actually work in a support organization. These roles are already showing up inside the teams who are scaling AI the fastest, and this week, we get closer to the ground.

Here’s what these roles look like in practice — what they do, how they work, and why your AI performance will inevitably drift without them.

AI operations lead — owns AI performance, every day. I think of this person as the air-traffic controller for our AI Agent. I treat the AI as a living system that needs ongoing supervision, evaluation, and tuning. This role is accountable for what leaders care about most: quality, reliability, and continuous improvement.

The AI ops lead sees the whole picture: conversation quality, missing knowledge, flawed assumptions, unexpected failures, new opportunities for automation, and the subtle signals that the system is beginning to drift. In practice, that vigilance is the difference between steady gains and slow decline.

Day-to-day, here’s what I expect from this role.

1. Reviews AI conversations and surfaces performance patterns. The AI ops lead monitors the AI Agent’s behavior — the tone shift after a product launch, a sudden dip in resolution for a specific intent, or conversation clusters revealing new customer behavior. They scan for anomalies, trends, and early warnings, with an emphasis on what’s happening right now, not last week. Without this intentional ownership, I’ve watched a 2% dip turn into a 10% drop in days.

2. Prioritizes fixes and improvements. Once patterns emerge, they triage fixes like a product team handles bugs. Missing or incorrect content? They route it to the knowledge manager. Behavioral issues? They adjust guidance and guardrails. Action or system issues? They partner with the automation specialist. This connective tissue turns individual fixes into compounding improvements.

3. Defines and maintains AI guardrails. Leaders everywhere worry about AI doing things it shouldn’t. This role answers that fear by establishing clarification logic, escalation rules, “never answer” policies, and safety boundaries. The goal is predictable behavior that protects customer trust — an essential pillar of any AI Strategy and AI risk management practice.

4. Aligns reporting with leadership. The AI ops lead reports on resolution rate, CX Score, CSAT, automation coverage, and hours saved — making the economic impact visible. That visibility is a foundational step in any credible customer support ai strategy.

Why this role exists now. AI systems are dynamic and require constant tuning. A small dip in quality quickly becomes an operational issue, and no existing role naturally owns that. When someone does, teams feel the benefit almost immediately.

Knowledge manager — builds and maintains the structured knowledge AI depends on. I hear the same thing from leaders again and again: AI is only as good as the content you give it. This role is rapidly evolving from classic knowledge management into knowledge strategy — part content designer, part systems thinker, part information architect. Their job is to build the knowledge scaffolding that lets AI answer accurately, consistently, and safely.

Here’s how the knowledge manager creates leverage.

1. Writes, maintains, and improves support knowledge — continuously. After every product change, they update articles, remove duplication, resolve contradictions, and pay down “knowledge debt” that quietly erodes accuracy. The upkeep is shaped by AI performance; when patterns expose gaps, they fix the source.

2. Structures knowledge for AI, not for browsing. Traditional help centers are for humans skimming pages. AI needs clean intent signals, crisp formatting, and clearly structured language. The knowledge manager designs that structure as intentionally as the content itself.

3. Works hand-in-hand with AI ops. Many performance issues stem from missing or unclear knowledge. When the AI ops lead surfaces recurring misunderstandings or low-resolution categories, the knowledge manager resolves the root cause at the source.

4. Ensures accuracy and compliance at scale. As AI handles more sensitive situations, the knowledge manager safeguards correctness, currency, and compliance — critical for data governance and regulatory alignment.

5. Develops a cross-functional knowledge strategy. The role creates a canonical, cross-functional source of truth that product, engineering, product marketing, go-to-market, and support (AI and human) can all rely on.

Why this role exists now. This is one of the highest-leverage positions in an AI-first support org. Teams like Rocket Money and Anthropic are hiring knowledge managers because AI accuracy depends on the quality of knowledge feeding it. Without this role, resolution rate caps out early and never climbs.

Conversation designer — designs how the AI speaks, clarifies, and interacts. AI isn’t just a tool customers use; it’s a representative they interact with. Tone, clarity, pacing, and conversational structure matter, especially in voice. Every word affects perceived expertise, trustworthiness, and brand. The conversation designer ensures the AI feels human-friendly without pretending to be human — the sweet spot that builds trust without misleading customers.

In my experience, staffing conversation design early accelerates results. It changes not only how we tune AI, but how we understand the end-to-end customer experience.

Here’s what great conversation design looks like.

1. Shapes the AI’s tone, voice, and communication style. This role refines phrasing, tunes politeness, adjusts how confusion is handled, and shapes micro-interactions that determine whether customers feel cared for or dismissed. On voice channels, natural cadence is make-or-break.

2. Designs flows for high-value conversations. They design how the AI clarifies intent, branches, communicates uncertainty, verifies details, escalates, hands off, and returns to the main thread without feeling mechanical — treating customer experience as a product with language as the interface.

3. Translates procedures and complex workflows into natural language and logic. As AI runs structured procedures and actions, this role becomes a conversational system architect, translating SOPs into conditional logic with exceptions and fallbacks. For example, in Intercom, our conversation designer uses Simulations to run simulated conversations to see where the AI Agent gets confused, over-confident, or awkward, and refine flows until the interaction feels effortless end-to-end.

4. Ensures transitions to humans feel smooth and respectful. Handoffs should provide clear context to the human agent and maintain continuity so customers never feel dropped.

Why this role exists now. As AI becomes the primary interface, conversation design directly influences trust, brand perception, and operational outcomes. It’s a core competency for any Generative AI and LLMs for product managers program.

Support automation specialist — builds the backend actions that allow AI to do real work. If the conversation designer shapes expression, this role shapes capability. They transform AI from an answering machine into an outcome engine by bridging AI and the systems it must safely and deterministically act on.

Support teams increasingly expect AI to do what a human would do: refund a charge, adjust a subscription, verify an identity, update an account setting, or pull relevant data. That expectation creates a new technical role at the edge of support, ops, and engineering.

What I rely on this specialist to deliver.

1. Creates and maintains backend workflows the AI executes. This includes building and maintaining: Fin Tasks. Fin Procedures with embedded steps. Action flows that call internal and external APIs. Automations that span billing systems, user identity layers, CRM objects, subscription entitlements, refund tools, and more. They ensure the AI can act compliantly and predictably — the playbooks that turn intent into action.

2. Owns the integrations required for advanced automation. Many problems require data elsewhere — billing platforms, internal databases, systems of record. The specialist ensures the AI can retrieve, validate, and use that information safely, often partnering closely on CRM integration and internal services.

3. Partners closely with product and engineering. Some workflows require new endpoints, permission layers, safety gates, or deterministic fallbacks. This role drives those changes across the stack.

4. Ensures reliability and safety at every step. Guardrails, validation logic, exception handling, safe execution paths — all are essential. They confirm that the AI has access to the correct data, the action matches policy, edge cases are accounted for, risky flows have deterministic constraints, and every action is auditable and reversible.

Why this role exists now. Customers don’t want answers, they want outcomes. AI can now deliver those outcomes, but only with the right backend scaffolding. This role modernizes operational architecture and unlocks end-to-end automation.

How these roles work together — the new operating loop. These roles aren’t silos; they’re interdependent parts of one system. The AI ops lead identifies patterns and performance gaps. The knowledge manager resolves inaccuracies or missing content. The conversation designer improves clarity, tone, and flow. The automation specialist expands the system’s ability to take action. Each improvement compounds the next, moving you from early automation to transformational resolution rates through continuous refinement.

This loop is what separates teams that plateau early from teams that scale AI into a reliable, high-performing system — the essence of a durable AI Strategy.

How to get started (even if you can’t hire all four roles today). Most teams phase into this model: assign partial ownership, formalize responsibilities, then specialize as AI volume grows. Here’s the progression I recommend.

Phase 1: Assign ownership. Give each role’s core responsibilities to someone who can devote five to 10 hours weekly. Early on, support ops, enablement, senior ICs, and technically inclined teammates can anchor the work.

Phase 2: Formalize the responsibilities. As AI resolves more queries, optimization becomes core operational work. Formalizing ownership prevents performance drift and knowledge debt.

Phase 3: Specialize and hire. Once AI handles 50–70% of incoming volume, these responsibilities become full-time roles. Investing in specialization becomes essential infrastructure for the next scale stage.

The bottom line. AI changes the shape of your support team. These four roles — AI operations lead, knowledge manager, conversation designer, and support automation specialist — form the backbone of the AI-first support organization. They bring order to a constantly changing environment and enable AI to deliver the outcomes leaders and customers expect heading into 2026.

Next week, we’ll continue the 2026 planning series with a deep dive into org design models for AI-first support teams — how to structure people, workflows, and accountability in a world where AI resolves most conversations before a human ever sees them.

To follow along with the series and have each new edition emailed to you directly, drop your details here.

Inspired by this post on The Intercom Blog.

December 2, 2025
Unlock Clarity and Confidence: How the New CX Score Transforms Every Customer Conversation

Customer expectations have never been higher. People expect fast, accurate, and effortless support, every time—and across industries, from ecommerce to financial services to healthcare, customer experience has become one of the most strategic levers for achieving durable competitive advantage.

Here’s the challenge I’ve seen again and again: you can’t improve what you can’t see. For years, most support organizations have been making decisions based on only a tiny slice of their customer interactions, captured through surveys that reach only the most motivated (or frustrated) voices. In my own program reviews, the most revealing insights often hid in the conversations that never made it into CSAT or NPS.

We created CX Score to change that. CX Score gives teams a complete view of the customer experience across every meaningful conversation—no CSAT or NPS surveys required. I wanted a signal that reflected reality, not just a vocal minority.

After launching CX Score, we saw many teams immediately use it to understand performance trends, highlight experience issues, and surface gaps across support operations. That early momentum validated the approach and showed us where to go deeper.

As adoption grew, new opportunities emerged. CX leaders found value from CX Score—but they also wanted the model to capture more nuance and identify the specific drivers leading to negative or positive scores, giving them clearer direction on where to focus. I heard the same ask from my own leadership peers: make it explainable and actionable.

That’s what we’ve built into the latest iteration of CX Score. If you’ve been using CX Score for a while and have noticed it shift recently, that’s an expected evolution. A recent shift in scores does not mean your support quality has dipped or that Fin or your team is performing worse than before—this one-time shift reflects a more advanced, more complete model that understands customer experience more deeply with even greater coverage.

Why CX Score needed to evolve

In the initial release, CX Score evaluated each conversation using a combination of sentiment, resolution, and support quality signals. It provided strong early insight and surfaced experience trends that were previously invisible. But as we analyzed real-world conversations across thousands of companies, it became clear that even these combined signals didn’t fully capture the nuance of how customers actually experience support—especially in moments where the outcome was technically correct, but the path to get there involved unnecessary friction, repeated explanations, or unresolved product limitations.

This evolution of CX Score builds on that foundation. It incorporates deeper contextual understanding of the entire interaction, creating a more complete and accurate reflection of the customer experience. As a product leader, that depth matters because it turns a lagging metric into a coaching and prioritization system.

How CX Score has evolved: deeper, more actionable insights

We expanded the CX Score evaluation criteria. CX Score now looks beyond just how your team replied, and into the broader context of the customer’s experience—including reasons that may be outside your support team’s direct control but still influence how your customers feel.

Alongside core support quality signals, we’ve introduced several new dimensions that capture what customers are actually reacting to:

Answer quality (Fin): How well Fin answered the customer’s queries—were responses clear, accurate, and able to resolve the issue without contradiction or repeated clarification?

Answer quality (Teammate): How well a human teammate answered the customer’s queries, using the same criteria: clarity, accuracy, and resolution without contradiction or repeated clarification.

Customer effort: How much effort the customer had to put in to get help (e.g. repeating themselves, multiple handovers, chasing follow-ups).

Strong emotion: Whether the customer expressed strong positive or negative emotions (e.g. joy, gratitude, frustration, anger).

The new CX Score adds context to every conversation: a donut chart surfaces drivers like policy feedback and effort, while a side panel explains why this interaction earned a 3 based on signals from an AI agent chat.

Product/Service feedback: Whether the customer praised or criticized the product (e.g. features, bugs, design gaps, etc.) or the service (e.g. delivery, reliability, onboarding, performance, etc.).

Policy feedback: Whether the customer praised or criticized a company policy (e.g. refunds, returns, account rules, limits, eligibility, etc.).

Broader coverage: more of your support volume now contributes to CX Score

Previously, some conversations couldn’t be scored reliably, especially short, simple, or low-context exchanges—which meant your CX Score was based on only a subset of your total support volume. With this update, CX Score now uses a wider set of criteria to evaluate each interaction. The result: more conversations qualify for scoring, fewer gaps in coverage, and a CX Score that reflects your true support mix—not just the longest or most detailed threads.

Greater transparency with richer, more informative summaries

We’ve made it much clearer why each conversation received the score it did. Right inside the product, every scored conversation now surfaces the specific reasons that influenced its rating—things like high customer effort, strong negative emotion, or product feedback. This added visibility makes it much easier to understand what’s driving your CX Scores, build trust in how they’re calculated, and confidently use them in reporting, coaching, and decision-making.

On top of that, conversation summaries now weave these reasons together with context from the customer’s original query. Instead of scanning the full thread, you can quickly see what happened (the core issue and how it was handled) and why it was scored that way (the key signals that impacted the rating). In my workflow, this shift lets me move from reading transcripts to taking action much more quickly.

From visibility to taking action

As customer experience becomes one of the clearest ways businesses can differentiate, teams need more than visibility—they need clarity on where to invest their time and how to improve. With deeper context and clearer reasoning behind every score, CX leaders can quickly identify what’s working, what needs fixing, and what to prioritize. CX Score moves from being a measurement tool to a system for continuous improvement.

What this unlocks for CX teams: Automatically flag conversations for review. Route threads with high customer effort, strong negative emotion, or low answer quality to QA, team leads, or specialists. Auto-forward product feedback to the right teams. Send conversations with product or policy criticism directly to Product, Engineering, or Ops channels, with no manual triage required. Spot operational issues such as handoff loops, unclear answers, or inconsistent workflows. Share transparent, explainable insights directly with leadership.

The future of CX measurement

CX Score isn’t just another metric. It’s becoming a new standard. Some customers have already chosen to replace CSAT entirely, using CX Score as their primary measure of experience quality because of the broader coverage, deeper context, and clearer paths to action it offers. This reflects a broader shift across the industry: as new competitors emerge and product differentiation narrows, customer experience is becoming one of the most strategic ways to stand out; measuring it accurately and understanding it deeply is now essential.

Our focus going forward is to help teams diagnose issues faster, prioritize with confidence, and improve at scale. This is the foundation we’ll continue to build on: turning every conversation into insight, and every insight into action.

The new CX Score is rolling out gradually to all customers and will be in your workspace by December 3rd.

Want to see CX Score in your workspace? Get started →

Inspired by this post on The Intercom Blog.

November 25, 2025
The Hidden ROI of Win‑Backs: Reactivate Dormant Users Faster, Cheaper, and With Lasting Impact

I’ve learned the hard way that the fastest, lowest-risk growth lever is hiding in plain sight: reactivating the users we already earned. When our team prioritized win-back programs over new acquisition, we unlocked higher net revenue retention, shorter payback periods, and stronger product-market signal—with a fraction of the spend.

"Discover why reactivating dormant users delivers better ROI than new acquisition. Learn how to identify and bring back at-risk users via targeted campaigns." That insight matches what I see daily: win-back campaigns compound value because they capitalize on existing familiarity, prior data, and stored intent.

Here’s the ROI logic I use. New acquisition burns budget on education and trust-building before value is realized. Reactivation, by contrast, taps into latent demand and prior setup, which means lower effective CAC, faster time-to-value, and higher LTV recapture. In retention analysis, these programs often outperform prospecting by a wide margin because the user already knows how to get value—they just need a relevant nudge.

To find the right users to re-engage, I start with leading indicators of risk: declines in weekly active use, feature decay (e.g., key workflows not triggered), shrinking session depth, and unresolved outcomes. Amplitude analytics or a unified analytics platform help me segment cohorts by recency, frequency, and monetary signals, then rank accounts by churn propensity. I also track intent proxies like billing pauses, reduced seat utilization, and cooling support contact.

I group users into three practical tiers: “at-risk” (recent value decay), “dormant” (no critical events in the past 30–60 days), and “churned-eligible” (post-cancel window with a viable path back). Each tier gets a distinct message strategy, incentive structure, and time horizon. The goal is to match the intervention to the activation friction each group faces.

For creative strategy, I anchor on the outcome they originally hired us to deliver. I lead with the value proposition they care about, not the features. A strong win-back narrative reminds users of the job-to-be-done, showcases what’s improved since they last engaged (new capabilities, performance, integrations), and offers an effortless next step—often a guided “return-to-value” flow or a one-click way to pick up where they left off.

Channel orchestration matters. I use Intercom and Pendo to deliver contextual nudges, in-app guides, and lightweight product tours that meet users at the precise moment and screen of friction. With CRM integration, we coordinate email and SMS for timely follow-ups, then reinforce success in-product with progressive tooltips and checklists. The best-performing sequences pair a personalized message, a sharp call-to-outcome, and a low-friction path back to activation.

Experimentation is non-negotiable. I run A/B testing on subject lines, offers, and in-product prompts, and size tests with a minimum detectable effect (MDE) that’s realistic for each segment. We personalize content by prior feature use, industry, and plan tier to avoid generic blasts that underperform. Over time, the library of proven treatments compounds, and the system becomes predictively better at catching risk earlier.

Measurement should be unambiguous. I define “reactivation” as the return to a qualifying level of usage that mirrors healthy customers (e.g., core event completion in a set window), not just a login. I track reactivation rate, time-to-reactivation, reactivated revenue, payback, and LTV uplift versus holdout cohorts. Cohort views in Amplitude analytics reveal whether improvements are persistent, and whether we’re driving true behavior change or short-term spikes.

Trust is part of the strategy. We build privacy-by-design into all outreach and respect user preferences. Clear value exchange (why this message, why now, how to opt out) consistently improves response rates and strengthens long-term relationships—win-backs should feel helpful, not harassing.

Operationally, I pair product-led growth with lifecycle marketing: product teams ship the “return-to-value” experiences; growth teams run the orchestration; customer success brings context from the field; and analytics sets guardrails and success criteria. When executed as a system, win-backs turn from occasional campaigns into a durable, compounding growth engine.

If you’re chasing growth in a tight market, start here. Your next quarter’s ARR may be sitting in dormant cohorts that are one relevant nudge—one fast path to value—away from coming back.

Inspired by this post on Amplitude – Best Practices.

November 25, 2025
Intercom is now a Shopify Plus Technology Partner: AI-powered support to scale ecommerce

I’m thrilled to share that Intercom is now a certified Shopify Plus Partner on the Technology Track. As someone who obsesses over product quality, speed, and measurable outcomes, this milestone reflects the rigorous standards we hold ourselves to and the trust Shopify Plus merchants can place in our solution.

The Shopify Partner Program Technology Track supports the largest Shopify merchants by helping them find the apps and solutions they need to build and scale their business. The program is available specifically for Shopify Partners who provide a level of product quality, service, performance, privacy, and support that meets the advanced requirements of Shopify Plus merchants.

As a Technology Partner, Shopify has recognized Intercom as a provider trusted to help high-growth ecommerce brands scale.

“The Shopify Partner Program Technology Track is designed to meet the advanced requirements of the world’s fastest growing brands. We’re happy to welcome Intercom to the program, bringing their insight and experience in Customer Support to the Plus merchant community.”

— Jeff Kennedy, Head of Product Partnerships, Shopify

For Shopify Plus merchants, this certification means that our integration is vetted and optimized, and that our roadmap aligns with Shopify’s priorities. In practice, that translates into faster resolutions, less context switching, and more personalized conversations—without compromising privacy or performance.

Over the past year, we’ve launched a series of enhancements to our Shopify integration to give merchants more control and speed in support, including:

Data Connector templates so our AI Agent Fin can fully resolve requests from customers who want to get information about their Shopify order.

Multi-store support for merchants to manage conversations from multiple storefronts in one inbox.

Inbox order actions for merchants to take actions like editing shipping addresses, cancelling and refunding whole orders, deduplicating or creating duplicate orders based on existing ones, all without leaving the conversation.

EU workspace support to ensure merchants stay aligned with EU data residency requirements.

Launch your AI customer service faster—this hero graphic invites users to try the #1 AI agent with a bold headline and clear CTA, emphasizing practical, real‑world demos over polished Hollywood sizzle.

Updated data mapping and custom fields to keep Shopify order data and customer profiles fully in sync.

These updates make it faster and easier for merchants to resolve queries, personalize conversations, and drive loyalty, all from one platform. I’ve seen these capabilities reduce average handle time and minimize escalations—especially for complex order changes and post-purchase workflows.

We’re already seeing how our Shopify integration is helping merchants scale their support and deliver better customer experiences: teams are deflecting routine inquiries with AI while empowering agents to focus on high-value, relationship-building conversations.

Our team is continuing to invest in Shopify-specific capabilities. Here’s what we’re working on:

Expanded Fin Tasks for complex order actions with new pre-built workflows.

Enabling Model Context Protocol (MCP) support.

Smarter product search powered by Shopify data.

These additions will help merchants resolve faster, personalize at scale, and stay ahead of rising customer expectations – particularly as we approach peak season. We’ll continue to ship in tight feedback loops with Plus merchants to ensure each improvement moves the needle.

If you’re a Shopify Plus merchant, learn more about how we can help you scale your support with Fin, the best performing AI Agent for ecommerce. Ready to move fast? Get started with Fin now.

Inspired by this post on The Intercom Blog.

November 18, 2025
5 Costly UX Research Pitfalls I See Often—and How AI + Qual Insights Prevent Them

In product reviews and roadmap debates at HighLevel, I come back to a simple truth: great products start with great user research—but even seasoned teams fall into the same traps. After leading product discovery across empowered product teams and product trios, I’ve learned that a few avoidable mistakes consistently derail speed, quality, and outcomes.

Learn how to avoid the top five UX research pitfalls. Discover how AI and qualitative insights can help teams uncover the why behind user behavior.

The “why” behind user behavior is where durable growth lives. When we pair qualitative insights with analytics and a clear AI Strategy, we don’t just validate a solution—we de-risk the roadmap, improve user activation, and increase retention. Here are the five pitfalls I watch for and how I coach teams to avoid them.

Pitfall 1: Treating opinions as insights. Early in my career, I mistook strong stakeholder opinions for customer truth. Now I insist on a clear research question, a decision we will make with the evidence, and a hypothesis we’re trying to falsify. A/B testing is great for measuring impact when you’ve defined minimum detectable effect (MDE), but discovery research demands explicit learning goals and unbiased inputs.

How to avoid it: Write the decision statement first (“We will proceed with X if we learn Y”), then design the research. Keep a visible decision log so insights connect directly to product roadmapping and sprint planning, not to the loudest opinion in the room.

Pitfall 2: Leading questions and flawed methods. I still see interview guides that telegraph the desired answer. This corrupts the signal. Instead, I push teams to pilot guides with a product trio, remove solution language, and focus on behaviors. We complement interviews with in-app guides, targeted surveys, and session reviews using tools like Pendo and Intercom to capture moments of friction in-context.

How to avoid it: Ask neutral, behavior-first questions (“Tell me about the last time you…”) and validate with artifacts (screenshots, workflows). Pilot every guide with a colleague, then refine for clarity and neutrality.

Pitfall 3: Over-indexing on quantitative data and ignoring the why. Amplitude analytics and retention analysis tell me what happened; they rarely tell me why it happened. When teams chase dashboards without pairing them with qualitative interviews, we optimize for surface-level metrics and miss underlying jobs, anxieties, and unmet needs.

How to avoid it: Pair funnels and cohorts with a short round of qualitative interviews. Use Generative AI to summarize transcripts, cluster themes, and highlight contradictions, then validate themes against Amplitude analytics and CRM integration data. The synthesis is where insight emerges.

Pitfall 4: Recruiting bias—talking only to superfans or the most vocal detractors. If we only hear from power users, we build for edge cases; if we only hear complaints, we over-index on blockers. The result is a lopsided roadmap that misses mainstream value.

How to avoid it: Recruit across segments—new users, churned users, evaluators who never converted, and adjacent personas. Balance the sample and document who you didn’t talk to. For sensitive segments, lean on privacy-by-design practices and data governance so participants feel safe sharing candid feedback.

Pitfall 5: Weak synthesis and no path to action. Research often ends with a beautiful report that gathers dust. Insights must translate into choices: what we will do, what we will not do, and what we must learn next. Without this, research slows delivery without improving outcomes.

How to avoid it: Convert findings into atomic insights with evidence, confidence, and impact. Tie each insight to outcomes vs output OKRs, then schedule a decision review with the product trio. If you can’t articulate the decision, you haven’t finished the research.

How I use AI without losing the plot: I rely on LLMs for product managers to speed the busywork, not to replace judgment. Gen AI helps me transcribe, tag, and cluster themes; extract Jobs to Be Done; detect hesitation and sentiment; and draft UX writing variants for follow-up surveys. With a ChatGPT connector or similar tools, I can map qualitative themes to Amplitude analytics events and Pendo paths, revealing the narrative behind the numbers.

Guardrails matter: I apply AI risk management and privacy-by-design principles—no sensitive data in prompts, clear consent, and human-in-the-loop validation. AI is a force multiplier when the prompts are grounded in a solid research plan and the outputs feed a real decision.

A quick checklist I share with teams: define the decision and hypothesis; recruit a balanced sample; use neutral, behavior-first questions; triangulate quant with qual; synthesize into atomic insights; and link every insight to a concrete action or OKR. Do this, and you compress time-to-learning without sacrificing rigor.

When we respect the craft of research and thoughtfully apply AI, we consistently uncover the why behind user behavior—and build products that users adopt, love, and keep. That’s the fastest path to product-led growth and durable differentiation.

Inspired by this post on Amplitude – Perspectives.

November 11, 2025
Stop Falling for Hollywood Demos: The Unfiltered Truth of Live AI Voice for Support

I’ve sat through countless AI demos, and I’ve learned there are really two kinds: the “Hollywood demo,” which is polished to perfection, and the “real-world demo,” which shows the product raw—imperfections and all. The former dazzles, but the latter is where you discover what’s actually ready for prime time.

Hollywood demos look great, but sometimes need a closer look to make sure what you see is what you’ll get. When I’m evaluating an AI Agent for customer service, I always look past the polish. I’m assessing how well it will handle real-world scenarios—the messy, complex conversations your team deals with every day. That’s especially true on voice, the toughest channel to get right.

Voice is one of the toughest tests of any AI system. It’s not just “chat with speech.” An AI Agent needs to be able to listen, respond, and adapt in real time. Timing, tone, and turn-taking are all part of the product, they shape the experience as much as accuracy or reasoning.

An edited video might sound seamless, but it can’t show how a system behaves in a real support environment—like when a conversation takes an unexpected turn or when it pauses briefly to reason or retrieve data. Those small moments—latency, clarifications, interruptions—are when you see what the AI Agent is really capable of. A real-world demo lets you see and hear how the system actually behaves under real conditions, not in a controlled environment that’s been smoothed out with editing.

That’s why the live Fin Voice demo at Pioneer stood out. The team called Fin live on stage to show the real thing (with real latency and interruptions) so people could understand the product they’d be deploying to their own customers. As a product leader, I appreciate that level of transparency because it mirrors how customers will experience the system in production.

When Paul Adams, Chief Product Officer, demoed Fin Voice at Pioneer, the goal was to show the product exactly as customers experience it. In 90 seconds, Fin verified his identity, retrieved account data, managed an interruption, offered options, completed the workflow, and sent a follow-up email. That’s the kind of end-to-end outcome I look for—fast verification, accurate retrieval, natural pacing, and a closed loop.

Latency. You could hear brief pauses while Fin fetched subscription details and checked backend systems. That wasn’t lag—it was work happening in real time. In voice AI, thoughtful latency that signals reasoning is far better than synthetic speed that collapses under real load.

Natural conversation flow. Fin detected when Paul finished speaking, handled interruptions gracefully, and replied in short, human-like turns. That turn-taking behavior is essential for trust and comprehension in voice customer support.

Awareness and tone. Subtle changes in pacing when Paul laughed or hesitated showed sensitivity to context. Tone control is not a “nice to have” in voice—it’s a core UX capability.

Unscripted conversation design. No rigid IVR menus or fixed paths. Paul spoke naturally, and Fin adapted to resolve his query. That adaptability is what differentiates a true AI Agent from a glorified decision tree.

Those details are the real test. A voice AI Agent that performs well in a live demo is one that will perform well for you and your customers too.

Voice has been one of the most demanding, and rewarding, areas of development for Fin. Since launch, we’ve been expanding what it can do so support leaders can customize how Fin sounds, behaves, and aligns with their brand.

Voice and tone customization: Choose from multiple natural voices, set greetings, and fine-tune how Fin communicates with customers.

Escalation and conversational guidance: Teach Fin to use your terminology, ask clarifying follow-ups, and escalate when needed.

Deployment controls: Manage rollouts, test safely in internal environments, and fine-tune before going live.

Flexible integrations: Connect to any telephony system via call forwarding, and link Fin Voice to backend systems or APIs to take action.

Multilingual capability: Fin Voice now supports 28 languages natively.

Alongside these features, we’ve made big improvements to Fin’s answer quality—the foundation of a great voice experience. When people call, they’re looking for accurate, immediate answers they can trust.

So we’ve focused on three key areas: low latency, which is down roughly 30–40% since launch; clarification flow, so Fin asks smart follow-up questions to reduce back and forth and improve resolution rates; and voice-specific answer structure, so Fin delivers information in shorter sentences with pacing designed for listening.

Together, these improvements mean customers get the highest-quality answers as quickly as possible, resulting in more resolutions and better experiences.

Running a live demo always carries risk because things can go wrong. But that’s also why it matters—because that’s how customers experience it too. Support leaders stake their reputation on the systems they choose, so the only way to understand what you’re putting in front of your customers is to see it under real conditions.

When you see Fin in a demo, you’re seeing the same system that runs in production. Real-world demos take more effort and don’t always go perfectly, but they show what’s real—and that’s exactly what you need to evaluate before you deploy voice AI at scale.

Inspired by this post on The Intercom Blog.

November 11, 2025