This is our 18th edition of CX-News.com in 2026. Every week, we cover the most important news and discussions for Customer Experience and Customer Support Leaders, in about 5 minutes per week.
The LinkedIn Newsletter is the short version. CX-News.com covers the operational impact and implementation considerations for each update. When you’re using a product or considering switching to one, head to the website for the deeper context.
We also host the Unresolved.cx podcast for CX leaders rebuilding their operations from the ground up. Not everyone can run AI experiments live in production, and the podcast covers what others have learned. You don’t have to do it alone.
When you know your processes need to change but don’t have time to fix them, you need a strategic partner. RushtoResolution.com offers 1-on-1 advisory sessions.
Pressure-test your priorities with someone who has 20 years of experience in SaaS Customer Experience.
Intercom Rebrands to Fin, Launches Ecommerce Agent
Fin, the AI customer service platform that announced its rebrand from Intercom, launched Fin for Ecommerce, a Shopify-native integration that combines product discovery, purchase guidance, and post-purchase support in a single chat conversation. The feature connects directly to a merchant’s Shopify catalog, syncing products, variants, pricing, and availability, and Fin handles both finding the right product and resolving returns or order changes without handing off to a separate flow.
Operational Impact
The practical shift is the removal of the wall between commerce and support in a single session. A customer asking about sizing and then following up about a return has historically moved between different contexts — different tools, different agents, or at minimum a hard context switch. Fin for Ecommerce handles both without a handoff. For teams already on Fin, setup starts with a Shopify connection; Fin then automatically drafts Procedures for common post-purchase requests, reducing manual configuration time. The pricing model ($0.99 per resolution) applies to both support queries and shopping interactions — a full shopping journey from product question to checkout counts as one resolution, not several.
Gorgias moved in the same direction in its Spring 2026 release, repositioning its chat widget as a native shopping interface with in-chat product pages and product grids. Fin for Ecommerce is Fin’s entry into that same category, with deeper Shopify integration and AI-driven product narrowing at scale.
Implementation Considerations
Full shopping capabilities are web messenger only. On iOS and Android, Fin automatically switches to support-only mode. Email, social, voice, and Slack are not supported. For brands whose customers primarily reach out through mobile or social, that limitation is meaningful and worth confirming before planning a commerce-enabled rollout. The Shopify integration is native — Shopify MCPs should not be used alongside it. Teams with complex catalogs or strict tone requirements may need to add guidance manually, though Fin works without it for most standard Shopify setups.
Gorgias Rebuilds Agent Workspace with Helpdesk 2.0
Gorgias, a customer support platform built for ecommerce, launched Helpdesk 2.0, a rebuilt workspace designed to surface customer context, order data, and AI activity directly within the ticket view. The update includes a redesigned customer timeline with filtering, Shopify order previews with product images, customizable metrics display, AI handover summaries, a left/right conversation layout, and a global navigation layer for agents managing multiple stores or inboxes.
Operational Impact
The most practical change for daily agent work is the AI handover summary. When automation escalates a ticket to a human, agents currently scroll the full thread to understand what happened. Helpdesk 2.0 surfaces a structured summary at the top: what context the AI gathered, what actions it took, and why it handed off. For teams running high ticket volumes with AI handling first contact, that single change reduces pickup time on escalated conversations. The customizable Shopify metrics view is useful for operations managing multiple product lines or store configurations — an agent supporting a subscription brand can prioritize different data fields than one handling one-time purchases.
Implementation Considerations
Teams trained on the previous layout will need adjustment time. Gorgias offers a 30-day toggle back to the old view, which eases the transition but can also delay full adoption if teams default to the fallback. The bigger operational risk is data quality: teams with messy ticket histories or incomplete Shopify data won’t see much benefit from the redesigned timeline or order previews. Clean, connected data is the prerequisite the feature announcement doesn’t name directly. Gorgias is also using “2.0” framing for what is, in practice, a UI redesign with useful workflow improvements — not a platform rearchitecture. Expectations should be scoped accordingly.
Siena Announces AI-Native CX Operating System
Siena AI, a customer service platform built for direct-to-consumer brands, announced Siena Renaissance, described as the first AI-native operating system for commerce brands. The company framed the announcement around consolidating fragmented CX tools — support, voice of customer, social media management, and reporting — into one connected system, with a live reveal at a May 13 event in New York City attended by brands including SPANX, Brooklinen, and Kitsch.
Operational Impact
For DTC brands running customer service across email, chat, social, and SMS, the fragmentation problem the announcement describes is real. An agent handling a warranty claim via email may have no visibility into the Instagram DM the same customer sent two days earlier. A support lead pulling VoC data is often working from a different tool than the one tracking CSAT or social sentiment. If Siena’s platform delivers on cross-channel memory and unified reporting, the operational benefit is fewer handoffs between tools and earlier visibility into customer issues across channels. Siena’s existing capabilities — including video understanding, review management, and order tracking — suggest the components for a unified system exist; the Renaissance announcement positions them together for the first time.
Implementation Considerations
The phrase “AI-native operating system” is positioning language, not a technical specification. What teams actually inherit depends on the depth of integrations and whether data from existing tools migrates cleanly. DTC brands with established tech stacks — Gorgias, Zendesk, Klaviyo, Yotpo — will face evaluation questions about replacing versus layering. The platform was revealed live during the window this newsletter covers, so full feature documentation and pricing are not yet publicly available. Teams evaluating Siena should request a detailed integration map before drawing conclusions about consolidation potential.
Linear Adds Release Tracking and AI-Written Release Notes
Linear, a project management and issue tracking platform used by software teams, launched Linear Releases, a feature that connects issue tracking to CI/CD deployment pipelines and tracks what code is live in which environment. The company also added the ability for Linear Agent to auto-generate release notes based on the issues included in a given release, available to Business and Enterprise plan customers.
Operational Impact
For support teams embedded in product feedback loops, this matters in a specific scenario: a customer reports a bug that engineering says is fixed, but the fix hasn’t deployed yet. Today, confirming deployment status means pinging an engineer or checking a Slack thread. With Linear Releases, a support lead can see directly whether a fix is merged, in staging, or live in production. That lookup happens repeatedly in many support operations, particularly for teams managing enterprise customers who expect status updates on outstanding issues. The auto-generated release notes are more useful for internal handoffs than customer-facing communications — when engineering ships a release, agents get a structured summary of what changed, closing the gap between deployment and support team awareness.
Implementation Considerations
Linear Releases requires integration with CI/CD tools, which is a technical setup step that may involve engineering support to configure correctly. The feature is gated to Business plans (up to 5 release pipelines) and Enterprise plans (unlimited); teams on Starter or Pro plans will not have access. For the auto-generated release notes to produce useful output, issues in Linear need to be consistently written and labeled — teams with inconsistent issue hygiene will get inconsistent notes. This is worth assessing before setting expectations with stakeholders about automation quality.
Decagon Partners with Block on AI Concierge Support
Decagon, an AI customer service platform serving enterprise clients, announced a partnership with Block, the financial technology company behind Cash App and Square, to deliver AI concierge experiences across Block’s customer-facing products. The announcement positions Decagon’s agents as the infrastructure for customer interactions where financial trust is central to the brand relationship.
Operational Impact
For support leaders tracking enterprise AI adoption, this partnership signals movement in financial services — an industry historically cautious about AI in customer interactions due to compliance requirements and trust considerations. Block’s combined customer base across Cash App and Square represents millions of financial interactions weekly. Deploying AI agents at that volume requires tight guardrails, defined escalation paths, and reliable identity verification. The fact that a company at Block’s scale chose a third-party AI vendor rather than building in-house is a notable signal for other enterprise CX teams evaluating build-versus-buy decisions.
Implementation Considerations
The announcement does not specify which Block products are live with AI support versus still in deployment. For teams in fintech or adjacent regulated industries evaluating enterprise AI vendors, the Block partnership adds reference credibility to Decagon’s profile but does not substitute for direct evaluation. Decagon’s Agent Operating Procedures framework — which lets CX teams write agent instructions in plain language while engineering maintains control over integrations and guardrails — is worth examining specifically for teams managing complex compliance requirements. Any vendor in a financial services environment will need to answer questions about data residency, audit logging, and escalation SLAs before deployment.
Miro Connects Visual Boards to Copilot and ChatGPT
Miro, a visual collaboration and whiteboarding platform, launched integrations with both Microsoft Copilot and ChatGPT that allow users to generate Miro boards, diagrams, flowcharts, timelines, and sticky notes directly from AI chat prompts. The Copilot integration works within Microsoft Teams, Outlook, and other Microsoft 365 applications; the ChatGPT integration is free and generates shared collaborative workspaces from natural language descriptions.
Operational Impact
For support and operations teams that use Miro for process mapping, workflow design, and retrospectives, both integrations reduce the friction between describing an idea and visualizing it. A support ops lead drafting a new escalation flow can describe it in ChatGPT and pull the result directly into a Miro board without starting from a blank canvas. The Copilot integration is more relevant for teams already in Microsoft 365 environments — it allows searching across Miro boards and Microsoft 365 content from a single interface, which helps distributed teams find process documentation without switching contexts. The ChatGPT integration positions Miro as the output layer for AI-generated plans, which is a workflow some support design teams already approximate manually.
Implementation Considerations
Both integrations are most useful for teams that already collaborate in Miro. For teams that don’t, neither integration addresses the underlying adoption question. The Copilot integration may require admin-level setup in Microsoft 365, particularly in enterprise environments with tenant restrictions on third-party connectors. The ChatGPT integration is free, but output quality depends heavily on prompt specificity — vague inputs produce vague diagrams. Teams should treat AI-generated visual output as a starting point for collaboration, not a finished deliverable.
Now this is:
Strategic Support for CX Leaders.
You’ve got ambitious Support targets and new metrics but you’re not sure what to prioritize first.
The list is long, the queue is getting longer, and you don’t have time to step back and think about CX strategically.
What if you could pressure-test your thinking with someone who’s spent 20 years building Customer Support operations?
No pitch, just a conversation.
