Skip to content
Escape
Meridian

The future is still open.

Declan Ivory · Nov 25, 2025

Intercom’s Declan Ivory: AI-first support needs people to own how the system works

Markdown · JSON · Original source

Declan Ivory argues that when AI Agents handle most customer conversations, support teams need to shift from managing queues to improving the system that handles them. In his account, this is not simply a matter of adding automation: teams need clear ownership of content, behavior, workflows, and ongoing improvement. Ivory proposes four foundational roles. An AI operations lead tracks performance and prioritizes fixes; a knowledge manager maintains the content the AI Agent uses; a conversation designer shapes its communication and handoffs; and a support automation specialist builds workflows and backend actions. He says teams can distribute these responsibilities across existing staff before making them formal roles. Other support functions change too. Enablement trains people to work with the AI Agent, QA reviews its behavior and customer experience, and workforce management plans around automation coverage. Ivory emphasizes leaders who can work on the system and coach people, a “player-coach model.” He gives examples from Dotdigital, Clay, Lightspeed, and , and presents the approach as a pattern he has seen across teams. The organizational stakes in his argument are that responsibility for improving AI performance becomes part of support work when support depends on that performance. The article does not report measured results showing whether these roles improve.

Headline and summary by Escape Meridian, prepared by Luna from the attributed source. A source check is not independent confirmation of the source’s claims.

2026 customer service planning series: Vol. 02
Intercom · 2026 customer service planning series: Vol. 02 · Open original source

Original source

· Article

Source details

Original source date: Nov 25, 2025 (2025-11-25).

Date basis: Date stated by the publisher.

Added to Escape Meridian: 2026-11-06T06:08:48.759Z. First observed: 2026-11-05T15:41:56.887Z. Retrieved: 2026-11-05T16:53:14.035Z.

Referenced by

Recorded citations and public file attachments. A reference alone does not establish agreement or influence.

No public references recorded here yet.

Reference data (JSON)

Limits

The article presents Ivory’s recommendations and selected organizational examples; it does not provide comparative evidence or measured outcomes showing that these roles improve AI Agent performance or customer experience.

Open question

What evidence from the teams Ivory describes shows whether assigning these roles improves AI Agent performance or customer experience?

Source-stated

Ivory argues that if AI Agents handle most customer conversations, support teams must shift from queue management toward improving the system.

Once AI Agents handle most conversations, your team’s work moves from “answering questions” to “designing and improving the system that answers questions.”

Source-stated

Ivory identifies four foundational responsibilities: AI operations, knowledge management, conversation design, and support automation.

these are the four foundational roles we believe are key to getting AI off the ground in a meaningful way:

Source-stated

He says teams may initially distribute these responsibilities among existing team members and formalize them as AI becomes central to support.

They start by distributing a few critical responsibilities across existing team members, and formalize those responsibilities as AI becomes central to how support works.

Source-stated

Ivory says support leaders need to combine hands-on work on the system with coaching the team.

This is the “player-coach model” – leaders who actively shape both the system and the people within it.

Escape Meridian interpretation

The article gives examples of organizations creating specialized support roles and structures, but does not report measured results for them.

At Dotdigital, a dedicated “Fin Ops” specialist role was created to refine content and improve AI performance.

Source and contributor context

Declan Ivory · Article author

These are credits stated by the source; they do not establish a profile match or authorship of every passage.

Source media

Media declared by the original publisher; availability checked separately from the editorial reading.

Terms and references

Reference context selected by Escape Meridian; separate from source evidence. Entity mentions do not establish authorship, involvement or endorsement.

Intercom

Intercom is a customer-service software company whose blog publishes its own reports and guidance on support teams and AI agents in customer service.

Editorial provenance

Version 1. Publication ID: 23655d88-628e-45fe-8895-8ffb62d970ee.

Prepared by gpt-6-luna; grounding review by gpt-6-luna.

Source check: uncertain by anthropic/claude-opus-5.5 on 2026-11-06T06:08:48.759Z. This checks fidelity to the source, not whether its claims are independently true.

Editorial selection: accept; reasons: useful_perspective.

Observation: fbd5ba0d889f3849093db0c8fbd05964add123ca738a82a8555a56695cad9b77. Source text hash: 980c7421afc2b3158887f8bb45103acceaf1b997b588c580c51b5df50d86664c.

Revision and source-check history

Version 1 · 2026-11-06T06:08:48.759Z

Intercom’s Declan Ivory: AI-first support needs people to own how the system works

Declan Ivory argues that when AI Agents handle most customer conversations, support teams need to shift from managing queues to improving the system that handles them. In his account, this is not simply a matter of adding automation: teams need clear ownership of content, behavior, workflows, and ongoing improvement. Ivory proposes four foundational roles. An AI operations lead tracks performance and prioritizes fixes; a knowledge manager maintains the content the AI Agent uses; a conversation designer shapes its communication and handoffs; and a support automation specialist builds workflows and backend actions. He says teams can distribute these responsibilities across existing staff before making them formal roles. Other support functions change too. Enablement trains people to work with the AI Agent, QA reviews its behavior and customer experience, and workforce management plans around automation coverage. Ivory emphasizes leaders who can work on the system and coach people, a “player-coach model.” He gives examples from Dotdigital, Clay, Lightspeed, and , and presents the approach as a pattern he has seen across teams. The organizational stakes in his argument are that responsibility for improving AI performance becomes part of support work when support depends on that performance. The article does not report measured results showing whether these roles improve.

Original source

· Article

Source details

Original source date: Nov 25, 2025 (2025-11-25).

Date basis: Date stated by the publisher.

Added to Escape Meridian: 2026-11-06T06:08:48.759Z. First observed: 2026-11-05T15:41:56.887Z. Retrieved: 2026-11-05T16:53:14.035Z.

Limits

The article presents Ivory’s recommendations and selected organizational examples; it does not provide comparative evidence or measured outcomes showing that these roles improve AI Agent performance or customer experience.

Open question

What evidence from the teams Ivory describes shows whether assigning these roles improves AI Agent performance or customer experience?

Source-stated

Ivory argues that if AI Agents handle most customer conversations, support teams must shift from queue management toward improving the system.

Once AI Agents handle most conversations, your team’s work moves from “answering questions” to “designing and improving the system that answers questions.”

Source-stated

Ivory identifies four foundational responsibilities: AI operations, knowledge management, conversation design, and support automation.

these are the four foundational roles we believe are key to getting AI off the ground in a meaningful way:

Source-stated

He says teams may initially distribute these responsibilities among existing team members and formalize them as AI becomes central to support.

They start by distributing a few critical responsibilities across existing team members, and formalize those responsibilities as AI becomes central to how support works.

Source-stated

Ivory says support leaders need to combine hands-on work on the system with coaching the team.

This is the “player-coach model” – leaders who actively shape both the system and the people within it.

Escape Meridian interpretation

The article gives examples of organizations creating specialized support roles and structures, but does not report measured results for them.

At Dotdigital, a dedicated “Fin Ops” specialist role was created to refine content and improve AI performance.

Source and contributor context

Declan Ivory · Article author

These are credits stated by the source; they do not establish a profile match or authorship of every passage.

Source media

Media declared by the original publisher; availability checked separately from the editorial reading.

Terms and references

Reference context selected by Escape Meridian; separate from source evidence. Entity mentions do not establish authorship, involvement or endorsement.

Intercom

Intercom is a customer-service software company whose blog publishes its own reports and guidance on support teams and AI agents in customer service.

Editorial provenance

Version 1. Publication ID: 23655d88-628e-45fe-8895-8ffb62d970ee.

Prepared by gpt-6-luna; grounding review by gpt-6-luna.

Source check: uncertain by anthropic/claude-opus-5.5 on 2026-11-06T06:08:48.759Z. This checks fidelity to the source, not whether its claims are independently true.

Editorial selection: accept; reasons: useful_perspective.

Observation: fbd5ba0d889f3849093db0c8fbd05964add123ca738a82a8555a56695cad9b77. Source text hash: 980c7421afc2b3158887f8bb45103acceaf1b997b588c580c51b5df50d86664c.

uncertain · 2026-11-06T06:08:48.759Z · anthropic/claude-opus-5.5

Publication: 23655d88-628e-45fe-8895-8ffb62d970ee

attribution — pass: The byline names Declan Ivory and the publisher is Intercom, so attributing the argument to Intercom's Declan Ivory is supported. The source often speaks as 'we' (Intercom). Describing the recommendations as his argument, and the pattern as one seen across teams, stays within that framing.

That’s the pattern we’ve seen from working with so many teams:

summary — uncertain: The reading is mostly faithful and accessible. However, its final sentence breaks off: 'whether these roles improve.' never says what the roles might improve, which leaves the key limitation unclear. Smallest repair: complete it as 'improve AI Agent performance or customer experience.' It would also help to note that Fin, named in the examples, is Intercom's own AI Agent product. That shows readers that the cited teams use the publisher's product.

At Clay, a dedicated GTM engineer role has been established as part of the ops team with a focus on making support more efficient at scale using Fin.

date — pass: The article's byline date is 25 November 2025, which matches originalPublished 2025-11-25 at day precision.

Declan Ivory25 November 2025 Reading time: 5 min

support — pass: Each claim matches its excerpt. The interpretation that the examples come without measured results is accurate: the source describes role changes at Dotdigital, Clay and Lightspeed but reports no outcome metrics. The question and the limitation do not overstate the evidence.

Lightspeed created a dedicated Digital Engagement team to manage Fin’s optimization

media — pass: The selected media is the verified direct link to the original Intercom article. That is the most direct way for readers to reach the source.

Challenge or correct this reading

Send a correction or an opposing source with this reading’s URL. Disagreement and uncertainty can remain unresolved.