August 19, 2026

Intercom's article editor is deliberately constrained -- it is designed for support content rather than arbitrary web pages, and that limits what you can embed.
The more interesting point is that help articles are only one of several places Intercom lets you put a demo, and usually not the most valuable one.
Check what your workspace's editor allows for embedded content, since capabilities differ between plans and change over time. Where a live embed is not available, an image linked to the demo is the dependable pattern.
Use a screenshot of the step that matters, not a generic cover. A reader scanning a help article should be able to tell what the demo shows without opening it.
When a support agent answers "how do I set up X", a demo link answers it more completely than a paragraph and takes less agent time than writing one out.
Saved replies containing demo links turn your demo library into support infrastructure. This is usually where demos pay for themselves fastest in a support context.
The point of a demo in support is fewer conversations about the same thing. Watch whether the tickets containing that question fall after you publish it.
That number is far more convincing internally than demo view counts, and it is the one that justifies keeping the demos current.
Click through it — the same kind of demo you can record of your own product.
Record your first interactive demo free.
Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.
Start free →