Support chat that answers
from what you know.
A messenger on your site. An AI that answers from a knowledge tree you control, and a human one click away. A sign-in your visitors already have. Every conversation lands in your graph — searchable, shareable, yours.
This is what your visitors get.
Open the chat straight away — that is the open mode, anyone can ask. Or click Sign in with iLiveMyLife first, and the same thread becomes the visitor’s own. Left: your website. Right: what you see in your graph while it happens.
Three things, one widget.
A messenger on your website
A docked chat that opens on any page. Every visitor conversation becomes a node in your graph — with history, files, and your whole team able to join.
An AI that knows your business
Lifebot answers from the knowledge tree you give it — shipping, returns, pricing, docs — and only from that. It is the same AI that works your own graph, pointed at a branch you chose. It hands over to a person whenever asked.
Sign-in your visitors already have
“Sign in with iLiveMyLife” — one account across every partner site. No registration form on your side, no passwords for you to store.
Open to everyone, or signed in.
The same window, two settings. Most sites end up running both: open on the public pages, signed in where the work continues.
Open — no sign-in at all
Anyone who lands on the page can ask: no account, no form, nothing kept in their browser. The AI answers from the tree you chose. Best for pre-sale questions, documentation and landing pages — the visitor who would never register. The chat in the corner of this page is this one.
Signed in — a conversation that continues
One click on “Sign in with iLiveMyLife” and the visitor becomes a participant: the thread belongs to them and to you, keeps its history and files, your team can join it, and either side can come back to it days later. Best for support, orders, and anything with a follow-up.
What it costs you to install: the signed-in widget runs entirely in the visitor’s browser under their own account, so it needs nothing from your servers — a static site is enough. The open one talks to a small service on our side, because an account token cannot sit in a browser; we host it, or you run it inside your own perimeter.
Live in days, not quarters.
Your knowledge becomes a tree
Drop in your FAQ, policies, product docs — Lifebot structures them into nodes, or we do it with you. Already working in iLiveMyLife? Just reference the nodes you have. You edit the tree; the answers follow.
One import on your site
From @ilivemylife/react-sdk: IlmlAskWidget for the open chat, or IlmlButton + IlmlChatWidget for the signed-in one. Or we embed them for you. The signed-in version also makes your website a registered partner of the platform — that is the part we switch on, not you.
Answer where you like
Let the AI take the first line and step in from the app when a person is needed — or answer everything yourself. Each conversation is a node: share it with your team, search it forever.
If your team already keeps its work in iLiveMyLife, there is nothing to prepare. Put references to the nodes you already have — Features, Roadmap, the Deck, the docs — into the chat’s knowledge tree, and the AI on your homepage answers from them. They are the same nodes your team edits every day, so the answers never fall behind: ship a feature, update the roadmap, and the next visitor already hears about it. The chat is only as good as what it knows — and here it knows what your team knows.
Anyone who answers the same questions every day.
Straight answers.
Is this just another chatbot?
No. The AI answers from a knowledge tree you own — the nodes you gave it access to — and hands over to a real person the moment you or the visitor want one. Every conversation is a node in your graph: searchable, shareable with your team, and yours to keep.
What does the visitor need?
Nothing at all, if you run the open version — they just type. If you run the signed-in one, a single click: “Sign in with iLiveMyLife”. It is the same account they use on every partner site, so there is no sign-up form on your side and no passwords for you to store.
Where do the conversations live?
In your iLiveMyLife graph, under your site’s node. Open them in the app, reply from there, or let your AI handle the first line — you decide per node who sees what.
How does it get onto my website?
One import from our React package, @ilivemylife/react-sdk: one component for the open chat, two for the signed-in one (a sign-in button and the chat widget). Or we embed them for you. For the signed-in version your site also becomes a registered partner of the platform — we switch that on; nothing else about your site changes.
Do we need a backend of our own?
For the signed-in chat, no — the widget works in the visitor’s browser under their own account, so a static site is enough. The open, no-sign-in chat needs a small service to hold the account token, since a token cannot live in a browser. We host that for you, or you run it in your own infrastructure.
Can it run inside our own perimeter?
The platform runs on our own Kubernetes and can be deployed inside a client’s infrastructure. Tell us what you need and we will scope it. How self-hosting works →
How do I get it?
Talk to us. We scope a pilot on your site with your first knowledge tree and run it with you, then agree the rest once you have seen it work. It is a project with a result, not a per-seat subscription.
Get one on your site.
We set it up with you: a pilot on your site with your first knowledge tree, then a scope for the rest. A project with a result, not a per-seat subscription — the platform is what makes it weeks instead of quarters.
The chat behind that button runs on this exact product — you are trying it before you buy it.
