The site widget
A single agent, dropped onto your site in one line of code, with live preview, conversation tracking and evaluation all in one place.
The Web agent is your customer service placed directly on your pages, in a chat bubble. You build it, dress it in your colors, install it in one line, then review and rate every conversation from a single screen. Here is everything you control.
Create a website agent
A website agent is a brain that lives on your site, in a chat window at the bottom of the screen. It's the same engine as your social agents: same instructions, same knowledge base, but with a channel of its own, your site, and an appearance you control entirely.
You build it in the editor, with a live preview on the right: the real widget, always open, replaying your brain and re-styling itself with every setting. The "Deployment" tab brings together everything that shapes its presence on the site: its appearance, its proactive engagement, and the embed code.
Appearance
The "Appearance" section tunes the look of the widget on your site. Every change shows up instantly in the preview on the right, without saving anything, so you can fine-tune until you get exactly the look you want.
| Setting | Effect |
|---|---|
| Color | The widget's brand shade: button, header, and the agent's bubbles. Picked with the eyedropper or as a hex code. |
| Position | The side the bubble anchors to: "Left" or "Right". |
| Logo | An image (PNG, JPG, or SVG, 2 MB max) shown in the header and on the button. Without a logo, the initial is used. |
| Initial | One or two letters shown when there's no logo. |
| Title | The name shown at the top of the chat window. |
| Subtitle | The line under the title, for example "Your assistant". |
| Button text | The label on the open button, for example "Chat". |
| Name shown in the footer | Your company's name, at the bottom of the window. |
None of this requires touching your site's code: the appearance is driven entirely from here, and the preview gives you a faithful rendering.
Proactive engagement
By default, the widget waits to be clicked. Proactive engagement invites it to reach out to the visitor. Two levers, each enabled separately.
Teaser message: a small bubble appears above the widget after a delay you set in seconds, with the text of your choice, for example "A question? We're here". A click opens the chat.
Automatic opening: the window opens on its own after a delay, without the visitor having to click.
Both only fire if the visitor hasn't yet started the conversation: the moment they open the window or dismiss the bubble, they go quiet. We never push someone who has already responded.
A short teaser, after five to ten seconds, gets noticed without being annoying. Reserve automatic opening for pages where help is genuinely expected, like a checkout flow or a pricing page. Across a whole site, opening every time eventually wears thin.
Embed
To place the agent on your site, a single line is enough. The "Embed" section gives you the ready-to-copy code; paste it just before the </body> tag of your pages, and the widget appears on its own.
<script src="https://app.magnitude-ai.com/widget.js" data-key="your_key"></script>The key (data-key) identifies your agent; the code is already filled in with yours in the editor. No style changes are needed on the site side: everything is driven from the "Deployment" tab. Adjusting the appearance or engagement later? The widget in place updates itself, without touching this line.
The embed code only appears once the agent is saved, the time it takes for its key to be generated. Until the key exists, the section simply prompts you to save the agent.
The site's conversations
The "Web Agent" page brings together all the sessions held by your website agents. On the left, the list of sessions, with the number of exchanges, the visitor's name or the label "Visitor", the first question, and topic tags added automatically. A search field and, if you have several agents, a per-agent filter help you find an exchange.
Open a session to review the chat exactly as the visitor saw it: their messages, the agent's replies, the buttons offered, the product cards. Everything is read-only. The agent replied on its own, in the moment; this page is for reviewing, understanding, and rating, not for taking over.
What the agent did to reply
Below the replies, you'll find the agent's work, reserved for your team: every lookup of your knowledge and your data is traced. Expand a trace to see what the agent searched for and what it got back.
Each tool carries a clear name: "Knowledge base" for a search in your documents, "Data" for a query on a connected source, "Transfer to an agent" when it hands off to a human, and the names of your custom tools. Identical calls that follow one another are grouped into a single line, with a counter, to stay readable.
The sources and tool traces show up in the preview and for your team only. The visitor sees only the reply: never the documents cited, never the searches run behind the scenes.
Sometimes a session ends on a lookup with no written reply: the agent searched but composed no message. This case is flagged "No reply" at the bottom of the thread. It's a useful clue: often, the information was missing from the knowledge base, or an instruction needed to be sharpened.
Rate a session and take notes
To the right of an open session, a panel lets you judge the exchange and document it for the team. "Rate" offers two verdicts, "Positive" or "Negative", with one click (click again to remove your rating). A rated session carries a dot in the list, letting you spot at a glance the cases to review.
Below, "Internal notes" collects your remarks: what worked well, what needs fixing, a case to bring up in a meeting. These notes stay with you, with their author's name, and never appear on the visitor side. Together, the rating and the notes turn your real conversations into raw material for improving the agent.
What you spot here, a reply that misses the mark or a missing piece of information, gets fixed in the agent's instructions or its knowledge base, then verified in the sandbox and the scenarios before going back live.