Skip to content
InPage

An AI assistant that lives in your website

Your website,
answering back.

Visitors ask in their own words. Instead of a chat bubble in the corner, the page changes to show the answer: the right screen, the right plan, the comparison they were looking for.

acmefleet.example

Try a question

What the page shows

Acme Fleet

Run your rental bicycles without the spreadsheets.

Fleet tracking and repair logs for bicycle rental depots.

Try a question

Acme Fleet is made up, to show how it works. It isn't a customer, and this demo is scripted.

How it works

Most of the page stays quiet. The part they asked about moves.

  1. They ask, in their own words

    A box on your page, or a button if you'd rather. English and Portuguese today, following your page's language.

  2. The page shows the answer

    A short reply, next to the view that fits: product screens, a plan comparison, customer logos, a before-and-after, or a short form.

  3. Your content, not generated content

    The screens, plans and quotes are the ones you provided. The AI chooses what to show and writes the sentence around it. It doesn't draw your product or invent a plan.

  4. When they're ready, they reach you

    A button right under the answer opens a conversation with your team, so they don't have to go looking for how to reach you.

Your facts

It's only as sure as you are.

The assistant is instructed to answer from a knowledge base you control, not from what it can guess. Each fact carries its source and a status, and the status decides how it may be used.

Three facts from the made-up Acme Fleet

An AI can still get something wrong, so you can read every conversation, and run your own standard questions against a draft before you publish it.

Your control

Nothing reaches your visitors until someone on your team says so.

  • Drafts, then publish

    Change facts and images in a draft, try real questions on it, and publish with a note. Every version is kept, so you can go back.

  • Images checked before they're public

    Uploads stay private until approved. Location data is removed, AI drafts the captions in both languages, and it flags names, emails and other things to look at. It can miss things, so a person decides.

  • Every conversation, readable

    See what visitors asked and what they were shown. It's how you find out what your website wasn't answering.

  • Roles and a record

    Owner, Admin, Editor and Viewer. Publishing, member changes and exports are recorded in an activity log.

Install

One script tag. We run the rest.

Add it to your pages, and tell us which addresses it should work on. There's nothing to deploy, and no keys to look after: the key in the tag is public by design, and it only works from your addresses.

HTML
<script async src="https://api.inpage.io/loader.js"
        data-site-key="YOUR_SITE_KEY"></script>

<ask-box></ask-box>
  • Hosted by us, and updated without you doing anything.
  • About 6 KB until someone asks. The rest loads when it's needed.
  • It keeps to its own shadow DOM, so your styles and its styles stay out of each other's way.
  • Works in plain HTML and in any framework.

Your data, and your costs

The parts you'd ask about anyway.

Kept apart
Each customer's data is separated at the database, not only in our code. Tests check that one can't read another's.
Scripts held back
A bot check runs before a conversation starts. Most visitors never notice it, and anyone it blocks is pointed to your team.
Limits on spending
Daily and monthly limits stop a bad day becoming a big bill. If one's reached, visitors are pointed to your team.
Yours to take or remove
Owners can download everything we hold for them. One visitor's conversations can be deleted on request.

See it on your own website.

We set up each customer by hand for now, so it starts with a conversation.

Request a demo