# Enterprise
Source: https://docs.inklyai.dev/account/enterprise

Advanced demo modes, beta developer workflows, and a fractional solutions engineer.

Enterprise adds advanced demo modes and hands-on support for teams with more complex products.

## Product clone

Inkly captures your interface as HTML. The result looks and behaves like your product but stays separate from the backend.

The agent can drive the demo. The visitor can also click through the interface. If they move away from the planned path, the agent follows and continues from the new screen.

<CardGroup>
  <Card title="Shared control" icon="hand-pointer">
    The agent guides while the visitor explores.
  </Card>

  <Card title="Sharp text" icon="text-height">
    Text renders natively and the page reflows on smaller screens.
  </Card>

  <Card title="Stable targets" icon="location-crosshairs">
    Highlights stay attached to the right interface element when the layout changes.
  </Card>

  <Card title="Safe product data" icon="shield">
    The clone does not connect to your live backend.
  </Card>
</CardGroup>

Use a product clone when free exploration or exact interface fidelity matters.

## Demo against your real product

Inkly can run against a live instance of your product instead of a capture. The agent and the visitor can both interact with the real interface while Inkly keeps the conversation going.

This mode is configured for your product. Talk to us about access, the environment, and the workflows you want to demo.

## CLI and GitHub workflows

Enterprise teams can request beta access to the Inkly CLI and [GitHub connection](/build/connect-github).

These options let developers and coding agents work from the same demo source as the Inkly editor. They are still in private beta, so we help configure access and the initial workflow.

## Your fractional SE

Choose a done-for-you engagement when you want Inkly to build and maintain the demo agent with your team.

Your fractional solutions engineer turns product changes, sales feedback, and buyer questions into updated screens, storylines, knowledge, qualification, and outcomes. You keep the product expertise. We keep the demo current.

## What else Enterprise includes

* Everything in Pro
* A contract credit allowance
* Beta access to the CLI and GitHub connection
* A done-for-you fractional SE option
* Integrations and priority support

## Get access

Enterprise is not self-serve. Open **Settings → Plan & usage** and contact us from there.

## Next

<CardGroup>
  <Card title="The editor" icon="pen-ruler" href="/build/the-editor">
    Add and organize the screens in your demo.
  </Card>

  <Card title="Plans and credits" icon="credit-card" href="/account/plans-and-credits">
    Compare Free, Pro, and Enterprise.
  </Card>
</CardGroup>


# Plans and credits
Source: https://docs.inklyai.dev/account/plans-and-credits

What is free, what a credit is, what unlocking a visitor buys you, and what happens when you run out.

Inkly is priced around two units, and everything else follows from them.

<CardGroup>
  <Card title="Demo visitors" icon="users">
    People who watch a demo in a billing period. **Text chat with every one of them is never gated.**
  </Card>

  <Card title="Agent credits" icon="bolt">
    The paid unit. One monthly balance that funds unlocking visitors *and* the work of building demos.
  </Card>
</CardGroup>

## The plans

|                                                        | Free   | Pro       | Enterprise |
| ------------------------------------------------------ | ------ | --------- | ---------- |
| Demo agent embedded on your site                       | ✓      | ✓         | ✓          |
| Text chat with every visitor                           | ✓      | ✓         | ✓          |
| Anonymous sessions and transcripts                     | ✓      | ✓         | ✓          |
| Transcript and detail for an *identified* visitor      | —      | ✓         | ✓          |
| Unique visitor emails per period                       | Capped | Unlimited | Unlimited  |
| Agent credits per month                                | —      | Included  | Contract   |
| Interactive voice                                      | —      | ✓         | ✓          |
| Personalized links                                     | —      | ✓         | ✓          |
| Contact details and intent                             | —      | ✓         | ✓          |
| [HTML product clone](/account/enterprise)              | —      | —         | ✓          |
| [Demos against your real product](/account/enterprise) | —      | —         | ✓          |
| CLI and GitHub workflows (beta)                        | —      | —         | By request |
| Fractional SE option                                   | —      | —         | ✓          |

Free and Pro are self-serve. Enterprise is sold by a person.

Current prices, credit allowances, and the yearly discount are on the pricing page in the app — that page is authoritative, and paying yearly costs less than twelve months.

## How viewer credits work

Interactive voice is funded through a viewer unlock. The first unlocked visit from a unique email costs **10 credits** for the billing period.

The charge is per person, not per session or demo. If the same email returns or opens another demo during that period, it costs nothing extra.

That unlock gives the visitor interactive voice. It also gives you their full session history, including transcripts, qualification, and buyer intent.

## When you run out

Your demos stay live and fall back to the chat-based agent.

* Text chat continues to work.
* Sessions and aggregate analytics continue to be recorded.
* Qualification and buyer intent continue to be saved.
* Identified visitor details stay locked.

You can later spend **10 credits** from **Sessions** or **People** to unlock that person and reveal their saved data. Repeat unlocks for the same email and billing period cost nothing.

Inkly AI also uses credits when it reads, writes, or generates material while building your demo. Both activities spend from the same balance.

<Note>
  Periods reset on your own billing boundary, not on the first of the month. When the window advances, usage in the new window starts empty.
</Note>

## Trials

Pro has a trial with its own credit grant, so you can put voice and personalized links in front of real visitors before deciding.

## Where to look

**Settings → Plan & usage** shows your balance, what has been spent this period, and what it went on.

## Next

<CardGroup>
  <Card title="Enterprise" icon="building" href="/account/enterprise">
    HTML product clones and demos driven against your real product.
  </Card>

  <Card title="People" icon="users" href="/measure/people">
    Unlocking in practice.
  </Card>
</CardGroup>


# Account settings
Source: https://docs.inklyai.dev/account/settings

Your plan, API keys, installation, integrations, and account activity.

Everything under **Settings** in the sidebar.

## Account

Your profile and sign-in. Inkly hosts your workspace — there is nothing to provision and no infrastructure to choose.

## Plan & usage

Your current plan, your credit balance, what has been spent this period, and what it went on. See [Plans and credits](/account/plans-and-credits).

## API keys

Tokens that let something outside the browser act as your account — today, the [Chrome extension](/build/chrome-extension).

<Warning>
  Treat a key like a password. It grants access to your account. Delete a key you are not using.
</Warning>

## Install

The [widget](/ship/install-the-widget) snippet, the popup variant, and your demo's share link — with a live preview of each. Copy from here or from the **Publish** menu in the editor.

## Domain setup

Request a subdomain you own for your hosted demo. See [Custom domain](/ship/custom-domain).

## Integrations

Slack, HubSpot, Pipedrive, and the rest.

<Note>
  This page is a set of **asks**, not a set of features — no integration is connected today. Clicking one starts a conversation and records that you wanted it, which is how the build order gets decided. Analytics destinations are separate: they live under the **Connectors** tab in [Analytics](/measure/analytics#connectors).
</Note>

## Activity

The change history of your demo — who changed what, and when. Useful when a demo starts behaving differently and you want to know what moved.

## Next

<CardGroup>
  <Card title="Chrome extension" icon="chrome" href="/build/chrome-extension">
    Record a demo from your own browser.
  </Card>

  <Card title="Plans and credits" icon="credit-card" href="/account/plans-and-credits">
    What your balance is spent on.
  </Card>
</CardGroup>


# Annotations and storylines
Source: https://docs.inklyai.dev/build/annotations-and-storylines

Show the guide what matters and put those moments in order.

An **annotation** tells the guide where to point and why it matters. A **storyline** puts annotations in an order the guide can follow.

<Note>
  **Inkly AI can write these for you.** Click **Inkly AI** and try: “Review my screens. Add annotations for the strongest product moments, explain why each matters to a buyer, and build a concise storyline around them.”
</Note>

## Add an annotation

Open **Assets**, select a screen, and add an annotation.

| Setting        | What to add                                                                                    |
| -------------- | ---------------------------------------------------------------------------------------------- |
| **Target**     | Select the product area the guide should point to. Choose a region large enough to notice.     |
| **Kind**       | Use **Showcase** to point and explain. Use **Action** when the guide should click.             |
| **AI context** | Explain what the feature does and why the buyer should care. The visitor never sees this text. |

Good context sounds like a briefing, not a tooltip:

> Dragging a bar reschedules the job without opening a form. Dispatchers do this dozens of times each morning, so this removes repetitive data entry.

On an image, **Action** shows a click without changing screens. Clickable captured pages are an [Enterprise capability](/account/enterprise).

## Build a storyline

Open **Storyline**, then:

1. Give the storyline a goal from the visitor's perspective.
2. Add annotations in the order that best explains the value.
3. Open **Preview** and test the flow.

Keep each storyline focused:

* Use six to ten annotations.
* Start with the problem, not your navigation.
* Explain one idea at a time.
* End where your [next step](/build/outcomes) makes sense.

Create another storyline only when a different audience needs a different argument.


# Chrome extension
Source: https://docs.inklyai.dev/build/chrome-extension

Capture product screens from a browser where you are already signed in.

Use the Inkly Chrome extension when the product flow is behind a login or cannot be built from your public site.

## Connect it

Install the extension from the link in Inkly, then connect it to your workspace. Click **Re-check** if Inkly does not detect it.

## Record a flow

<Steps>
  <Step title="Open the first screen">
    Sign in and navigate to where the demo should begin.
  </Step>

  <Step title="Start recording">
    The extension shows each captured screen as you click.
  </Step>

  <Step title="Show the value">
    Record five to eight meaningful clicks. End on the result.
  </Step>

  <Step title="Review in Inkly">
    Stop the recording and open the result in the editor.
  </Step>
</Steps>

The extension captures screenshots and video. Captured pages that visitors can click are an [Enterprise capability](/account/enterprise).

If an upload fails, click **Try again**. The extension keeps the recording until you start another one.


# Connect GitHub
Source: https://docs.inklyai.dev/build/connect-github

Keep your demo source in a repository your team controls.

Connect Inkly to GitHub when your team wants demos to follow the same review and collaboration process as the product.

<Note>
  **GitHub connection is in private beta.** Contact us from **Settings → Plan & usage** to request access.
</Note>

## What it gives you

* A repository and branch your team controls
* Version history for published demo changes
* A shared source for Inkly, developers, and coding agents
* A path to the Inkly CLI for Enterprise teams

Inkly still provides the visual editor and Inkly AI. GitHub adds another way to review and manage the same demo rather than creating a separate copy.

## Before you connect

Choose the GitHub organization, repository, and branch you want Inkly to use. If you already have a demo in Inkly, tell us whether you want that content moved into the repository.

We will guide the initial connection during the beta.


# Build from a URL
Source: https://docs.inklyai.dev/build/from-a-url

Ask Inkly AI to build the first version of your demo agent.

After you sign up, open [Inkly](https://app.inklyai.dev) and click **Inkly AI**. Give it your product URL and ask it to build your demo agent.

Inkly AI reads the public site to understand what you sell, who it is for, and which product moments support that story. It shows you its plan before it edits the draft.

## Give it useful source material

Your main product URL is enough to start. Add more context when you have it:

| Source                               | What it improves                  |
| ------------------------------------ | --------------------------------- |
| Product and feature pages            | The screens and storyline         |
| Pricing, security, and documentation | Answers to buyer questions        |
| Screenshots or screen recordings     | Product areas that are not public |
| A PDF or slide deck                  | Positioning and sales context     |

Tell Inkly AI which audience you care about and what action you want them to take. This helps it build an argument instead of a general product tour.

## What Inkly AI builds

The first draft includes:

* product screens
* annotations that explain why each moment matters
* a storyline that orders those moments
* company and product knowledge for buyer questions
* a call to action for the next step

Nothing goes live until you review and publish it.

## Review the first draft

Check three things:

1. **Screens:** Do they show the real product and the right workflow?
2. **Positioning:** Does the guide explain why customers buy?
3. **Storyline:** Does it lead with the strongest product moments?
4. **Answers:** Can it handle pricing, security, and common objections?
5. **Outcome:** Is there a clear next step for an interested buyer?

Ask Inkly AI to revise the draft in the same conversation. For example: “Replace the opening screen, make the storyline specific to sales leaders, and add our security page to the knowledge base.”

## Products behind a login

Inkly AI can only read public pages from a URL. If the product is behind a login, attach screenshots or use the [Chrome extension](/build/chrome-extension) to capture it from your signed-in browser.

Building and revising with Inkly AI uses [agent credits](/account/plans-and-credits).


# Knowledge
Source: https://docs.inklyai.dev/build/knowledge

Give the guide the facts it needs to answer buyer questions.

Open **Agent → Settings → Knowledge base**.

<Note>
  **Inkly AI can write this for you.** Click **Inkly AI** and try: “Read our pricing, security, and documentation pages. Add focused knowledge for pricing, security, integrations, and common objections. State our limits clearly.”
</Note>

## Company information

Add the facts that should shape every conversation:

* what you sell and who buys it
* why customers choose it
* where it is not a fit
* how the guide should speak

Write this like a briefing for a new teammate.

## Knowledge documents

| Option         | Use it for                                                                                               |
| -------------- | -------------------------------------------------------------------------------------------------------- |
| **From a URL** | Public pages such as pricing, security, documentation, or a changelog. Ask Inkly AI to capture the page. |
| **Markdown**   | Information you want to write directly. Keep each document focused on one subject.                       |

Use buyer language, answer the question first, and state limits clearly.

Open **Preview** and ask the hardest questions your team receives. Improve the knowledge when the guide hedges or guesses.


# Outcomes
Source: https://docs.inklyai.dev/build/outcomes

Give each visitor a clear next step.

Open **Agent → Settings → Outcomes**.

<Note>
  **Inkly AI can set this up for you.** Click **Inkly AI** and try: “Set our primary CTA to Start a trial at \[URL]. Offer a meeting only when a visitor mentions a timeline, budget, or implementation.”
</Note>

## Primary CTA

The primary CTA stays available throughout the demo. Add:

* **Label:** what the button says
* **Destination:** the page or email address it opens
* **Goal:** what the action means in analytics

The same CTA appears in the shareable link and widget.

## Actions

Actions appear when they fit the conversation.

| Action                 | Use it for                                                  |
| ---------------------- | ----------------------------------------------------------- |
| **Open a link**        | Pricing, documentation, signup, or another relevant page.   |
| **Schedule a meeting** | Your Calendly, Cal.com, or another embeddable booking page. |

Use **When to offer** to name a clear signal. For example: “Offer this when they mention a timeline, budget, or implementation plan.”

Test the signal in **Preview** and confirm that the action opens the right destination.


# The editor
Source: https://docs.inklyai.dev/build/the-editor

Edit what the agent shows, knows, and tries to achieve.

Open **Agent** in the sidebar to edit your demo agent.

<CardGroup>
  <Card title="Assets" icon="images">
    Screens and their annotations.
  </Card>

  <Card title="Storyline" icon="route">
    The product moments the guide presents.
  </Card>

  <Card title="Settings" icon="sliders">
    Knowledge, qualification, and outcomes.
  </Card>
</CardGroup>

## Assets

Select a screen to change its title, description, image, or annotations. Drag screens to reorder them.

| Screen            | Best for                                                                                      |
| ----------------- | --------------------------------------------------------------------------------------------- |
| **Image**         | Most product screens                                                                          |
| **Video**         | Short moments where motion matters                                                            |
| **Captured page** | A product experience the guide and visitor can both click ([Enterprise](/account/enterprise)) |

Replace an outdated image instead of rebuilding the screen. Its annotations and storyline position stay in place.

## Storyline

Choose the moments the guide should present and drag them into order. Select a moment to edit its target or **AI context**.

See [Annotations and storylines](/build/annotations-and-storylines).

## Settings

Use **Settings** to edit:

* [Knowledge](/build/knowledge)
* [Outcomes](/build/outcomes)
* [What the agent collects](/build/what-the-agent-collects)

## Preview and publish

Click **Preview** to test the demo as a visitor. Use the gear to change its name and brand.

Your edits stay in a draft until you click **Publish**. Existing links and widgets update without changing their URL.


# What the agent collects
Source: https://docs.inklyai.dev/build/what-the-agent-collects

Decide what the agent learns from each visit, during the conversation and afterwards.

Open **Agent → Settings → Data to Collect**.

<Note>
  **Inkly AI can design this for you.** Click **Inkly AI** and try: “Ask about the visitor's role and current workflow when it feels natural. After each session, deduce buying intent, buying stage, main objection, and pain point using clear rules.”
</Note>

## During the conversation

Add two or three questions the guide should ask naturally.

| Question                               | When to ask                                                             |
| -------------------------------------- | ----------------------------------------------------------------------- |
| What are you trying to improve?        | After they show interest in a workflow.                                 |
| How large is your team?                | When rollout or pricing becomes relevant.                               |
| What do you use today?                 | When migration or comparison comes up.                                  |
| What are you trying to get done today? | For a customer, first thing, so the agent can take them straight there. |

Use **Description** to tell the guide when and how to ask. Make a question required only when the answer is essential.

## After the conversation

Use deductions for things the guide should never ask directly.

| Result                      | Rule                                                                       |
| --------------------------- | -------------------------------------------------------------------------- |
| Buying intent               | High when they mention a timeline, budget, procurement, or next step.      |
| Buying stage                | Separate casual research from evaluation or procurement.                   |
| Main objection              | Capture their strongest concern.                                           |
| Pain point                  | Capture the problem that started the evaluation.                           |
| Where they got stuck        | The step or screen they could not get past, or asked about more than once. |
| Finished what they came for | True when they reached the end of the workflow they described.             |

Write rules another person could apply. Results appear in [Sessions](/measure/sessions) and [People](/measure/people), alongside the conversation that produced them.


# Inkly Docs
Source: https://docs.inklyai.dev/index

Inkly is a demo agent: an AI that shows people your product and answers their questions, live.

Inkly is a live demo agent for prospects and customers. Prospects try your product instead of booking a call. New customers learn it instead of waiting for onboarding. An agent guides both, 24/7.

<CardGroup>
  <Card title="For prospects" icon="handshake" href="/use-cases/sales-and-enablement">
    On your site and in outbound links: they see the product, ask anything, and you learn what they asked.
  </Card>

  <Card title="For customers" icon="graduation-cap" href="/use-cases/product-onboarding">
    After the sale: first workflows, how-to questions, and where people got stuck.
  </Card>
</CardGroup>

## Start here

<CardGroup>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Build, review, publish, and share your first demo.
  </Card>

  <Card title="What is Inkly?" icon="sparkles" href="/what-is-inkly">
    See how the agent demos your product and stays grounded.
  </Card>

  <Card title="The editor" icon="pen-ruler" href="/build/the-editor">
    Choose what the agent can show, say, and do.
  </Card>

  <Card title="Install and share" icon="code" href="/ship/install-the-widget">
    Add Inkly to your site or send a shareable link.
  </Card>
</CardGroup>

## Find what you need

<CardGroup>
  <Card title="Build" icon="hammer" href="/build/from-a-url">
    Create the demo and shape the agent.
  </Card>

  <Card title="Ship" icon="paper-plane" href="/ship/shareable-link">
    Publish, embed, or share it.
  </Card>

  <Card title="Measure" icon="chart-line" href="/measure/analytics">
    Review what people asked, where they went, and where they got stuck.
  </Card>
</CardGroup>


# Analytics
Source: https://docs.inklyai.dev/measure/analytics

Who is exploring your demo agent, what held their attention, and where they came from.

Open **Analytics** in the sidebar. It answers the shape questions — how much traffic, from where, holding attention on what — and hands off to [Sessions](/measure/sessions) for the individual stories.

<Note>
  Aggregate analytics continue when your credit balance reaches zero. Identified visitor details and collected fields stay saved but remain locked until you unlock that person.
</Note>

## Overview

| Panel                         | What it tells you                                                                                        |
| ----------------------------- | -------------------------------------------------------------------------------------------------------- |
| **Sessions over time**        | Volume, over a range you pick. The shape of a launch, a campaign, or a quiet week.                       |
| **Drawing the most interest** | Which screens held attention. Usually the fastest way to learn what your product's real hook is.         |
| **Top referrers**             | Where visitors came from before they opened the demo — captured on your page, not inside the demo frame. |
| **Top countries**             | Where they were.                                                                                         |

Filter by date range and by source.

<Note>
  "Drawing the most interest" is the panel worth checking weekly. It is measured from real attention rather than from the order you authored, so it regularly disagrees with the [storyline](/build/annotations-and-storylines) you wrote. That disagreement is the useful part.
</Note>

## What a session is

One visit to one of your demos. It starts when someone opens the demo and ends when they leave.

Duration is measured to the visitor's **last interaction**, not to the last thing the page did. A demo left open in a background tab and closed 45 minutes later is not a 45-minute session.

## What a session shows

Open a session to see:

| Detail                 | What it tells you                                               |
| ---------------------- | --------------------------------------------------------------- |
| Transcript             | What the visitor asked and how the guide answered               |
| Screens viewed         | How much of the product they explored                           |
| Questions asked        | How active the conversation was                                 |
| Outcomes               | Whether they clicked a CTA, shared details, or booked a meeting |
| Source and attribution | Where they came from and which campaign brought them in         |
| Device and location    | The context of the visit                                        |

## Connectors

The **Connectors** tab lists the analytics destinations we integrate with on request. Nothing is forwarded today — **Connect** starts a conversation to turn one on.

## Attribution

When the demo is opened through the [widget](/ship/install-the-widget), attribution is captured from **your page** rather than from inside the demo: the landing URL, the real referrer, every standard UTM parameter, and common advertising click IDs. The first snapshot is kept for the session, so someone who browses your site before opening the demo is still attributed to how they arrived.

## Privacy

Visitor IP addresses are never stored. The address is seen only during the request for abuse rate limiting. The session keeps the country resolved by the network.

## Next

<CardGroup>
  <Card title="Sessions" icon="play" href="/measure/sessions">
    Transcript and timeline, one visit at a time.
  </Card>

  <Card title="People" icon="users" href="/measure/people">
    The visitors you can put a name to.
  </Card>
</CardGroup>


# People
Source: https://docs.inklyai.dev/measure/people

The visitors you can put a name to — every session they had, everything they asked, and what the agent worked out about them.

**People** is the list of visitors you can identify. Where [Sessions](/measure/sessions) is one visit at a time, People is one *person* at a time — every visit they have made, in one place.

A visitor becomes a person when you have their email, either from the demo or from a [personalized link](/ship/personalized-links).

## What a person shows

|                      |                                                                                                                                        |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Identity**         | Email, company (from the domain), and anything you authored on them as a contact.                                                      |
| **Sessions**         | Every visit they have made, with duration and how far they got.                                                                        |
| **Questions**        | Everything they asked, across all visits.                                                                                              |
| **Collected fields** | What the guide asked during a session, and what was deduced afterwards. See [What the agent collects](/build/what-the-agent-collects). |

The second visit is the interesting one. Someone who comes back to a demo, alone, without being prompted, is telling you something no form field will.

## Unlocking

Identity and detail are gated per person. An anonymous session is always recorded and readable.

Unlocking a person costs **10 credits** and reveals every saved session, transcript, collected answer, and deduced field for that email.

You can unlock someone after their visit, or unlock several people at once. The charge applies once per email and billing period. Repeat visits cost nothing extra.

See [Plans and credits](/account/plans-and-credits).

## Limits by plan

**Free** caps how many unique visitor emails you collect in a period. Demos keep running past the cap — basic text chat is never gated — but new addresses stop being recorded.

**Pro** removes that cap and grants credits for unlocking. Unlimited addresses collected; a budget for how many you open.

## Using it

<CardGroup>
  <Card title="Follow up with the transcript" icon="reply">
    Open the person, read what they asked, and answer *that*. It converts better than any sequence, because you are answering a question they actually asked.
  </Card>

  <Card title="Watch for return visits" icon="rotate">
    A second unprompted visit is the strongest buying signal in the product.
  </Card>

  <Card title="Check your deductions" icon="magnifying-glass">
    Compare a few deduced fields against their transcripts. If they disagree, your field <a href="/build/what-the-agent-collects#after-what-is-deduced">description</a> needs to be a sharper rule.
  </Card>

  <Card title="Personalize the next one" icon="user-tag">
    Turn a good session into a <a href="/ship/personalized-links">contact</a> and send them a link the guide is briefed for.
  </Card>
</CardGroup>

## Next

<CardGroup>
  <Card title="Sessions" icon="play" href="/measure/sessions">
    Transcript and timeline for any single visit.
  </Card>

  <Card title="Plans and credits" icon="credit-card" href="/account/plans-and-credits">
    What an unlock costs and what it includes.
  </Card>
</CardGroup>


# Sessions
Source: https://docs.inklyai.dev/measure/sessions

Read what happened on any visit to your demo — the conversation, the path, and what the agent worked out.

**Sessions** is the list of individual visits. It is the most useful screen in the product, and the one people underuse.

A chart tells you that a screen loses people. A transcript tells you why.

## The list

The list shows **identified** visits, newest first — who it was, how long they stayed, and how far they got. Someone who left at the welcome screen without an email is still recorded and still counted in [Analytics](/measure/analytics), but has nothing you can act on, so they are not listed here.

Search across email, company, and country, and filter by source (your live demo versus previews) and by date range.

Duration is measured to the visitor's **last interaction**, not to the last thing the page did — so a demo left open in a background tab and closed 45 minutes later is not a 45-minute session.

## The transcript

The full conversation: every turn the visitor took and every answer the guide gave, in order, marked with which were spoken.

This is your most direct source of product feedback. The questions people ask a demo agent are the questions they were too polite, or too early, to ask a salesperson.

<Note>
  Read the first five transcripts after any change, end to end, without skimming. It consistently beats reasoning about the funnel from aggregate numbers.
</Note>

Read for four things:

<CardGroup>
  <Card title="Questions the guide fumbled" icon="circle-question">
    Each one is a missing [knowledge doc](/build/knowledge), or a missing section in one.
  </Card>

  <Card title="Questions you did not expect" icon="lightbulb">
    Objections you are not handling on your website either.
  </Card>

  <Card title="Where they interrupted" icon="hand">
    The beat they cut off is the beat that was not landing.
  </Card>

  <Card title="Where they went off-path" icon="route">
    What they went looking for is what they actually came for.
  </Card>
</CardGroup>

## Session details

Alongside the transcript, you can see the visit's duration, screens viewed, questions asked, outcomes, source, campaign, device, and location. See [what a session shows](/measure/analytics#what-a-session-shows).

## Analysis

Sessions carry the fields the guide gathered — what it asked during the visit, and what was deduced from the transcript afterwards. Both are shown against the conversation they came from, so a value you disagree with can be checked against what was actually said.

Configure what gets collected under [What the agent collects](/build/what-the-agent-collects).

## Locked sessions

When credits run out, the demo still records the session and the fields you asked the agent to collect. An identified visitor's email, transcript, and analysis remain locked.

Click **Unlock with 10 credits** to reveal every saved session for that email. The charge applies once per billing period, so repeat visits cost nothing extra. You can also unlock several visitors at once.

On the Free plan, every identified session is locked. See [Plans and credits](/account/plans-and-credits).

## Next

<CardGroup>
  <Card title="People" icon="users" href="/measure/people">
    Sessions grouped by the person who had them.
  </Card>

  <Card title="Knowledge" icon="file-lines" href="/build/knowledge">
    Where the answers to fumbled questions go.
  </Card>
</CardGroup>


# Quickstart
Source: https://docs.inklyai.dev/quickstart

Use Inkly AI to build, review, publish, and share your first demo agent.

Inkly AI builds your first demo with you inside [app.inklyai.dev](https://app.inklyai.dev).

<Steps>
  <Step title="Sign up with your product site">
    Create your account, name the project, and enter the public URL for your product.
  </Step>

  <Step title="Start the build with Inkly AI">
    After signup, **Home** opens the **Get onboarded** dialog with **Your product** already filled in.

    Add any useful sources you have. You can include product or pricing links, screenshots, a PDF, or a slide deck. These are optional.

    Click **Build Demo Agent**. Inkly AI opens in the right panel and starts the build.
  </Step>

  <Step title="Work with Inkly AI">
    Inkly AI researches your product and checks its plan with you before it edits the draft. Answer its questions when something is unclear.

    Keep using the conversation to request changes. Ask it to replace a screen, sharpen the product story, add knowledge, or change what the agent collects. You can reopen the panel from **Inkly AI** in the app header.
  </Step>

  <Step title="Preview the draft">
    Open **Agent** in the sidebar, then click **Preview**. Check three things:

    1. The screens show the real product.
    2. The agent explains it in your words.
    3. The next action is clear.

    Make edits in the editor or ask Inkly AI to make them. Nothing changes for visitors until you publish.
  </Step>

  <Step title="Publish and share">
    Use **Publish** in the editor. Then open **Settings → Install** to add the widget to your site, use your own button, or copy the shareable link.

    See [Install the widget](/ship/install-the-widget) for the current code snippet.
  </Step>

  <Step title="Read the first sessions">
    Open **Sessions** after people visit. Read their questions and paths to see what interested them, where the agent was unclear, and who may be qualified.
  </Step>
</Steps>

## If the product is behind a login

Inkly AI can only read public pages. Use the [Chrome extension](/build/chrome-extension) to capture screens from a browser session where you are already signed in. Add those screens to the draft, then ask Inkly AI to work them into the demo.

## Next

<CardGroup>
  <Card title="Build from a URL" icon="wand-magic-sparkles" href="/build/from-a-url">
    See what Inkly AI builds and what to review.
  </Card>

  <Card title="The editor" icon="pen-ruler" href="/build/the-editor">
    Edit what the agent shows and says.
  </Card>

  <Card title="Install the widget" icon="code" href="/ship/install-the-widget">
    Add the demo to your site.
  </Card>

  <Card title="Sessions" icon="messages" href="/measure/sessions">
    Review each visit.
  </Card>
</CardGroup>


# Custom domain
Source: https://docs.inklyai.dev/ship/custom-domain

Serve your demo from a subdomain you own, such as demos.yourcompany.com.

By default your demo lives at an Inkly address. You can request that it be served from a subdomain you own instead — `demos.yourcompany.com` — so the link you send matches everything else you send.

<Warning>
  Custom domains are **not self-serve yet**. Submit the request and the Inkly team confirms the DNS details with you before the domain is assigned.
</Warning>

## Request one

Open **Settings → Domain setup**, enter the subdomain you want to use, and submit.

Use a subdomain you control and are not already serving from — `demos.`, `try.`, and `product.` are the common choices. An apex domain is not supported.

## In the meantime

The [widget](/ship/install-the-widget) already runs on your domain. It mounts on your own page, renders inside your page's document, and carries your brand — so for the embedded case, a visitor never sees an Inkly URL at all.

A custom domain applies to your [shareable link](/ship/shareable-link), including links used in emails, sequences, and proposals.

## What does not change

Everything else works the same. Your demo's identity, its sessions, and its analytics are unaffected, and links already sent on the Inkly address keep working.

## Next

<CardGroup>
  <Card title="Shareable link" icon="link" href="/ship/shareable-link">
    Send your demo anywhere.
  </Card>

  <Card title="Install the widget" icon="code" href="/ship/install-the-widget">
    Already runs on your own domain.
  </Card>
</CardGroup>


# Install the widget
Source: https://docs.inklyai.dev/ship/install-the-widget

Let visitors open your demo agent without leaving your website.

The widget puts your demo agent at the moment of intent. A visitor can see the product, ask questions, and qualify themselves without leaving the page or waiting for a meeting.

Inkly generates the installation code for your published demo. Copy it from the app and paste it into your site without changing it.

## Choose a placement

<CardGroup>
  <Card title="Widget" icon="circle-dot">
    Adds the Inkly orb to your site. Visitors can open the demo whenever they are ready.
  </Card>

  <Card title="Popup" icon="arrow-pointer">
    Opens the demo from your own button. Use it behind a primary CTA such as “See the product”.
  </Card>
</CardGroup>

## Install it

<Steps>
  <Step title="Publish your demo">
    The install options appear after your first publish.
  </Step>

  <Step title="Open Settings → Install">
    Choose **Widget** or **Popup** and click **Copy**.
  </Step>

  <Step title="Paste the code into your site">
    Add the complete snippet before the closing body tag. Do not remove or edit its Inkly settings.
  </Step>

  <Step title="Test the experience">
    Open the page, start the demo, ask a question, and confirm the session appears in Analytics.
  </Step>
</Steps>

## Replace “Book a demo”

Use **Popup** when you want an existing button to open the product experience.

This gives buyers value before asking for time. The agent can show the relevant workflow, answer objections, qualify the visitor, and offer a meeting when it makes sense.

## What gets measured

Sessions opened through the widget include the conversation, outcomes, and first-touch attribution from your site. Use [Analytics](/measure/analytics) to see which pages and campaigns bring the strongest interest.

## Updates publish automatically

You install the widget once. Publishing a new version updates every page where it appears without another site deployment.

<Note>
  A strict Content Security Policy may block third-party scripts or frames. Contact us if the widget does not load after installation.
</Note>

## Next

<CardGroup>
  <Card title="Shareable link" icon="link" href="/ship/shareable-link">
    Send the same demo without installing anything.
  </Card>

  <Card title="Analytics" icon="chart-line" href="/measure/analytics">
    See where visitors came from and what held their attention.
  </Card>
</CardGroup>


# Personalized links
Source: https://docs.inklyai.dev/ship/personalized-links

Send one prospect a demo that greets them by name and briefs the guide about them — without cloning the demo.

A **contact** is a person, not a demo. Creating one gives you a link that makes your demo personal to them.

One contact works against **every demo you own**, and updating a demo reaches every link you have already sent. There is no per-prospect copy to maintain.

Manage them under **Contacts** in the sidebar.

## What the visitor sees

Deliberately little:

* The welcome screen greets them **by name**.
* If the contact carries an email, the demo **does not ask for one** — you already know who they are.

That is it. The demo is not visibly "customized"; it is simply expecting them.

## What the guide sees

Rather more:

* Their name, email, company, and role.
* **Your private note** — whatever you wrote about them.

The guide folds all of it into how it talks: it can open on the thing you said they care about, use their company as the example, and skip the parts you flagged as irrelevant.

<Warning>
  The private note **never reaches the browser**. It is resolved on the server on every turn and rides the guide's instructions. The page itself only ever receives the name and email.
</Warning>

## Creating one

Open **Contacts** and add a person. What matters:

| Field       | Why                                                                                                                                                        |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**    | What the welcome screen greets them with.                                                                                                                  |
| **Email**   | Where the link is going — and what the automatic company research runs on, so an address here is the difference between a tailored demo and a generic one. |
| **Company** | Only if you would rather state it than have it researched. An authored value always beats a researched one.                                                |
| **Role**    | Helps the guide pitch at the right altitude.                                                                                                               |
| **Note**    | Your private briefing for the guide.                                                                                                                       |

Copy the link it gives you and send it. Creating a contact also kicks off background research on the email's domain, so the guide knows something about their company before they arrive.

## Writing the note

This is the part that matters. The note is a briefing, not a CRM field.

<CodeGroup>
  ```text Good theme={"dark"}
  Evaluating us against ServiceTitan; their contract renews in March. Runs 40
  technicians. Complained on the call that dispatchers spend the first hour of
  every day rebuilding the board. Do not lead with reporting — they said twice
  they do not care about it.
  ```

  ```text Bad theme={"dark"}
  Warm lead, VP Ops, interested in scheduling.
  ```
</CodeGroup>

The second one is a CRM field. It tells the guide nothing it could not guess.

## What it costs

Personalized links are a **Pro** capability. Creating a contact costs nothing: the credits are spent when that person opens the link and the demo unlocks them. See [Plans and credits](/account/plans-and-credits).

## Next

<CardGroup>
  <Card title="People" icon="users" href="/measure/people">
    What happened when they opened it.
  </Card>

  <Card title="Shareable link" icon="link" href="/ship/shareable-link">
    Send the same demo without personalization.
  </Card>
</CardGroup>


# Shareable link
Source: https://docs.inklyai.dev/ship/shareable-link

Send your demo agent anywhere and see what each person asked and where they got stuck.

A shareable link lets someone see your product and ask questions immediately. They do not need to book a call, install anything, or visit your website first.

Use it in outbound, launch campaigns, follow-up emails, proposals, or QR codes.

## Copy your link

<Steps>
  <Step title="Publish your demo">
    Only published changes appear to visitors.
  </Step>

  <Step title="Open Settings → Install">
    Select **Direct link**.
  </Step>

  <Step title="Copy and send">
    Open it once yourself, then use it anywhere you would normally ask someone to book a demo.
  </Step>
</Steps>

## What the visitor gets

The link opens a complete demo agent:

* Your welcome screen and brand
* A guide that shows the product and answers questions
* The questions the agent asks during the conversation
* A relevant next step when the visitor is ready

Every visit appears in [Sessions](/measure/sessions), where you can review the conversation, engagement, and what the agent learned.

## Where it works best

<CardGroup>
  <Card title="Outbound" icon="paper-plane">
    Give a named prospect a product experience before asking for a meeting.
  </Card>

  <Card title="Launches and campaigns" icon="bullhorn">
    Let interested buyers explore while the announcement is still fresh.
  </Card>

  <Card title="Follow-up" icon="reply">
    Send the exact product story discussed on a call.
  </Card>

  <Card title="Events and proposals" icon="qrcode">
    Turn a QR code or proposal into a product conversation.
  </Card>
</CardGroup>

## One link stays current

The address does not change when you edit or rename the demo. Publish an improvement and every link you have already sent shows the new version.

You do not need to redistribute links or ask prospects to open a new one.

## Personalize it for a prospect

Create a [personalized link](/ship/personalized-links) when you know who will open it. The guide greets them by name and starts with the context you provide.

## Use your own domain

A custom domain such as `demos.yourcompany.com` is available on request. See [Custom domain](/ship/custom-domain).

## Next

<CardGroup>
  <Card title="Personalized links" icon="user-tag" href="/ship/personalized-links">
    Brief the guide for one named prospect.
  </Card>

  <Card title="Sessions" icon="play" href="/measure/sessions">
    Review what visitors asked and what they cared about.
  </Card>
</CardGroup>


# Customer success
Source: https://docs.inklyai.dev/use-cases/customer-success

Drive adoption and expansion by showing existing customers what they are not using yet.

Your customers use a fraction of what they pay for. A demo agent shows them the rest, on demand, without booking a call with their CSM.

## The problem it solves

Expansion conversations fail because the customer cannot picture the thing you are describing. A recording of the feature helps; a demo they can explore and interrogate helps far more — and it scales past the accounts a CSM can call.

It also tells you which accounts are interested before you ask.

## Where to put it

<CardGroup>
  <Card title="QBR follow-ups" icon="chart-line">
    A [personalized link](/ship/personalized-links) per account, with the guide briefed on what they said in the review.
  </Card>

  <Card title="Feature announcements" icon="bullhorn">
    "Here is what shipped" as something they can try, not a changelog entry.
  </Card>

  <Card title="Plan upgrade pages" icon="arrow-up">
    Show the tier's capability instead of listing it.
  </Card>

  <Card title="Renewal conversations" icon="rotate">
    A storyline covering everything they are not using yet, sent a month before the date.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Build demos for the under-adopted features">
    Not your whole product — the specific capabilities accounts routinely miss.
  </Step>

  <Step title="Personalize per account">
    Add them under [Contacts](/ship/personalized-links) with a note about their setup. The guide will use their situation as the example.
  </Step>

  <Step title="Configure what the agent deduces">
    An After field like "interest in this feature — low / medium / high" turns every session into a signal. See [What the agent collects](/build/what-the-agent-collects).
  </Step>

  <Step title="Point the CTA at the right thing">
    For CS, that is usually "talk to your CSM" rather than a self-serve upgrade. See [Outcomes](/build/outcomes).
  </Step>
</Steps>

## Reading the results

A customer who opens a feature demo twice, unprompted, is a signal your usage data will not give you for weeks. [People](/measure/people) groups every visit by the person, so a returning account is visible immediately.

## Related

<CardGroup>
  <Card title="Personalized links" icon="user-tag" href="/ship/personalized-links">
    Per-account briefings.
  </Card>

  <Card title="People" icon="users" href="/measure/people">
    Who came back.
  </Card>
</CardGroup>


# Enterprise teams
Source: https://docs.inklyai.dev/use-cases/enterprise-teams

Demos that stay current across many products and audiences, with the fidelity a large buying committee expects.

At scale, the problem is not making a demo. It is that you need it to serve several audiences at once, and that it goes stale the moment the product ships.

## What changes at scale

<CardGroup>
  <Card title="One demo, many storylines" icon="route" href="/build/annotations-and-storylines">
    A committee is not one audience. The engineer, the economic buyer, and security want different beats in a different order — from the same captured product.
  </Card>

  <Card title="Replace, do not rebuild" icon="rotate" href="/build/the-editor#assets">
    When one screen changes, swap that screen. Every beat and storyline attached to it survives.
  </Card>

  <Card title="Personalized per account" icon="user-tag" href="/ship/personalized-links">
    A link per named contact, with the guide briefed on what that account cares about.
  </Card>

  <Card title="Pixel-accurate clones" icon="clone" href="/account/enterprise">
    Captured pages of your real product, where the buyer clicks through it themselves.
  </Card>
</CardGroup>

## Enterprise capabilities

Two things are only available on Enterprise, and both change what a demo is:

**[Captured pages](/account/enterprise)** let visitors click through the product at their own pace. Text stays crisp and the layout adapts to the available space.

**Demos against your real product** — driven against a running instance rather than a frozen capture.

Both are sold rather than switched on, because they need setup and support to be right.

## Keeping it current

<Steps>
  <Step title="Watch the transcripts">
    The questions the guide fumbles are the fastest signal that something has drifted — either your product moved or your [knowledge](/build/knowledge) did not keep up. See [Sessions](/measure/sessions).
  </Step>

  <Step title="Fix the screen, not the demo">
    Replacing one image keeps its title, description, beats, and place in every storyline. Re-recording starts over.
  </Step>

  <Step title="Publish in place">
    Publishing updates your demo where it already is, so every link already sent — and every page the widget is on — is current. No redistribution.
  </Step>
</Steps>

## Governance

The guide can only use [annotations](/build/annotations-and-storylines) you authored and go to screens that exist. It cannot invent a product target. [Knowledge](/build/knowledge) and captured pages are treated as information, not instructions to the agent.

Screens are frozen captures with nothing running behind them: no backend, no live data, no path from a visitor to a real record.

Links appear as cards and never open automatically. Preview each outcome before publishing to confirm that the next step works as intended.

## Related

<CardGroup>
  <Card title="Enterprise" icon="building" href="/account/enterprise">
    Captured pages and real-product demos.
  </Card>

  <Card title="People" icon="users" href="/measure/people">
    Who from the account has been in, and what they asked.
  </Card>
</CardGroup>


# Product marketing
Source: https://docs.inklyai.dev/use-cases/product-marketing

Show the product on the page where people are deciding, instead of describing it.

Your landing page has about eight seconds to prove the product does what the headline claims. A demo agent proves it in place.

## The problem it solves

Screenshots and a feature grid ask the visitor to imagine the product. A recorded video asks them to sit through your ordering of it. Neither answers the question they actually have, which is almost always specific and almost always unasked.

A demo agent shows the product *and* answers the question — and tells you what the question was.

## Where to put it

<CardGroup>
  <Card title="The hero" icon="star">
    Put “See it work” beside your primary CTA and open on the product claim the page makes.
  </Card>

  <Card title="Feature pages" icon="layer-group">
    A storyline per feature page, opening on the beat that page is about.
  </Card>

  <Card title="Launch posts" icon="rocket">
    A [shareable link](/ship/shareable-link) in the changelog, blog post, and social thread.
  </Card>

  <Card title="Comparison pages" icon="scale-balanced">
    Where a buyer is actively deciding, and where seeing it beats reading a table.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Build the demo from your site">
    Inkly reads your marketing pages, so it starts with your positioning. Fix it where it guessed — see [Build from a URL](/build/from-a-url).
  </Step>

  <Step title="Write one storyline per message">
    A storyline is an argument, not a tour. If your site makes three claims, that is three storylines. See [Annotations and storylines](/build/annotations-and-storylines).
  </Step>

  <Step title="Say what you are not">
    Put the disqualifiers in your [knowledge](/build/knowledge). An agent that says "we are wrong for that" is more persuasive than one that never says no.
  </Step>

  <Step title="Match your brand">
    Use the gear in **Preview** to match the accent colour, logo, and wordmark to your site.
  </Step>
</Steps>

## The feedback loop

The transcripts are the best copy research you will get. Every question the guide fumbled is a page your site does not have; every question you did not expect is an objection you are not handling anywhere.

The [attribution](/measure/analytics#attribution) captured on your page tells you which campaigns bring people who actually explore, as opposed to people who bounce.

## Related

<CardGroup>
  <Card title="Install the widget" icon="code" href="/ship/install-the-widget">
    Orb, or your own button.
  </Card>

  <Card title="Analytics" icon="chart-line" href="/measure/analytics">
    What held attention, and where they came from.
  </Card>
</CardGroup>


# Product onboarding
Source: https://docs.inklyai.dev/use-cases/product-onboarding

Walk a new user through their first success before they hit it alone in your product.

The gap between signup and first value is where most churn happens. A demo agent closes it by showing someone the path before they walk it.

## The problem it solves

In-app tours interrupt a user who is trying to do something. Help docs require them to know the word for what they want. Both fail the same way: they arrive after the user is already stuck.

A demo agent runs *beside* the product, where the user can watch the whole flow end to end, ask what they missed, and then go do it.

## Where to put it

<CardGroup>
  <Card title="The welcome email" icon="envelope">
    A [shareable link](/ship/shareable-link) that opens the flow for the thing they signed up to do.
  </Card>

  <Card title="Empty states" icon="inbox">
    "Not sure where to start? Watch it work." A demo agent explains an empty dashboard better than illustration and copy.
  </Card>

  <Card title="Your help centre" icon="circle-question">
    Beside the article, so someone who could not follow the text can watch and ask.
  </Card>

  <Card title="The upgrade page" icon="arrow-up">
    Show the feature behind the plan, rather than describing it in a comparison table.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Capture the real path to first value">
    Not a feature tour — the actual sequence a new user has to complete. Record it with the [Chrome extension](/build/chrome-extension), signed in as a new user would be.
  </Step>

  <Step title="One storyline per outcome">
    "Send your first invoice", "Connect your calendar". Named for what the user gets, not for the feature.
  </Step>

  <Step title="Ground it in your help content">
    Point [knowledge docs](/build/knowledge) at your existing help pages. The guide can then answer the question the article was written for.
  </Step>

  <Step title="Send personalized links">
    Every demo asks for an email at the welcome screen. For existing users you already have the address, so mint a [contact](/ship/personalized-links) — the field disappears and the guide greets them by name.
  </Step>
</Steps>

## Reading the results

Where people interrupt the guide is where your onboarding is confusing. Where they go off-path is what they actually wanted to do first, which is often not the step you put first.

Both are in the [session transcript and timeline](/measure/sessions), and both are far more direct than a funnel chart.

## Related

<CardGroup>
  <Card title="Storylines" icon="route" href="/build/annotations-and-storylines">
    One outcome per storyline.
  </Card>

  <Card title="Sessions" icon="play" href="/measure/sessions">
    Where they got stuck.
  </Card>
</CardGroup>


# Sales
Source: https://docs.inklyai.dev/use-cases/sales-and-enablement

Let every prospect see the product the moment they are curious, and find out who they were.

The demo you booked for next Thursday is competing with a decision the buyer is making today. A demo agent runs the moment they ask.

## The problem it solves

A booking form filters out everyone not ready to talk to sales — which is most of the people who would have bought. They wanted to *look* first, found a calendar, and left.

An embedded agent converts that larger group: they explore, they ask the questions they were too early to ask a person, and you get the transcript.

## Where to put it

<CardGroup>
  <Card title="Beside your booking CTA" icon="calendar">
    Not instead of it. "Book a demo" for the ready; "See it now" for everyone else.
  </Card>

  <Card title="In outbound" icon="envelope">
    A [personalized link](/ship/personalized-links) that greets them by name beats a Loom nobody watches.
  </Card>

  <Card title="On the pricing page" icon="tag">
    The highest-intent page on your site, and the one where a demo answers "is this worth it".
  </Card>

  <Card title="In the follow-up" icon="reply">
    After a call, send the storyline that covers exactly what they pushed back on.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Build the demo">
    Give Inkly your product URL, or capture the logged-in product with an agent. See [Build from a URL](/build/from-a-url).
  </Step>

  <Step title="Write two storylines">
    One for the economic buyer, one for the technical evaluator. They want different beats in a different order. See [Annotations and storylines](/build/annotations-and-storylines).
  </Step>

  <Step title="Ground the guide on your objections">
    Your [knowledge docs](/build/knowledge) should answer the five things you lose deals on — pricing, security, migration, integrations, and who you are not for.
  </Step>

  <Step title="Set the outcome">
    A primary CTA and a scheduling action the guide offers when someone shows real intent. See [Outcomes](/build/outcomes).
  </Step>

  <Step title="Install it and read the transcripts">
    The questions people ask an agent are the ones they were too polite to ask you.
  </Step>
</Steps>

## For outbound specifically

Add each prospect under **Contacts** and you get a link per person, with the guide briefed by the private note you wrote about them — a note that never reaches the browser. See [Personalized links](/ship/personalized-links).

## What you get back

Who opened it, how long they stayed, which screens held them, where they stopped following the guide, and every question they asked — per person, across every visit. See [People](/measure/people).

## Related

<CardGroup>
  <Card title="Personalized links" icon="user-tag" href="/ship/personalized-links">
    One prospect, greeted by name.
  </Card>

  <Card title="Sessions" icon="play" href="/measure/sessions">
    Transcript and timeline.
  </Card>
</CardGroup>


# Training
Source: https://docs.inklyai.dev/use-cases/training

Teach a process once, and let everyone who needs it ask their own questions.

Training material goes stale the moment the UI changes, and it can never answer the question the trainee actually has. A demo agent does both jobs: it walks the process, and it answers.

## The problem it solves

A recorded video plays at your pace and stops when the trainee's question starts. Written SOPs assume the reader knows the vocabulary. Live training does not scale past one room.

An agent-guided demo runs at the learner's pace, in a safe copy of the system where nothing they click can break anything.

## What it is good for

<CardGroup>
  <Card title="New hire ramp" icon="user-plus">
    The internal tools someone needs in week one, in a copy where a wrong click costs nothing.
  </Card>

  <Card title="Standard operating procedures" icon="list-check">
    One storyline per procedure, named for the outcome.
  </Card>

  <Card title="Customer training" icon="graduation-cap">
    Attach it to a certification path or a support article.
  </Card>

  <Card title="Partner enablement" icon="handshake">
    Teach a reseller your product without giving them an account.
  </Card>
</CardGroup>

## Why the safety matters here

The screens are frozen captures. Nothing runs behind them — no backend, no writes, no real records. A trainee exploring a finance or admin tool cannot delete anything, cannot see live customer data, and cannot reach a state you did not capture.

That is usually what makes training on internal tools possible at all.

## Set it up

<Steps>
  <Step title="Capture the real system">
    Internal tools are behind a login, so record them with the [Chrome extension](/build/chrome-extension) — it captures from the session you are already signed into.
  </Step>

  <Step title="One storyline per procedure">
    Named for what the learner will be able to do, not for the screen it happens on.
  </Step>

  <Step title="Ground it in your own documentation">
    Point [knowledge docs](/build/knowledge) at your existing SOPs so the guide answers in your organisation's language.
  </Step>

  <Step title="Send personalized links">
    Every demo asks for an email at the welcome screen, and that is not configurable. Minting a [contact](/ship/personalized-links) per learner skips the field and greets them by name — which is also how you see who completed the training.
  </Step>
</Steps>

## Reading the results

Where trainees interrupt is where your process is unclear. The questions they ask are the FAQ your documentation is missing. Both are in the [transcripts](/measure/sessions#the-transcript).

## Related

<CardGroup>
  <Card title="The editor" icon="pen-ruler" href="/build/the-editor">
    Shape the screens, guidance, and knowledge behind your agent.
  </Card>

  <Card title="Storylines" icon="route" href="/build/annotations-and-storylines">
    One procedure per storyline.
  </Card>
</CardGroup>


# What is Inkly?
Source: https://docs.inklyai.dev/what-is-inkly

Inkly is a demo agent: an AI that shows people your product and answers their questions, live.

It does more than talk beside a product tour. It controls the demo. It can open the right screen, point to a feature, explain it, and answer a follow-up question without losing its place.

The visitor is not locked into a script. They can interrupt, ask for something else, or explore on their own when the demo supports it.

## What happens during a demo

<Steps>
  <Step title="The visitor says what they need">
    The agent starts with a question instead of a fixed pitch.
  </Step>

  <Step title="The agent shows the answer">
    It moves to the relevant part of the product, points to it, and explains it.
  </Step>

  <Step title="The visitor changes direction">
    A typed or spoken question stops the agent immediately. If the visitor navigates elsewhere, the agent follows and continues from the new screen.
  </Step>

  <Step title="The conversation is recorded">
    You can review what they saw, what they asked, and where they went.
  </Step>
</Steps>

## Two kinds of visitor, one agent

The same agent serves a prospect deciding whether the product fits and a customer learning to use it. For a prospect it is the demo they get instead of booking a call. For a new customer it is the onboarding session they no longer have to wait for. One build, one knowledge base, one agent; what changes is who it is built for and what it treats as the next step.

## Three ways to demo your product

### Captured screens

Most demos use images and short video clips captured from your product. The agent controls navigation and the visitor talks to it. Nothing connects to your backend, so the demo is safe and predictable.

This mode is available on Free and Pro.

### Product clone

Inkly can capture your interface as HTML. The agent can guide the demo while the visitor clicks through the product at their own pace. If they leave the planned path, the agent follows them.

The clone has no live backend connection. It preserves the interface without exposing customer data or letting a visitor change the real product.

Product clones are an [Enterprise capability](/account/enterprise).

### Real product

Inkly can also run a demo against a live instance of your product. The agent and the visitor can both interact with the real interface while the conversation continues.

Real-product demos are an [Enterprise capability](/account/enterprise). Their setup depends on your product.

## What keeps the agent accurate

The agent works from three sources:

* **Your product:** the screens, controls, and destinations it is allowed to show.
* **Your guidance:** the features to point out and the order you want to introduce them.
* **Your knowledge:** product facts, pricing, positioning, and answers to common questions.

The agent can only navigate to screens and act on targets that exist in the demo. This keeps it grounded in what you gave it.

## What you learn afterwards

Every visit creates a session with the conversation and the visitor's path. You can see what held their attention, where they changed direction, and what they wanted to know.

If the visitor identifies themselves, the session can also connect the questions and intent to that person. See [Sessions](/measure/sessions) and [People](/measure/people).

## Next

<CardGroup>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Build and share your first demo.
  </Card>

  <Card title="The editor" icon="pen-ruler" href="/build/the-editor">
    Shape the screens, guidance, and knowledge behind your agent.
  </Card>

  <Card title="Enterprise" icon="building" href="/account/enterprise">
    Learn about product clones and real-product demos.
  </Card>
</CardGroup>