Welcome to Customer Experience News, a place to learn about updates and releases from all of the tools that are building solutions for Customer Support, Success, and Growth. If you’re considering different tools to solve your specific workflow, this podcast is for you.
The major theme of December 2025 product launches were connecting tools together.
Think of it as the last product pushes to end 2025.
The focus was heavily on connecting customers and connecting teams.
You might learn about connections you’ve been waiting for.
This podcast is sponsored by Rush to Resolution.
When support volume becomes difficult to manage, customer retention drops, or you need a scalable operational strategy, Rush to Resolution organizes, prioritizes, and optimizes your customer support operations.
They deliver both strategic guidance and implementation to match where you are and where you’re going.
Connect with Brett to build that scalable customer experience your company deserves without adding headcount.
Now, let’s dive into the news.
Intercom announces many updates
Intercom announced mid-December a major wave of updates for Fin, their AI agent.
- CX Score Reasons breaks down customer satisfaction beyond just ratings—you’ll see what’s actually driving scores, like user effort or answer quality, in both individual conversations and aggregate reports.
- Trending Topics flags weekly volume spikes or drops and resolution rate shifts, with AI summaries so you can spot outages or issues without reading every conversation.
- Fin now works in Slack—you can resolve tickets, manage conversations, and send broadcasts directly in Slack channels where your customers and teams already are.
- Fin Audiences lets you segment customers once at the system level—like buyers versus suppliers—and those rules automatically apply across all content and workflows.
- Finally, a centralized Change Log tracks every deployment and configuration change, so you can actually diagnose what broke when Fin starts misbehaving.
—
Linear Connects to Major Support Platforms
Linear launched integrations with Intercom, Zendesk, and Gong in mid-December.
The core capability: automatic ticket-to-issue creation with bidirectional syncing.
What it does: Support agents can create Linear issues directly from customer conversations.
The integration pulls in conversation context, customer details, and relevant metadata.
When engineering updates the issue status in Linear, that information flows back to the support ticket.
Operational consideration: This only works if your team has clear criteria for when a ticket becomes an engineering issue. Without defined escalation rules, you’ll end up with Linear cluttered with non-bugs and support tickets that never get proper resolution updates. The automation is only as good as your triage process.
—
Help Scout’s Linear Integration Gets Smarter
Help Scout shipped an enhanced Linear integration in December with improved context sharing.
When creating issues from conversations, the integration now captures the full conversation thread, not just the initial message.
What’s notable: Help Scout also rolled out AI-powered article suggestions in their November update.
The system analyzes conversation content and recommends relevant help center articles to agents in real-time.
—
Gorgias Opens Up Statistics API
Gorgias introduced a new Statistics API in December, allowing teams to pull support metrics into external reporting systems and data warehouses.
What it enables: Teams can now extract ticket volume, response times, resolution rates, and agent performance data programmatically.
This matters for organizations that need support data integrated into broader operational dashboards or want to build custom reporting.
Support Leaders, make it easier on yourself.
Get these posts sent to your inbox.
—
Front Brings AI to Slack Conversations
Front launched AI capabilities for Slack-based support in December.
Teams using Front to manage customer conversations in Slack channels can now access AI-powered draft responses and conversation summarization.
—
Pylon Adds Slack Channel Context and Analytics
Pylon shipped two updates in December: enhanced Slack channel context and improved conversation analytics.
The Slack update allows support agents to see which channels a user is active in and recent messages, providing better context for support conversations.
The analytics update provides clearer visibility into conversation volume trends and resolution patterns.
—
Plain Introduces Manual Workflow Triggers
Plain added manual workflow triggers in December, allowing agents to initiate automated workflows on-demand rather than relying solely on automatic triggers.
What this enables: Agents can manually kick off predefined sequences—sending follow-up emails, creating tasks, updating custom fields—without needing automatic conditions to be met. This gives teams more control over when automation runs.
—
Zendesk approval workflows
- Approval workflows got more practical. End users can now comment directly on approval requests, and you can assign approvals to entire groups instead of individuals—so requests don’t sit waiting for one person to get back from vacation.
- AI agent controls improved. You can now set escalation limits for email AI agents and track which specific use cases are actually driving automation success. Finally, some visibility into what’s working.
- Security and compliance expanded. Two-factor authentication now works via email, data masking extends to light agents, and the access log provides better context for monitoring agent activity.
—
Birdie provides a VOC template
Birdie announced their Voice of the Customer template and I loved the setup.
This is just a shout out to a great resource provided by Birdie.
—
The Real Pattern: Integration Infrastructure
Looking across these updates, the pattern it integration infrastructure.
Platforms are focused on connecting existing tools more intelligently.
Before jumping in and enabling any of these updates, the product teams assume that you have:
- Clean and organized data in all connected systems
- Standardized processes that can be automated
- Technical capability to configure and maintain integrations
- Agent training and adoption resources
Most support teams don’t have these foundations.
Adding sophisticated integrations on top of messy processes just creates sophisticated mess.
What Support Leaders Should Consider
Before implementing any of these updates:
1. Audit your current tool usage Are you actually using the features you already pay for? Adding more integrations won’t fix underutilized tools.
2. Evaluate your data quality Linear integration won’t help if your ticket data is inconsistent. AI article suggestions are useless if your KB is outdated. APIs don’t solve bad data problems.
3. Assess your team’s technical capability Can your team configure, maintain, and troubleshoot these integrations? Or will they become another thing that “used to work” until someone broke it?
4. Define your processes first Automation requires repeatable processes. If every ticket is handled differently, integration features won’t change that.
The platforms are building impressive connectivity. The question is whether your operations can support it.
If you need someone to talk to about organizing your Support Operations, connect with me and let’s talk.
This no-pressure meeting is your chance to explore how I can help optimize your Support strategy.
Looking forward
I’m looking forward to early Q1 updates, announcements and pivots. December finishes off everything companies have been working towards, and now we’re excited to see the new ideas and innovations for 2026.
That does it for today’s podcast, see you next Friday.
Support Leaders, make it easier on yourself.
Get these posts sent to your inbox.
