AI chatbot: train it on your content

Add an AI chatbot to your site that's trained on your own pages, runs on your own AI provider key (BYOK), and sends every chat lead straight to your CRM.

The Amabrik AI chatbot is an assistant that answers your visitors’ questions from your own content, around the clock. You point it at your website, it reads your pages, and from then on it replies with your real pricing, shipping, returns, docs and FAQ instead of generic guesses. It runs on your own AI provider key, so your chats go directly to the provider you choose and you pay them at cost, with no per-chat fee from Amabrik on top.

A few things it is not. It’s not live human chat: there’s no agent inbox, no “an agent will be with you shortly”, no seat to staff. It’s an AI assistant that answers on its own and hands off to you when it should. It’s also not a CRM. When it collects a lead, that lead goes straight to your connected integration and is never stored on Amabrik.

Turn it on

In your dashboard, open Widgets and click the AI Chatbot card.
Pick a theme to start from, then Continue to open the editor.
The editor has a live desktop and mobile preview on the right and a sticky Save button. Changes save on their own as you edit.
When you’re ready, copy the Amabrik snippet into your site’s <head> (you only ever paste one snippet for all your widgets). Make sure the chatbot’s toggle at the top of the editor is on.

If you haven’t added the Amabrik snippet to your site yet, see Getting started. The chatbot works on WordPress, Shopify, Webflow, Framer or a custom build.

Connect your AI provider key (BYOK)

The chatbot needs an AI key before it can answer. You bring your own, so inference runs on your account and you’re never marked up per conversation. Add your key once under AI API keys in your dashboard, then pick it inside the chatbot’s Agent tab.

Amabrik supports four providers. You only need one. Your key is validated, then encrypted and stored encrypted; it’s never sent to the browser, never put in your public config, and never logged. It’s decrypted in memory on our side only to forward your chat to the provider.

OpenAI (ChatGPT)

Open platform.openai.com/api-keys and sign in, or create an account.
Click Create new secret key and copy it. You only see it once.
If you can’t create one, add a small credit (about $5) under Billing, then retry.
Paste it into Amabrik under AI API keys and click Validate & save.

Models range from GPT-4.1 nano (cheapest) up to the GPT-5 series. GPT-4.1 mini is the recommended balance for a website chatbot.

Anthropic (Claude)

Open console.anthropic.com/settings/keys and sign in, or create an account.
Go to Settings, then API keys, then Create Key, and copy it.
If you’re blocked, add credits (about $5) under Billing, then retry.
Paste it into Amabrik and click Validate & save.

Claude Haiku 4.5 is the recommended fast, low-cost option, with Sonnet and Opus available for stronger reasoning.

Google (Gemini)

Open aistudio.google.com/apikey and sign in with your Google account.
Click Create API key and copy it.
The free tier is enough to start; enable billing for higher limits.
Paste it into Amabrik and click Validate & save.

Gemini 2.5 Flash is the recommended default; Flash-Lite is cheaper for high volume and Pro is for the hardest questions.

Perplexity

Open perplexity.ai/settings/api and sign in.
Add a little prepaid credit under Billing (the API needs credit to run).
Click Generate API key and copy it.
Paste it into Amabrik and click Validate & save.

Perplexity models answer with live web search built in, which adds to the cost per message. Sonar is the recommended entry model.

After saving a key, go to the chatbot Agent tab, choose the Provider you connected and pick a Model from the list. Each model shows a plain estimate of cost per 1,000 messages so you can choose without guessing. If you select a provider you haven’t connected, the editor tells you to add its key first.

Train it on your content

This is what makes the answers actually yours. In the Knowledge tab:

Enter your Website URL.
Click Train on my site.

Amabrik then reads your site. It starts from your sitemap (following one level of sitemap index), and falls back to following internal links from your homepage if there’s no sitemap. It respects your robots.txt, stays on your own domain, and reads up to 1,000 pages. It pulls the visible text out of each page, splits it into passages, and indexes those passages so the assistant can find the right one for any question.

Crawling is incremental. A re-train sends conditional requests and only re-reads pages that actually changed since last time, so keeping the assistant current after you edit your site is cheap. Re-train any time your pricing, shipping or docs change.

When a visitor asks something, Amabrik finds the passages from your site that best match the question and gives them to the model as context. The answer is grounded in your real pages, not a generic model guessing.

Add knowledge by hand

In the Knowledge tab you can also add facts that may not live on a page:

Business information: hours, location, contact, anything the agent should always know.
Question & answer pairs: exact answers for common questions.
Text blocks: passages you want the agent to know verbatim.

Set it up, tab by tab

The chatbot editor uses the same simple tabs as every Amabrik widget, with named accordion sections inside each one.

Agent

Where the assistant’s brain lives.

Provider & model: pick the AI key you connected and the model to run.
Profile & behavior: set the Agent name and Role, a Tone of voice (Friendly, Professional, Casual, Direct or Custom), and an Answer length (Short, Medium or Long). Turn on Strict mode so it answers only from your knowledge and refuses to use outside facts. Set a Fallback message for when it has no answer.
Greeting & questions: write the opening Greeting, add Quick-reply buttons that seed the first questions, and add Conversation rules the agent must always follow (for example, “Never give legal advice”).

Knowledge

Train on your site, and add manual knowledge, as described above.

Skills

In-chat actions you can switch on one at a time:

Collect contacts: when a visitor shows clear interest, the agent asks for the details you choose (name, email, phone), one at a time, and forwards them to your connected integration. You write how it should ask. Amabrik never stores what it collects.
Follow-up message: if the visitor goes quiet, the agent sends one gentle nudge after a delay you set, to re-open the conversation.
Contact a human: offer a direct way to reach a person by Email, Phone, WhatsApp or Link, with a button label of your choice.
Action buttons: up to six persistent buttons under the chat, each linking to a key page like pricing, booking or docs, opening in a new tab.

Style

The look of the chat.

Theme: start from one of the built-in themes (Amabrik, Ocean, Forest, Ruby, Blossom, Sunbeam, Amber, Midnight, Cosmos, Nebula). Applying one sets the colors and the background texture; you can fine-tune everything after. A Background texture can be None, Waves, Leaves, Space or Stars.
Colors: each color is its own full-width row: accent, background, agent bubble, visitor bubble, text, header, quick replies, send button, input background, borders and the online dot.
Avatar: an icon, the agent’s name initial (monogram), or an image URL you host elsewhere (so it costs you no storage).
Typography: font, weight, size and line height for the chat text, plus the corner radius.

Display

How the chat shows up on the page.

Layout: a Floating button (a bubble in a corner that opens the chat) or Embedded inline on a page. For floating you choose the launcher icon, the corner (bottom right or bottom left), and the open/close animation. For embedded you set the height and paste the small embed snippet where the chat should appear.
Behavior: a Compact or Large message box, and whether to require visitor consent before the conversation is stored.
Proactive messages: nudge visitors with a small ping bubble on chosen pages (by URL pattern) after a delay, and optionally auto-open the chat. Each proactive message is per language and can be shown once per visitor.

Advanced

Languages: set the default language, auto-detect the visitor’s language, and translate the greeting and quick replies for each language you add.
Direction: Auto, LTR or RTL. Auto follows the language, so Arabic, Hebrew and similar mirror the whole layout on their own.
Analytics: optionally send amabrik_chat_open, amabrik_chat_message and amabrik_chat_lead events to your Google Analytics. These fire only after the visitor grants analytics consent, so they stay compliant.
Custom CSS: target the chat’s Shadow DOM for fine styling.

Where chat leads go

When the Collect contacts skill gathers a name, email or phone, those details are forwarded straight to the integration you’ve connected to this widget (your CRM), never stored on Amabrik. The assistant is told to never claim it saved them itself. Amabrik is a pass-through here, not a CRM: there’s no lead inbox in the dashboard, because we don’t keep the leads. Connect your CRM in the widget’s integration settings so captured contacts have somewhere to land.

Translations and languages

Every Amabrik widget is multi-language, and the chatbot is no exception. In Advanced > Languages, pick a default language and add others. For each added language you translate the set phrases (the greeting and quick replies) once. With auto-detect on, a visitor is greeted in their browser language when you’ve added it, and otherwise the default. The answers themselves come from your content in the visitor’s language, since the model replies in the language it’s asked in.

Tips

Train on your site before you go live, so the first visitor gets a real answer.
Turn on Strict mode if it matters that the assistant never strays from your content. Leave it off if you want it to fill small gaps from general knowledge while staying in its role.
Write a helpful Fallback message. It’s what visitors see when there’s no answer, and (in strict mode) for off-topic questions. Pair it with the Contact a human skill so a dead end becomes a handoff.
Re-train after any meaningful site change. It’s incremental, so it only re-reads what changed.
Start with a cheaper model. The recommended models answer most website questions well; you can switch to a stronger one any time without changing anything else.
Use Action buttons to turn a good answer into a next step: see pricing, book a call, track an order.

FAQ

Is this live human chat?

No. It’s an AI assistant that answers on its own, trained on your content. There’s no agent inbox or staffing. When a visitor wants a person, the Contact a human skill shares your real email, phone, WhatsApp or a link.

Who pays for the AI, and how is it billed?

You do, directly to your AI provider, because you bring your own key. Your chats run on your OpenAI, Anthropic, Google or Perplexity account at that provider’s rates. Amabrik adds no per-chat or per-resolution fee on top; the chatbot is included in your Amabrik plan like every other widget. Each model in the editor shows a plain estimate of cost per 1,000 messages so you can pick one that fits your budget.

Will it make up answers?

Not in strict mode. With strict mode on, it answers only from your indexed content and your manual knowledge, and when something isn’t covered it gives your fallback message instead of inventing an answer. With strict mode off, it can fill small gaps from general knowledge while staying in its role. Either way, its answers are grounded in the passages from your own site.

Which AI providers and models can I use?

Four providers: OpenAI (ChatGPT), Anthropic (Claude), Google (Gemini) and Perplexity. Each offers a range of models from cheap and fast to flagship, and you can switch model any time from the Agent tab.

Does it work in other languages?

Yes. Turn on auto-detect and it greets and replies in the visitor’s language, so one assistant serves every market you sell to. You translate the set phrases like the greeting once per language; the answers come from your content in the visitor’s language.

How does training actually work, and how often should I re-train?

You give it your website URL and it reads your pages (sitemap first, then internal links), respecting robots.txt, up to 1,000 pages. It indexes the text so it can find the right passage for any question. Re-train whenever you change your site; it’s incremental, so it only re-reads pages that changed.

Does Amabrik store the leads it collects?

No. Collected contacts are forwarded straight to your connected CRM and are never stored on Amabrik. There’s no lead viewer in the dashboard because we don’t keep them.

Is the conversation stored, and what about consent?

The conversation is kept in the visitor’s own browser so it survives a page reload, and you can require visitor consent before that happens. If you also turn on the Google Analytics events, those only fire once the visitor grants analytics consent.