Embed the demo agent inside the page, not on top of it

Place a live, guided demo in the flow of a landing page, campaign, help article, or product surface. It opens on that page's promise and guides the workflow right there.

Sign Up
How the embed behaves

A demo that is part of the page

  1. 1

    Sits in the flow of the content

    You choose the spot: under the hero, beside a feature, inside an article. Readers reach it as they read.

  2. 2

    Opens on the page's own promise

    The page has already narrowed the audience and the topic, so the first question can be specific from the start.

  3. 3

    Guides the workflow in place

    The answer and the product moment appear inside the block. The visitor never leaves the page they came for.

Website launcher or embedded

Which one do you need?

Both run the same demo agent. They differ in where it lives and who starts the conversation.

Website demo agent

Where it sits

A launcher at the bottom of every page of your site.

Who starts it

The visitor, whenever curiosity strikes.

What it knows up front

Which page it was opened from. It asks about role and goal, then adapts.

How you roll it out

One launcher for the whole site.

Best for

Home, product, feature and pricing pages, where intent is mixed.

Embedded demo agent

This page
Where it sits

A block inside one page, at the spot you choose.

Who starts it

The page. The agent is part of what they are already reading.

What it knows up front

The page's audience, campaign and promise, so it opens on that topic.

How you roll it out

Placed page by page, framed for each one.

Best for

Landing pages, campaigns, launches, help content and product surfaces, where the question is already narrow.

You are looking at it.

You can run both: the launcher across the site and an embed on the pages that carry a specific campaign. Sending a demo by email instead? See Inkly for outbound.

Where it belongs

Add product discovery where the question already has context

Use an embedded demo agent when the surrounding page has already narrowed the audience, problem, or workflow worth exploring.

Landing pages

Place product proof beside the promise so a visitor can explore the workflow while the message is still fresh.

Campaign and launch pages

Turn a release, event, or paid campaign into a focused product conversation built around that exact story.

Help content

Let readers move from an explanation to guided practice without leaving the article or documentation path.

Product surfaces

Add an on-demand guide where users encounter a new workflow, decision, or moment of friction.

Same agent underneath

Wherever you put it, the demo agent is the same

Answers from approved knowledge

Your team decides what the agent can draw on and reviews it before launch.

How Inkly works

Guides the real product

It walks the visitor through the workflow instead of describing it.

See the setup

Hands sales the context

What the buyer asked, what they explored and what still needs an answer.

Buyer intelligence

FAQ

Questions about embedded AI demos

What to know about placing a conversational product experience inside the pages and surfaces your audience already uses.

An embedded AI demo agent is a conversational, guided product experience placed directly inside a page or product surface. Visitors can ask questions and explore relevant workflows without first opening a separate tour or scheduling a presentation.

The embedded demo agent is a block you place inside one page, so it is part of that page's content and opens on that page's topic. The website demo agent is a launcher that sits at the bottom of every page and opens when the visitor clicks it. Both run the same agent, and you can use both.

A static tour asks every visitor to follow the same sequence. Inkly can begin from the surrounding page, learn what the visitor is evaluating, answer follow-up questions, and guide them toward the product moments that match that context.

Common placements include landing pages, campaign and launch pages, help content, documentation, and product surfaces. The best placement is usually where the visitor already has a specific question or outcome in mind.

Yes. The opening prompt, product story, and next step can reflect the page's audience and intent while drawing from the same approved product knowledge.

The session can reveal the questions a visitor asked, the workflows they explored, the outcomes they cared about, and the context needed for a more relevant follow-up.

No. The same grounded demo agent can support multiple placements. Each page can frame the conversation around a different goal while the underlying product knowledge and reviewed guidance stay consistent.

Bring the product into the page

Let buyers explore while their interest is still active

Turn a high-intent page into a guided product conversation—and give your team the context to continue it well.

Talk to sales
Speaking

Can I see how account routing works?

Yes. I can guide you through the routing workflow here, then adapt the explanation to the signals your team already uses.

Show me the workflow.