An AI agent for your website is different from a chatbot script. A script follows the branches somebody drew. An agent reads the question, decides what it is about, and works out what to do next.
This one starts by building itself from your website — its role, its knowledge, its skills and its voice — and then runs on your site answering visitors on its own.
Autonomy is only useful if you know where it stops. Here is the honest split.
It decides on its own:
It comes to you:
It never:
The profile is the job description: who the agent is, what it covers, how it should sound and how long its answers should be.
It writes that from your website first. You review it, and you can rewrite any line. Rules sit on top of the profile as extra instructions — what to always mention, what never to say.
It answers from your own content: pages, files, images and question-and-answer pairs you add yourself.
When it cannot answer, it says so and logs the gap rather than guessing. Fill the gap once and it answers that question from then on.
Answering is the baseline. The agent can also collect a name, email and phone, put a button in the chat, show your contact card when someone wants a person, and send a follow-up if they go quiet.
You turn each of those on or off. The agent decides when a conversation calls for them.
Conversations and captured contacts can go to Google Sheets, to thousands of tools through Zapier, to your own endpoint through a webhook, or show up as events in Google Analytics.
The agent does not log into those tools and change things mid-chat. It sends what happened, and your other systems do the rest.
Mostly, yes. The words are used interchangeably by most people searching for either.
Where there is a difference, it is about how much the thing works out for itself. A chatbot in the older sense answers from a script somebody wrote. An agent is given a role and a set of knowledge, and decides how to respond within that.
This product is both, depending on which word you use. It appears on your site as a chat widget. Behind it is an agent that reads your content, judges intent, and picks its own response.
Three things it is not, so nobody finds out the hard way.
If you need a shared inbox with agent handover, Tidio and Intercom are built for that and we are not going to pretend otherwise.
On WordPress the same agent runs as a snippet in the footer or through a code-snippet plugin — no PHP, no database tables, and it works with any theme, including Elementor.
Paste your site address, review what it wrote, then add the code. There is a free plan if you want to try it on a live site first.
It will not invent facts that are not in your knowledge base. It will not change records in your other systems during a conversation. It will not pass the chat into a shared inbox, because there is not one.
When a visitor wants a person, it shows your contact card — WhatsApp, a call or an email — and they continue there. If you need live handover into a queue, that is a different kind of product.
