Omnichannel

Add a Chatbot Widget to Your Website Without Code

A website chat widget is generated inside the chatbot panel and installed with one code snippet. This guide covers where to place it, how to write the greeting, how working hours and offline mode should behave, and what to check on mobile. Messages from the website land in the same inbox as Instagram, WhatsApp and Messenger.

Adding a chatbot widget to your website is a copy-and-paste job. You generate the widget inside the chatbot panel, copy one short code snippet, and paste it into your site template before the closing body tag. No plugin, no developer, no rebuild of the site.

The code is the easy part. The decisions that actually change your results are which pages the widget appears on, what the first message says, what happens outside working hours, and how the bubble behaves on a phone. This guide walks through all of them in the order you will meet them.

What a website chat widget is

A chat widget is the small bubble in the bottom corner of a website. A visitor clicks it, types a question, and gets an answer. Behind the bubble sits your bot: it answers from a knowledge base you uploaded, replies in the language the visitor writes in, collects a phone number or email when the visitor is ready to buy, and passes the conversation to a human when a human is needed.

Two clarifications. A chat widget is not a contact form — a form drops a message into an inbox that somebody opens tomorrow, while a widget answers now. And it is not a separate product from your Instagram or WhatsApp bot. On an omnichannel chatbot platform such as NERO, the website widget is simply one more channel wired to the same bot, the same knowledge base and the same unified inbox.

How the widget is generated inside the panel

When bots are built inside the panel itself, there is no external automation layer in the middle — no n8n, Make or Zapier subscription is required to run a standard website chat widget. The sequence is short.

1. Build the bot first. Load your frequently asked questions, catalogue, delivery rules and pricing logic into the knowledge base. This step takes the most time; the widget itself takes minutes.
2. Create the website channel. In the channels section, choose website chat. The panel creates a widget bound to your workspace.
3. Set the appearance. Colour, position (left or right corner), icon, widget title, and the name the bot introduces itself with.
4. Set the behaviour. Greeting message, delay before the bubble opens by itself, working hours, offline mode, and which contact fields to collect.
5. Copy the snippet. The panel gives you one code snippet. That is the whole installation package.
6. Paste it into the site. Put it before the closing body tag in the shared template so it loads on every page, then reload the site and send a test message.

Where the snippet goes depends on how your site is built. On WordPress it is the theme footer or a header-and-footer code plugin, on a store platform the theme layout file, on a hand-coded site the shared footer include, and on a visual builder the custom code area in site settings. In every case it is the same single snippet, pasted once.

Which pages should show the chat widget

The default answer is every page. You cannot predict where a search engine drops a visitor, and a widget that exists only on the home page misses most of the traffic. A few page types still deserve different treatment.

Page type	Widget	Reason
Home page	Yes, greeting after a short delay	Highest traffic, most undecided visitors
Product or service pages	Yes, with a page-specific greeting	Buying intent is highest here
Pricing page	Yes, open sooner	Most questions and most hesitation appear here
Blog and guide articles	Yes, quiet mode	Readers are researching; do not interrupt them
Contact page	Yes	Faster than the form the visitor was about to fill in
Checkout and payment steps	Usually off	Anything that covers a button costs you the order
Customer account or admin area	Off	These users need support tickets, not a sales bot

If you cannot control the widget page by page, keep it everywhere and soften the greeting instead.

Writing the greeting message

The greeting is the single setting most people get wrong. "Hello, how can I help you?" gives the visitor nothing to react to. A good greeting names what the visitor is looking at and offers a concrete next step.

• Be specific to the page. On a service page: "Want a price estimate for this service? Tell me the size and I will calculate it."
• Offer two or three buttons, not an open field. Most visitors click rather than type. Prices, delivery, book a time, talk to a person.
• Say who is answering. "You are chatting with our assistant. I can connect you to a colleague at any moment."
• Keep it under two lines. Long greetings get closed unread, especially on mobile.
• Delay the auto-open. A bubble that jumps out in the first second reads as an advertisement. Several seconds, or on scroll, works better.
• Do not promise what the bot cannot do. If it cannot check order status, do not offer to check order status.

Because the bot detects the visitor's language and replies in it, you do not need a separate widget for every market. Write the greeting in your main language and let the bot switch when a visitor writes in another one.

Working hours and offline mode

A chat widget has two different jobs depending on the clock, and both of them must be configured.

Inside working hours

The bot answers first. If the question falls outside its knowledge, or the visitor asks for a person, the conversation is handed to a live agent — the bot pauses and an operator continues in the same thread. The visitor sees no transfer and no context is lost. Set an internal target for how quickly an operator must pick up a handover; a widget that says "connecting you" and then stays silent is worse than no widget.

Outside working hours

Offline mode is the setting that pays for the whole project. Most enquiries arrive in the evening, at night and at weekends. The bot should keep answering the questions it knows, and for everything else collect a name and a contact number, state clearly when someone will reply, and store the conversation for the morning. Visitors accept "our team replies from nine in the morning" — they do not accept silence.

Set working hours in the panel rather than inside the greeting text. When the schedule changes you edit one field and every page follows. The biggest measurable gain from a website widget is usually not extra sales but the enquiries you stop losing overnight.

How the widget looks on a phone

Most website traffic is mobile, so the phone view is the real view. Check these points before launch.

• The bubble does not cover a call-to-action button, a cookie notice or the checkout total.
• Opening the chat fills the screen properly and the keyboard does not hide the input field.
• The close button is reachable with a thumb and actually closes the window.
• The widget does not noticeably slow the page down — it should load after the main content, not before it.
• Buttons and quick replies wrap onto narrow screens instead of being cut off.
• A visitor who leaves and comes back finds the same conversation, not a blank one.

One inbox for the website and every other channel

The reason to prefer a platform widget over a standalone chat script is what happens after the message is sent. A message from the website chat lands in the same unified inbox as Instagram DM, WhatsApp and Facebook Messenger. Your team works in one window instead of four, and a customer who wrote on Instagram yesterday and on the website today is one customer with one history.

It also means one bot to maintain. You update a price rule or a delivery term in the knowledge base once, and the website widget, WhatsApp and Instagram all start giving the new answer. Team roles decide who sees which channel, and analytics show which channel actually produces enquiries. More on the channel model is in our products overview and in the AI Media company profile.

Common mistakes, and when you do not need a widget

• Installing the widget before the content exists. An empty knowledge base produces a bot that says "I do not know" — worse than no chat at all.
• Two chat tools on one page. Remove the old script when you add the new one, or visitors will see two bubbles and write into the dead one.
• Nobody watching handovers. Decide who is responsible for the inbox before you go live.
• Auto-open on every page load. It irritates returning visitors. Open it once per session.
• Never reading the failed answers. The log of questions the bot could not answer is your improvement list; review it weekly for the first month.

And the honest part: you do not need a widget if your website gets almost no traffic. A bot cannot create visitors. In that case put the effort into the channels where your customers already write — usually Instagram or WhatsApp — and add the website widget later. You also do not need one if every enquiry is a complex custom negotiation. Our services page lists which route fits which situation, and the pricing page explains what a standard setup includes.

Next step

If your content is ready, a standard chatbot is built and handed over within about an hour, widget included. Tell us what your site sells and which questions eat your team's time, and we will say honestly whether a website widget, another channel, or a management system is the right first move. The first consultation costs nothing and carries no obligation.

Contact page · Message us on WhatsApp · Platform: app.aimedia.az · Phone: +994 50 250 00 74