Stagewright with Intercom Fin

The problem, in Intercom customers’ words

In April 2026, an Intercom customer asked Intercom to “Auto-flag Help Center articles that go stale when we ship product updates, and suggest the edits needed,” because it “Reduces outdated self-serve content, improves Fin resolution rates … and scales KB maintenance as release velocity increases.” Another replied that it “would be super impactful and reduce our time manually locating existing articles that require edits due to a product release.” (Intercom Community)

A Fin admin on r/CustomerSuccess: “All of this.. Just for Fin not to know how to answer a question such as “How to log in”..” Later in the thread: “Final decision did land on deleting past 3 years of Docs (inside Intercom) and will start over from scratch because it totally got out of the control..” (r/CustomerSuccess, reply)

A knowledge manager on r/technicalwriting, about their knowledge base: “70% [of them] at this point isn’t (it’s causing user confusion and degrading the chatbot and AI summary output) because no one has been treating them like living docs.” (r/technicalwriting)

More on why this happens: Stale articles are why your AI support agent answers wrong.

What Fin Operator does

Intercom: “Give Operator a brief about anything, from a new feature or policy change to release notes, and it finds every article in your help center that needs updating.” It can “find and update every mention across your entire knowledge base — articles, snippets, and internal articles — in one go.” Since September 2026, Recommendations “reviews the conversations Fin couldn’t resolve and surfaces prioritized fixes.” Every change is a proposal, and it needs the paid Pro add-on.

What its docs don’t describe, as of October 2026: watching code or deploys, checking an article against the product, or touching screenshots and video. It updates text from what you tell it.

What Stagewright adds

It notices the change. Operator needs a brief. Stagewright runs on the pull request, so the flows that changed are known before the release, and the PR comment lists them: which walkthroughs changed, with before and after frames.
It checks the article against the product. Each Intercom article is mapped to the feature it explains and marked ▲ failing when that feature’s walkthrough fails, ◐ stale when the UI changed after the article’s last edit or it names a label no screen has any more, ● fresh when it was checked against a current walkthrough.
It supplies the pictures. When a walkthrough change is approved, the linked article is updated as a draft with step text, annotated screenshots and the video, stamped with the build it was recorded from.

Using both

A pull request changes how inviting a teammate works. Stagewright’s check shows the “Invite a teammate” walkthrough changed; the author approves it.
On merge, the linked Intercom article arrives as a draft with new steps, screenshots and video. You review and publish it.
Give Operator the PR comment’s list of changed flows with your release notes as the brief, and it finds the other articles, snippets and internal articles that mention them.

There’s no direct integration between the two. The handoff in step 3 is a person, or a Stagewright webhook on approvals that you wire to your own process.

Side by side

Stagewright and Fin Operator

Stagewright and Fin Operator: Stagewright and Fin Operator
Capability	Stagewright	Fin Operator	Source
What starts an update	A pull request that changes a flow an article describes	A brief from a person, such as "Attached are the release notes, update my content"	source
Finds the articles affected	Articles mapped to the features whose walkthroughs changed or failed	"finds every article in your help center that needs updating"	source
What it changes	The steps, screenshots and video of a flow, recorded from the product	Text in articles, snippets and internal articles	source
Checks the article against the running product	Yes	No. Not documented, per their public docs as of October 2026	source
Screenshots and video	Yes. With the build they came from and when they were last verified	No. Not documented, per their public docs as of October 2026	source
Nothing goes live without a person	Approval in the PR; articles arrive in Intercom as drafts by default	"Fin Operator proposes, you review, you approve. Nothing goes live until you say so."	source
Learns from unresolved conversations	Conversations grouped into redacted question clusters per feature	"Recommendations reviews the conversations Fin couldn't resolve and surfaces prioritized fixes"	source
Answers customers	No. We make the articles right for Fin to answer from	No. Operator "cannot respond to customers"; Fin does	source
Plan	Not priced yet (private beta)	Requires a paid Pro add-on; US, EU and AU workspaces	source

Last verified 2026-10-11 against Fin Operator's public pages, linked in each row.

FAQ

Is Stagewright’s Intercom integration live? It’s built against Intercom’s documented API and tested against mocks: it reads articles, collections and conversations, and writes articles back as drafts. It hasn’t run against a live Intercom workspace yet; we’re proving it with the first teams in the private beta.

Does Stagewright build a chatbot? No. Fin, Zendesk’s AI and Productlane’s AI answer from your articles. We make the articles match the product.

What if an article covers a flow no walkthrough records? It’s listed as ○ not checked. Fin Operator’s text updates still apply to it.