Wherever they ask, one hiy answers.

Your page on hiy.ai, live chat on your website, your own product, your Inbox — four places, one engine.

Four places, three agents.

The Expert Twin leads with its public page; the Support Agent ships behind your own sign-in and your own token; the Team Agent answers colleagues who sign in.

Expert TwinSupport AgentTeam Agent
01Your page on hiy.aiYesIts homeNoNot hereYesSigned in
02Live chat on your siteYesOne tagYesWith a tokenNo
03Inside your productYesBy addressYesIts homeNo
04Your InboxNoYesHandoversNo

01

A page that answers, at hiy.ai/you.

An Expert Twin starts as a hosted page — a link that fits a bio, a talk, an email signature. Paste it anywhere people already ask you things, and the page answers them there.

Sharing your page
Unlisted when you want it
Reachable by anyone holding the link, indexed by nobody — that is the whole difference between unlisted and public.
Links that unfurl
Every twin page ships a social card, and a question link arrives with the question already asked.
A launch kit included
Your link, a QR code, and three ready-to-post announcements, drafted from your own material.

Who answers here

  • Expert TwinIts home — public, or unlisted and shared by link.
  • Team AgentAnswers here too: invited colleagues, from their first sign-in.
  • Support AgentDeliberately not here. It answers only through your site (02) and your product (03), behind your token.

02

Live chat on your site, three ways.

The same hiy, as live chat on your own site. A bubble waits in a corner, a bar rests at the foot of the page, and inline it sits in the page like any other element. One script tag each way.

Embedding, end to end

The whole install

One script tag. A Support Agent’s also names data-token-url, your own token route.

<script
  src="https://hiy.ai/embed.js"
  data-twin="your-agent"
  data-token-url="/api/hiy-token"
  async></script>
Nothing loads early
The inline iframe mounts when a visitor scrolls near; the bubble’s iframe is not created until the first open.
The visitor’s theme, and the label
The embed follows each visitor’s own device preference, and the AI disclosure stays on every plan.
Ask our own agent full screen

Who answers here

  • Expert TwinThe tag with your handle, and nothing else.
  • Support AgentThe same tag plus data-token-url, the route on your server that mints each visitor a token. No server? Open it on the websites you list and the plain tag works: anyone there can ask, so what it knows counts as public.

03

Behind your sign-in, on your pages.

Your backend mints a short-lived signed token for a visitor it already knows, and your hiy answers them and nobody else. This is the Support Agent’s home channel — the whole of how it ships inside a product — and because it is plain HTTP, anything that can call an API can be the caller, an AI agent included.

The API, tokens, and limits
  1. Signed-in visitorYour product already knows who is asking.
  2. Your serverMints a short-lived token; its secret never reaches the browser.
  3. Support AgentVerifies the token, then streams a cited answer.
app.yourproduct.com · signed inExample
AI support · may make mistakes

How do I add a teammate?

Open Settings, then Team, and press Invite. They join from the link you send them.

Team settingsdocs.yourproduct.com
Tokens your server signs
HMAC over a shared secret, an hour at most — your users never need hiy accounts, and we never see your user list.
Streamed, cited answers
The same frames the hosted page renders, citations intact, over one POST.
Every limit named
Rates, caps and error shapes are all in the docs — including the files an AI agent can fetch to integrate this without a person.

Who answers here

  • Support AgentIts home channel. No token, no answer — nobody reaches it except through you.
  • Expert TwinCallable too: a public twin answers by its address alone, no token needed.

04

Every handover lands in your Inbox.

When a Support Agent can’t answer, the thread doesn’t die in a widget. The visitor leaves an email, and the question is in the agent’s Inbox that second, with the whole conversation behind it. Where email is set up, you’re also emailed what they asked and how to reach them, and the visitor gets a receipt. One direction, stated outright: conversations end with you — nobody writes to your hiy by email.

How handover works

On your site

yoursite.comExample

Can I move my projects to another account?

Not in the source material

I don’t have anything about moving projects between accounts in the docs. Want me to pass your question to a person?

Want a person to pick this up?

Leave your email and your question goes straight to the team.

[email protected]Send to the team

In your Inbox

InboxExample

“Can I move my projects to another account?”[email protected] · Waiting

Can I move my projects to another account?

I don’t have anything about moving projects between accounts in the docs. Want me to pass your question to a person?

The question and the person, not a ticket number
The Inbox row carries what they asked and how to reach them, and opens the whole conversation behind it — so you answer a person rather than chase a reference.
Alerts as they land
Where email is set up, a new lead or a new unanswered question can email you the moment it happens.
A summary on your schedule
By email where it is set up: daily, weekly, or none — who asked, what they asked, who opened your booking link.
Recorded whatever the clock says
A handover goes through outside your team hours too; Team Hours change only what the visitor reads while it happens.

Who answers here

  • Support AgentThe handover and its Inbox — plus, where email is set up, the handover email and the visitor’s receipt. The one agent that sends either.
  • Team AgentNo handover form: it never asks a colleague for an address. An unanswered question lands in your teach queue instead, and, where email is set up, can email you the moment it does. The Handover page sets what it says when it is stuck.
  • Expert TwinThe alerts and the summary email, like every agent, where email is set up.

05

Three products, one set of rules.

An Expert Twin for you, a Support Agent for your product, a Team Agent for your colleagues. The channels above are where they differ; underneath is one engine, and the rules never change with the channel.

The three products, compared
  • Taught once

    Teach it once and it knows the answer on your site the moment it knows it anywhere.

  • Cited the same

    An answer cites its source on your own pages exactly as it does at hiy.ai/you.

  • Refused the same

    What it won’t answer in one place it won’t answer anywhere.

  • Labelled AI

    It is labelled AI on every surface — no plan removes that.

Change a rule once, and it changes everywhere it answers.How the loop behind this works

06

What’s next, honestly.

From the roadmap’s exploring tier — what we intend to build, not a commitment or a schedule.

Where everything stands
  • Exploring

    Slack & WhatsApp

    The same agent and the same rules, answering where your people already are.

  • Exploring

    Helpdesk & CRM

    Handover into Intercom or Zendesk when a person takes over, and CRM or Zapier out.

  • Exploring

    Voice

    An audio twin.

What people ask before they ship it.

Where it answers, what it costs your page, and what happens at the edges.

Can it answer in Slack or WhatsApp today?

No. You can paste your twin’s link there and it unfurls with a card that carries the question, but the twin does not answer natively inside either app. Multi-channel is something we are exploring, not something shipped — the roadmap says exactly that, and so does this page.

Which channels does a Support Agent use?

Your website and your own product — the same script tag plus a token your server mints, and the API behind your sign-in. It deliberately has no public page: its own hiy address answers nobody. When it can’t answer, the visitor can leave an email: the question lands in the agent’s Inbox with the conversation behind it. Where email is set up, you’re also emailed what they asked, and the visitor gets a receipt.

Will the embed slow my site down?

It loads nothing until it’s needed. The snippet is one script tag; the inline embed’s iframe mounts when a visitor scrolls near it, and the bubble’s iframe is not created until the first open. A visitor who never engages pays nothing.

Can visitors tell they’re talking to an AI?

Yes — everywhere, always. Every surface is labelled AI, and no plan removes that. The only branding a plan can remove is the “Powered by hiy.ai” line.

What happens when it can’t answer?

It says so in so many words instead of improvising — and a Support Agent offers to hand the thread to a person. Either way the unanswered question lands in your teach queue, so the gap closes for the next visitor.

Do I need a developer?

For your hiy.ai page, no — it’s live when you publish. For your website, whoever can paste one script tag, plus a small token route on your server for a Support Agent — or no server at all, if you open it on the websites you list. For your own product, yes: your backend mints the visitor tokens, and the docs walk through it.

Which plans include which channels?

Your hosted page, the inline embed, the chat bar and the API work on every plan. The floating bubble is part of Founding, and so are Support and Team Agents, with the handover and its Inbox; each account gets one 14-day free trial. Pricing has the full comparison.

They’re already asking, everywhere.

Create your hiy
  • 14-day free trial
  • No card needed
  • Paste a URL to start