AI webchat: what it is and what your website chat should have
What a webchat is, how it differs from live chat and a WhatsApp button, how it's installed on a website and what it needs to answer well with AI.
In a nutshell
A webchat is a chat window inside a website: the visitor types right there and gets an answer without leaving the page or opening another app. A person, an AI assistant or both can handle it, and today it's installed by pasting one line of code.
What a webchat is
A webchat (also written web chat) is the chat window that appears on a website, almost always as a floating button in a corner. The visitor taps it, types a question and gets the answer in that same window, without leaving the page, installing anything or handing over a phone number.
On the other side there can be a person replying live, an assistant with artificial intelligence, or a combination: the AI answers the common questions and passes the conversation to someone on the team when needed. Technically it's a snippet of code the site loads that talks to an external service; for the visitor it's simply a chat.
- Works in the browser, on desktop and on mobile.
- No app to download and no account to create.
- The conversation stays on record for the business instead of getting lost in an email.
Webchat, live chat, chatbot and WhatsApp button: how they differ
All four coexist on websites and get mixed up often. Live chat is a webchat handled only by people: if nobody is online, the visitor waits or leaves a message. A chatbot is the program that replies on its own; it can live inside a webchat or on WhatsApp. And a WhatsApp button is not a chat on the site: it's a link that sends the visitor out to the WhatsApp app.
An AI webchat combines the best of the three: it's available at any hour like a chatbot, lets a person step in like live chat, and doesn't force a switch to another app. The WhatsApp button is still useful when you want the conversation to continue on the customer's phone; many sites use both.
- Live chat: people, and it depends on someone being online.
- Chatbot: automatic replies, with or without AI, on any channel.
- WhatsApp button: a link to the app, not a chat on the page.
- AI webchat: answers on the page and hands off to a person when needed.
Organize your team's customer service in one inbox.
Assign each conversation to an owner and keep track of everything the team still has pending.
What it's for on a website and when you don't need it
It's useful when the site gets the same questions over and over: prices, hours, shipping, availability, how to get started. Also when the person is about to decide and one unanswered doubt makes them leave. And it's useful for capturing a contact in the moment, instead of hoping they fill in a form.
You don't need it when the site is a brochure page that gets no inquiries, when nobody is going to check the inbox or load information, or when volume is so low that an email or a WhatsApp button is enough. A chat with a greeting nobody answers looks worse than having no chat at all.
- Online store: stock, shipping, returns and payment methods.
- Professional services: scope, appointments and first contact.
- Your own systems and platforms: support for users who are already inside.
- Institutional site with no inquiries: it probably doesn't need one.
What it needs to answer well
First comes the business information: an AI webchat answers well only if it has somewhere to get the answer from. Prices, policies, hours and frequently asked questions, loaded and current, are worth more than any tone adjustment. Second is knowing what not to answer: when there's no backing, it should acknowledge it and offer to have someone on the team continue.
Third is continuity: the conversation should land in an inbox where a person can read it and take it over, and that person's reply should show up for the visitor in the same chat. In Volga the webchat assistant uses the same information as the WhatsApp one, every conversation enters the inbox labeled “Web chat”, and if your team replies from there, the visitor sees it in their window as long as it's open.
- Business information loaded and kept up to date.
- Clear limits: it acknowledges what it doesn't know and doesn't make it up.
- A shared inbox and a handoff to a person without losing the history.
- Options to pick with one click when the journey is always the same.
How it's installed on a website
In most tools the installation is the same: the provider gives you a snippet of code (a script tag) and you paste it into the site's template so it shows up on every page. On WordPress it's done with a plugin that inserts code in the footer; on a store or your own system, in the main template. No programming required.
In Volga the webchat is included from the Starter plan. From the dashboard you generate a credential, list the domains where it may run (if someone copies the code onto another site, it won't respond), choose the greeting language and copy a single script tag. The dashboard includes instructions for HTML, WordPress and Google Tag Manager, plus a live preview to try it before pasting it.
The appearance is adjusted in the same place: color, window title, opening greeting, button icon, bottom-right or bottom-left corner, and a sound when a reply arrives. The chat is isolated from the rest of the page, so it doesn't change the site's styles and the site doesn't change the chat's. If you'd rather open it from your own button, you can hide the floating one.
- One snippet of code, pasted once into the site's template.
- Authorized domains: the code only works where you enabled it.
- Customization with a live preview; changes save on their own.
- Optional anti-bot protection, which the Volga team turns on at your request.
Lead capture and languages
Asking for details in conversation works better than a form, but only with a reason: sending a proposal, coordinating with the team or continuing on another channel. In Volga, with lead capture turned on, when the visitor shows intent to move forward and leaves an email or phone number, the assistant saves them as a lead, with their name if given and with the history; it doesn't put the visitor through a questionnaire.
Language is handled in two layers. The window's texts (greeting, send button, notices) appear in the language you choose when installing it or in the page's language. The assistant's replies follow the language the visitor writes in: if they write in English, they get an answer in English, even if your information is loaded in Spanish.
- Minimal data, with a clear purpose.
- The contact stays in the inbox and in leads, with the full conversation.
- Interface in Spanish, English or Portuguese, depending on how you install it.
- Replies in the visitor's language.
How to measure whether it works
Three numbers are enough to start: how many conversations the chat opened, how many contacts it captured, and what share of conversations ended in a contact. If the first one grows and the second doesn't, the chat talks but doesn't convert: review what it asks for and when.
Then look at quality: read a sample of conversations each week, find the questions the assistant couldn't answer and load that information. Volga shows conversations and contacts for the last 30 days in the widget dashboard, and the ratio between them; and if you turn on attribution, it records which campaign or page each visitor came from (UTM parameters and landing page) on the conversation and on the contact.
- Conversations per day.
- Contacts captured and conversion rate.
- Unanswered questions: the list of what's missing.
- Where the visit came from, when you run campaigns.
Continuity with the rest of your channels
A webchat shouldn't be an island. If the same business also serves customers on WhatsApp and Instagram, the sensible thing is for the assistant to use the same information on all three channels and for the team to work in a single inbox, instead of checking three tools. That's what people usually call multichannel chat or a multichannel assistant.
In Volga the website conversation enters the same inbox as WhatsApp and Instagram, with the same information and the same team. And you don't need WhatsApp to get started: you can begin with the webchat alone and add the other channels later, without loading anything again.
- One information base for every channel.
- One inbox, with the channel labeled on each conversation.
- The same handoff rules and the same team.
- Start with the website and add WhatsApp or Instagram later.
Step by step in Volga
In Web Widget you tap «Generate credential», type your site's domain under «Authorized domains» and pick the window's color and title; changes save on their own. Then you copy the code with «Copy» and paste it into your site: the dashboard includes the steps for HTML, WordPress and Google Tag Manager, plus a «Live preview» to try it first.
From then on the chat answers on its own, at any hour, with what you loaded in Knowledge: the same prices and shipping it uses on WhatsApp. If the visitor wants to move forward and leaves their name and phone, Leads keeps the contact with what they asked for and the site they wrote from; «View conversation» shows the whole chat and «WhatsApp chat» lets you write to their number.
If they ask to talk to a person, you get the «A customer wants to talk to a person» alert in the dashboard bell and in the mobile app. «Go to chat» opens the conversation in the Inbox, next to your WhatsApp ones; you take it with «Take», and what you write shows up in the website chat while they keep the window open.
And if they had already written to you on WhatsApp, they can confirm it: when they say so in the chat, they get a code and an «Open WhatsApp» button that opens WhatsApp with the code ready to send to you. The code expires in 15 minutes. Volga replies on WhatsApp with a «Yes, it was me» button and, once they tap it, the website chat lands on the same contact record: in Contacts, «Details» shows both linked identities. This needs your WhatsApp connected to Volga, and the assistant doesn't show on the website what was said on WhatsApp.
- The credential, the authorized domains, the color and the code to paste.
- Answers with your prices and shipping, at any hour.
- The lead with the name, the phone and what they asked for.
- The alert when someone asks for a person, «Take» and the reply in the website chat.
- WhatsApp verification and the contact record with both conversations.
Frequently asked questions
Questions about this guide
Does the webchat replace the site's pages?
No. Important answers should also exist as public, navigable and indexable content: the chat helps whoever is already on the page, not whoever is still searching.
What happens if someone writes outside business hours?
If the AI answers, it does so at any hour. If the inquiry is left for a person (an options menu, a handoff or a plan without AI), Volga can prepend an out-of-hours notice that you set up together with your business hours; it's sent once and not repeated on every message.
Can visitors send photos or voice notes through the webchat?
Photos yes: on the Scale and Enterprise plans you can let visitors attach photos, with bot protection turned on, and the AI looks at them to reply. Voice notes no: if an inquiry needs one, it's best to continue it on WhatsApp.
Does the visitor have to start over if they reload the page?
No. The conversation is saved in their browser and picks up where it was if they reload or move to another page on the same site. From another device it starts fresh, unless your platform has logged-in users and identifies them.