Business Agent · Website widget
Paste one script tag into your website and your agent appears in the corner — your colours, your knowledge, no account for the visitor. Everything about how it looks is changed from your dashboard afterwards. You never touch the tag again.
That bubble in the corner is not a mock-up — it is this widget, running our own agent.
Your dashboard gives you these two lines with your own agent's address already in them.
Paste them once, just before the closing </body> tag of your site, and
you are done.
<!-- paste before </body> -->
<div data-chatlamix-agent></div>
<script src="https://myaimodelmanager.com/agent/your-agent/embed.js" async></script>If your site lets you add a snippet — WordPress, Shopify, Webflow, Squarespace, a landing page builder or plain hand-written HTML — it will take this one.
The tag does not carry your settings — it fetches your agent. Every time someone loads your page it asks us how this agent should look right now, so anything you change in your dashboard is live on your site about a minute later, with nothing to re-paste and nobody to ask for a deploy.
Turning the agent off in your dashboard stops the widget answering too — you never have to go back and edit your website to take it down.
Same agent, same knowledge, same conversation — the only question is whether you want it waiting in the corner or built into the page.
The floating button has two looks: a plain round chat icon, or a wider pill carrying your agent's face and its name.
Pinned to the bottom left or right of every page you put the tag on, above your own layout but out of its way. Tapping it opens a chat panel just above the button — 380 by 600 on a desktop, and as wide as the screen allows on a phone. Tapping again puts it away.
Choose the round chat icon, or the pill that shows your agent's photo beside Chat with and its name — written in whichever language you set the agent to lead in, so a French agent invites people in French.
The same chat, mounted exactly where you put the div — in a support section, at the foot of a pricing page, in a sidebar, inside a landing page you built for one campaign. It sizes itself to the space and reads as part of the page rather than something floating over it.
Nothing else changes: it is the same agent with the same knowledge, so a visitor who started in one can carry on in the other.
A chat widget sits on someone else's website, in the corner of the eye, all day. Most of the work went into it not being annoying.
Open it and the button does not sit stubbornly on top of the conversation: it narrows into a round close control, the two strokes of the cross drawing outward from the centre, while the panel springs up out of the button's own corner.
Someone who has asked their device for reduced motion gets no animation at all. Someone browsing in dark mode gets a dark chat — and a dark panel behind it, so nothing flashes white for a second while it loads.
The chat runs inside its own frame, so its styling and yours can never leak into each other. The handful of elements outside the frame carry their own prefixed names and one scoped stylesheet, and the script loads asynchronously — your page never waits for it.
A proper button with a proper label, reachable and operable from the keyboard, announcing whether the chat is open or closed. Your own "Talk to us" link can open it too, instead of sending the visitor somewhere else.
"How much is this one?" is the most common question a website chat gets, and it is unanswerable without knowing where the visitor is. So the widget reads the page it is sitting on and hands it to the agent before it answers.
The page is context, never instruction. The agent still answers only from the knowledge you gave it, and it is explicitly built to ignore anything written into a page that tries to tell it what to say — including text a stranger left in a comment.
Everything you switched on for your agent works inside the widget, for a visitor who never signs up for anything.
It replies from the knowledge base you wrote. Asked something outside it, it says so and flags the question for you rather than inventing a price.
How the knowledge lock worksIt collects the fields you chose in the flow of the chat, and each one lands on your pipeline board — no form, no "fill this in first" gate.
Lead capture & pipelineA visitor who is ready for a human can take a slot you actually have free, from inside the same conversation.
The call button lives in the chat's own header, so a visitor can start talking without leaving your page or dialling anything.
When showing beats describing, it can put one of your images or videos straight into the reply.
A returning visitor picks the conversation up where it stopped, remembered in their own browser and readable by nobody else.
Every agent gets its own page on a link you can hand out anywhere — a bio, an email signature, a QR code on a menu, the destination of an ad. Same agent, same knowledge, same branding, on a page we host for you.
Two lines: an empty div and one script tag pointing at your agent. Put them once before the closing body tag of your site. There is no package to install, no framework, no build step and no plugin, so it works the same on a hand-written HTML page, WordPress, Shopify, Webflow or anything else that lets you add a snippet.
No. The tag is a loader, not a copy of your settings: it asks us for the agent every time your page loads, so the style, the position, the theme and the colours you pick in your dashboard are already in it. Even switching between the floating button and the inline chat needs no new snippet. Changes reach your site within about a minute.
Two ways. As a floating button in the bottom corner — left or right, either a round chat icon or a wider pill showing your agent's face and "Chat with <name>" — which opens a chat panel above it. Or as the chat itself, placed inline wherever you put the div, so it sits in the page like any other section.
It is built not to. The chat runs inside an iframe, so its styling and your site's can never bleed into each other, and the few elements outside the iframe — the button and its panel — use their own prefixed class names and a stylesheet scoped to them. The loader makes no cross-origin data calls; it only opens a window back to us.
By default yes — leave the theme on automatic and the chat, and the panel behind it, follow whatever the visitor's system is set to. If your site is always dark or always light you can force one instead, or set the background, text and bubble colours yourself.
Yes. The widget reads the page it is sitting on — the title, the description, the main heading, the visible text, and the product name and price if the page publishes them — and hands that to the agent. So "how much is this one?" on a product page is answered about that product. Page text is treated as untrusted: the agent still only states facts from your knowledge, and never follows instructions hidden in a page.
No. Anyone can open it and talk, exactly like the bubble in the corner of this page. Their conversation is remembered in their own browser, so coming back to your site continues the thread rather than starting again, and no one else can read it.
Yes — whatever you switched on for the agent works inside the widget: leaving their details, booking a meeting against your availability, being shown an image or a video mid-answer, and a live voice call if you enabled calls.
Every agent also gets its own page at a link you can share anywhere — in a bio, an email signature, a QR code, an ad. It is the same chat, the same knowledge and the same branding, on a page we host.
Switch the agent off in your dashboard and the widget and the public link both stop answering, with nothing you configured lost. You do not have to go back and edit your website.
The bubble in the corner of this page is exactly what you would paste into yours. Open it, ask it something awkward, then build your own — free, with your website read for you to make the first draft of its knowledge.
You only pay when you put it live. See pricing.