The demo agent that follows visitors across your site

One launcher sits at the bottom of every page, out of the way until a visitor wants it. One click opens a live, guided demo on the page they are on.

Sign Up
How the launcher behaves

One launcher, within reach on every page

  1. 1

    Tucked away until it is wanted

    A small launcher sits at the bottom of the page. It does not cover your content or change your layout.

  2. 2

    Follows the visitor

    It stays in the same place as they scroll and as they move from page to page, so it is there whenever the question comes up.

  3. 3

    Opens on the page they are on

    No form, no redirect and no separate demo page. One click and the demo starts right there.

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

This page
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.

You are looking at it.

Embedded demo agent

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 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

The pages where the launcher earns its place

Product and feature pages

Turn claims into product proof

Go straight from a feature promise to the workflow behind it.

Campaign landing pages

Continue the story after the click

Open on the campaign message, then show the product instead of a gated asset.

Pricing and high-intent pages

Resolve questions while intent is high

Answer fit questions, then offer a call when the buyer wants one.

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 website demo agents

What teams ask before putting one on a live page.

It is a product conversation visitors can open from your site. It asks what they want to accomplish, answers their questions, and walks them through the workflows that match.

A chatbot answers in a message window. Inkly drives the product while it talks, so the visitor sees the workflow instead of reading about it.

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

Start where product interest is strongest: home, product and feature pages, solutions, pricing, and campaign pages. The opening question can match the page it sits on.

Yes. The agent asks about role and goal, then adjusts the path, so different buyers reach different proof points from the same page.

The questions a visitor asked, the product areas they explored, and whether they booked. Sales opens the follow-up already knowing what matters.

No. It gives visitors something useful before they book, and the ones who are ready still move into your sales process.

It runs on a controlled demo environment and answers only from product knowledge your team approves. You review the story as the product changes.

Start with your highest-intent page

Give website visitors a product conversation worth continuing

Let buyers see the product while their interest is fresh, and give your team the context to follow up.

Talk to sales
Speaking

Can I explore the product from this page?

Yes. Tell me what you are evaluating and I'll show you the workflows that match.

Show me account signals.