An AI chat site earns its keep page by page, not site-wide. The same opening line on your homepage, your fees page and a careers page reaches three visitors with three different reasons for being there, and it fits none of them. This article answers one question: how do you decide where chat appears on your site, what it opens with on each kind of page, and how do you set that up on the levelpartner.ai platform so chat adds enquiries without getting in the way of the ones you already receive? Installing the widget in the first place is covered in adding AI chat to any website.
Why page context decides whether an AI chat site works
A visitor on a pricing page is close to a decision. A visitor halfway through a blog post is researching and will leave if interrupted. A visitor on a careers page is not a buyer at all, and one on a booking page is already doing the thing you want. A single "How can I help?" treats all four the same, and most of them close it.
Match the opening line to the page and the widget stops being decoration. On a fees page, "Questions about what is included or how onboarding runs? Ask here" invites a reply. On an article, a closed bubble with no greeting lets the reader finish. The configuration is a little more work, but it changes what the conversations are about.
Most AI chat sites get this wrong in the same way: one widget, one greeting, one agent, judged by the total number of chats. That number rises when the greeting is loud and falls when it is quiet, and it says nothing about whether the chats were with buyers.
Map the site before you touch any settings
Sort your pages into groups and give each group one goal. A typical split for a firm of 10 to 250 staff:
- Commercial pages: services, industries, pricing. Goal: a booked call.
- Proof pages: case studies, reviews, about, team. Goal: a question answered.
- Content pages: blog posts, guides, resources. Goal: stay out of the way, or offer something useful.
- Contact page: show chat, since people there already have a question.
- Task pages: booking, payment, forms, client login, careers, legal. Goal: no chat, or a closed bubble at most.
Agencies, consultants, mortgage brokers and real estate firms will word their greetings differently, but the page logic holds for all four. Write one greeting per group, short enough to read at a glance, and name the question the visitor is most likely to have.
Before you start
- A chat widget configured in Sites, with its contact form and office hours set. AI chatbot site covers the knowledge and tone behind it.
- An AI agent connected to the widget, if an agent answers first.
- Your page groups written down, with the pages or templates in each.
- One greeting per group, and a decision for each group: show the widget, or leave it off.
- Edit access to the pages in Sites, or to your website's templates if the site is built elsewhere.
How to set it up
The platform lets you choose one widget for a whole website or funnel, or place different widgets on individual pages. Each widget carries its own welcome message, so a page-specific greeting means a separate widget for that page group.
- Open Sites > Chat Widget and click + New.
- Choose the type of chat widget you want to create.
- Open Sites, then Websites or Funnels, and select the site.
- In the Settings tab, use the Chat Widget dropdown for the site-wide widget.
- Set the Chat Widget dropdown to None and click Save.
- In Sites > Chat Widgets, open the widget, click Get Code, copy it.
- Open the Page Editor for the target page.
- Click Add Element (+), find Code and drag it onto the canvas.
- Select the Code element, click Open Code Editor, paste and Save.
Steps 1 to 4 are enough if one widget should cover the whole site. Use steps 5 to 9 when page groups need different greetings: create one widget per group first, then place each group's snippet on its own pages. If an AI agent should answer, open the agent in AI Agents, turn on the Chat Widget channel on its Deploy tab and assign each widget you created. For a site built on another system, the copied snippet goes into the templates used by each page group rather than into a site-wide header or footer.
Writing greetings that suit each page
A service page for consultants: "Wondering whether we work with firms your size? Ask me." A fees page: "Want to know what onboarding involves? I can answer now." A case study: "Curious how this would apply to your firm? I can find you a time with the team." Each one names the likely question and offers one clear next step.
On content pages, either leave the welcome message out or offer something that fits reading, such as the checklist version of the article. A sales prompt in the middle of a guide reads as pressure and teaches visitors to close the bubble without looking.
Suppose one greeting on every page brings about 90 chats a month, roughly half from blog readers asking for free advice and very few from the pricing page. Now imagine three widgets: one for commercial pages, one for proof pages and a quiet one for the blog. Total chats might fall to around 70 while booked calls from chat climb from 6 to 13, because the conversations that remain would be with buyers. Fewer chats and more meetings is the pattern to look for.
A live chat widget for website pages on a phone
On a phone the bubble competes for the same space as your main button. A live chat widget for website visitors on mobile can cover the very call to action you want pressed, or sit on top of the cookie banner. Check every page group at phone width after placing the widgets. If the bubble overlaps something important, move it to the other corner in the widget's style settings or keep that group's widget closed with a single short line.
Switching on a greeting everywhere because the first week shows more chats. Read what those chats are. If most are off-topic or from people who are not buyers, the greeting is creating work rather than leads. Keep the louder greetings on commercial pages and let the rest of the site stay quiet.
Reading chats by the page they started on
Once page groups exist, the transcripts become research. If a service page keeps producing the same question about timescales, the page needs a paragraph on timescales. If proof pages produce almost nothing, the case studies may already answer what visitors need, and that is fine. Review one group a week and fix either the agent's knowledge or the page itself. For reviewing the agent's replies as they happen, see supervising AI chat in real time.
What it replaces and the time it takes
Page-level chat replaces the one-size-fits-all widget and the contact form at the foot of every page that few people complete. Planning the groups and greetings takes about an hour. Creating the widgets and placing them takes another hour or two, longer if an outside contractor manages your templates. After that, a short monthly review of chats by starting page keeps the greetings sharp.
When not to add chat to a page
Leave chat off pages where the visitor is completing a task: checkout, a booking calendar, a long form, client login. A bubble there splits attention away from the action you want. Leave it off careers and legal pages too. If your site has fewer than ten pages, or nearly all your traffic lands on one campaign page, one well-written greeting is enough and the extra widgets add little.
If nobody can answer the conversations an agent hands over during the hours a page gets most traffic, either let the agent handle that page fully or leave chat off it until you can.
Troubleshooting
The wrong greeting appears on a page. The page still inherits the site-wide widget. Set the site's Chat Widget dropdown to None, then check that only one snippet sits on that page.
Two chat bubbles show at once. An older chat tool, or a second copy of the snippet, is still loading. Remove the extra code so each page carries exactly one widget.
The widget still shows on a page where you removed it. On an external site the snippet sits in a shared header or footer. Move it into the templates for the page groups that should show it.
Blog readers ask for free consulting. Give the agent a polite boundary for detailed advice and have it offer a guide or a call instead.
Frequently asked questions
Should the chat bot site widget appear on every page?
No. A chat bot site works best when the widget shows where visitors are deciding, stays quiet where they are reading and stays away from pages where they are already converting. Keep it on commercial and contact pages at minimum.
Can different pages have different greetings?
Yes. Create one widget per greeting and place each widget's code on the pages it suits. One AI agent can answer in all of them if its instructions cover every page group, which is easier to maintain than several agents. Running chat across several separate domains is covered in chat bots for websites.
How many website chat widget versions should I create?
Start with one per page group, so three or four at most. More than that is hard to maintain and hard to measure. Add a page-specific version only for your busiest commercial pages.
How do I write an opening line people answer?
Make it specific to the page and ask a question the visitor already has. Conversational chatbot examples shows openings that work, and the AI chatbot website guide covers tone.