A chat bot for website visitors earns its place when it answers the question that would otherwise send someone back to the search results, then books the meeting or captures the lead while they are still on the page. On the levelpartner.ai platform the bot is a conversation agent connected to a chat widget, a calendar and your CRM, so every chat lands as a contact with the full transcript attached. This guide covers the whole first launch: what to prepare, how to build and connect the agent, where to place it, and how to run it each week.
What a website with chat bot coverage changes
Most company websites ask the visitor to do the work. Read three pages, find the contact form, wait a day for a reply. A website with chat bot coverage reverses that. The visitor asks in their own words and gets an answer in seconds, at any hour, followed by one sensible question back.
For a 60-person firm whose revenue has gone flat, the gain is rarely more traffic. It is fewer wasted visits. A form feels like a commitment and a phone call feels like an effort, so chat becomes the low-effort way to ask. The people already arriving get a reply, a booking link and a reason to stay, and your sales team starts the day with qualified conversations instead of an inbox of half-filled forms.
What a chat bot with AI does that a scripted one cannot
Older website bots follow buttons and fixed branches. A chat bot with AI reads the question as typed, answers from the knowledge you trained it on and decides what to ask next within the goals you set. That matters because visitors rarely phrase things the way a menu expects.
The difference that counts for a growing firm is what happens after the answer. A free plugin usually answers in isolation and emails you a transcript. Here the agent writes the contact to your CRM, books into your calendar and hands the thread to a colleague in the shared inbox, so nothing has to be copied between systems.
Before you start
- Permission to edit AI Agents, Sites and Calendars in the account.
- The ability to add one code snippet to your website, or a site already built in Sites.
- A calendar your sales or advisory team actually uses, with real availability.
- Your ten most common pre-sales questions and the answers you give on the phone.
- A named person who owns chat conversations during office hours, plus an out-of-hours rule.
- Your privacy notice updated to mention chat, checked by whoever owns compliance.
- Agreement on the one action you want the bot to drive, usually a booked call.
How to set it up
The build has two parts: create the agent, then connect it to a chat widget on your site.
Create the conversation agent
- Go to AI Agents > Conversation AI and click + Create Bot.
- Select Guided Form Setup.
- Click Create New Bot.
- Choose the bot type: Appointment Booking for a call-booking bot.
- Select or create a Brand Voice.
- Configure Bot Settings.
- Configure Bot Goals, including the booking calendar and contact details.
- Save the bot.
- Choose Suggestive as the bot's mode while you test.
Connect it to your website chat widget
- Go to Sites > Chat Widgets, create or open a widget and save it.
- Go to AI Agents > Conversation AI and open the bot.
- Select the Deploy tab and turn on Chat Widget.
- Open the Chat Widget channel's edit icon and turn on Assign channel.
- Select the widget and add tag conditions if needed.
- Click Update, save the bot and test the widget on your site.
Once five or six test chats from a phone and a laptop read well, including one that asks for a person, move the bot from Suggestive to Auto-Pilot. Check that each test contact appeared in Contacts with the conversation attached before you do.
Choosing what the bot should do first
An online chat bot for website traffic can try to do everything: support, sales, recruitment, complaints. Resist that. Pick one job for the first month and judge the bot on it.
For agencies and consultants the job is usually booking a discovery call. For mortgage brokers it is collecting enough detail to route the enquiry to the right adviser. For real estate it is capturing the property, the budget and the timescale, then booking a viewing or a valuation. A bot with one job improves quickly because every conversation teaches you something about that job.
Placement and the greeting
Put the widget where visitors have intent: service pages, pricing and contact. On blog posts it attracts curiosity questions and fewer buyers, so a quieter greeting or none suits those pages. Our guide to placing the bot page by page covers different widgets and greetings for different parts of a site.
Keep the greeting to one line that says what the bot helps with, for example "Ask me about our services, fees or availability." Leave the window closed until the visitor clicks it. Pop-ups that open by themselves on every page get closed by reflex and teach visitors to ignore the bubble.
What it replaces and what it costs in time
A working chat bot replaces the generic contact form on most pages, the out-of-hours voicemail for web enquiries and a fair share of first-reply emails. It does not replace your sales conversation. It shortens the gap before that conversation starts.
Launch takes about a working day if your answers are already written down, and most of that goes on training the bot, not on settings. Running it takes around thirty minutes a week: read the chats that ended without a booking or hand-off, add better answers where the bot was vague, and check that hand-offs were picked up within the hour.
Say the firm gets roughly 1,200 visits a month to its service pages and around 15 contact form submissions. A bot that answers scope questions and offers a call might start about 90 conversations a month; if 20 of those booked a call directly, chat would outperform the form. The form stays live for people who prefer it. Your own traffic and offer decide the real numbers.
Suppose the site gets 6,000 visits a month and 60 form enquiries. With the bot on listing and valuation pages only, it might handle around 150 chats a month. If about 40 of those became viewing or valuation bookings, they would come on top of the forms, not instead of them.
The common mistake is training the bot on the whole website and nothing else. Marketing pages are written to persuade, not to answer, so the bot gives vague, brochure-style replies. Add direct answers to the questions people actually ask, including the awkward ones about price and timescale, and the quality of replies changes within a day.
When not to add a chat bot
If nobody will read transcripts or pick up hand-offs within a working day, wait. A bot that promises a person and then delivers silence costs you more than no bot. If your services cannot be discussed without a formal fact-find, use the bot only to book that meeting. And if the site gets very few visits, fix the traffic first, because a bot cannot convert visitors who never arrive. For a wider comparison of approaches, see chat bots for websites.
Troubleshooting
The widget does not appear. The code was added to one page rather than the shared site template, or a cache is serving an old version. Add it site-wide and clear the cache.
The bot answers but never books. Appointment Booking is not enabled in Bot Goals, or the calendar has no availability in the next fortnight. Check both, then test a booking end to end.
Chats arrive but leads have no name or email. The bot offers the booking before asking for contact details. Make email or phone a required detail in Bot Goals so the contact is saved properly.
The bot strays into competitors or off-topic chat. It has no instruction on scope. Tell it to stay with your services and decline the rest politely.
Bookings land at odd hours. The calendar's time zone does not match your office. Check the calendar settings and the times shown to visitors.
Frequently asked questions
Do we need a new website for a chat bot?
No. The widget works on most existing websites through a short code snippet placed in the site's header or footer. If your site is built in Sites, you select the widget in the site's settings instead.
Will the bot tell visitors it is not a person?
It should, and you should set it up that way. Visitors accept an AI assistant that is honest and useful, and lose trust fast when they discover the "adviser" was software. The guide to AI customer support covers disclosure wording and escalation.
Can the same bot answer on WhatsApp and SMS?
Yes. The agent can be deployed to more than one channel, and conversations from each land in the same inbox. See building a WhatsApp chat bot for what that channel needs, and AI text messaging for continuing a chat by SMS once the visitor shares a number.
What happens to the conversation after the chat ends?
The contact, transcript and collected answers are saved to the CRM and can start a follow-up. The article on the automated chatbot explains how chat connects to workflows.