You have chosen a chatbot, written the answers and pasted the script. One decision is left, and it is easy to get wrong: how the chat widget shows up. Position, timing and size decide whether it helps visitors or gets in their way, especially on a phone, where space is tight. This guide gives practical rules for placement, timing and mobile design, and a way to check your choices.
The Job of the Widget
A chat widget has two states: closed and open. Closed, it should be visible but quiet, a small signal that help exists. Open, it should be useful without hiding the page the visitor came to read. Almost every placement rule below follows from keeping those two jobs separate.
Position
Bottom right is the safest position for a chat widget, as long as it does not cover buttons or banners.
Bottom Right Is the Convention
Most visitors expect a chat button in the bottom-right corner. It is out of the way of main content on left-to-right sites and sits near the thumb on phones for right-handed users. Using the expected place means people find it without searching. Move it only for a reason, such as a cookie banner, a sticky checkout button or a right-to-left language layout.
Check for Collisions
The widget should never cover something important. Open your key pages and look for overlaps with:
- Sticky "Add to cart" or "Book now" buttons on mobile.
- Cookie or consent banners.
- Back-to-top buttons and other floating tools.
- Form submit buttons near the bottom of the page.
If something collides, move the widget's offset a little, or move the other element. A hidden "Buy" button costs more than a hidden chat button.
Timing
Let visitors open the chat themselves, or use one gentle, relevant prompt after they have had time to read.
Do Not Open Automatically Straight Away
A chat window that jumps open the moment a page loads is an interruption. Visitors have not had time to look around, and many close it without reading. A better default is to show the closed button and let visitors open it when they want help.
If You Use a Prompt, Make It Gentle
A small message above the button, such as "Questions about pricing?", can work if it appears after the visitor has had time to read, and if it is easy to dismiss and does not return on every page. Keep it relevant to the page. Consider showing it only once per visit.
Be Careful on High-Intent Pages
On checkout and booking pages, visitors are focused. Interruptions hurt. Keep the widget closed there, but make sure it is available if something goes wrong, such as a payment question.
Which Pages Should Have It?
The default is to show the widget on every page, because questions arise everywhere. You may still want to treat some pages differently:
| Page | Suggested approach |
|---|---|
| Home, services, pricing | Show the widget, with a greeting that matches the page |
| Product pages | Show it, with delivery and returns as starter questions |
| Checkout, booking | Keep it closed and quiet, but available |
| Contact | Show it, and offer the form or phone alongside |
| Legal pages | Optional; few visitors ask questions there |
Mobile
Most visits are on phones, so design for the small screen first.
- Keep the closed button small and tappable. It should be large enough to tap comfortably without covering content.
- Open to a sensible height. A full-screen chat window is fine on a phone, as long as the close button is obvious and easy to hit.
- Watch the keyboard. When the on-screen keyboard appears, the message box must stay visible and the latest message must not be hidden.
- Make links and starter questions easy to tap. Give them room so a thumb does not hit the wrong one.
- Test in both orientations. Landscape on a small phone leaves very little height.
Accessibility matters here too. Read chatbot accessibility: a practical checklist for keyboard, contrast and screen reader checks.
Size and Content
Keep the open window large enough for readable messages, but not so large that it takes over a desktop screen. Short answers with a clear first line work best in a narrow window. Rich answers, with bullets, bold text and links, are easier to scan than paragraphs. A welcome message and a few starter questions make the first screen useful; see chatbot welcome messages that get visitors to reply.
Branding Without Distraction
Match your brand colours so the widget feels part of the site, but keep contrast readable. A pretty button that people cannot see against the background is not helping. Avoid animation that keeps moving; a small, calm indicator is enough.
A Simple Test Routine
Test the widget on a real phone and a laptop, on your three most important pages, and ask someone new to find it.
- 1Open your three most important pages on a real phone and a laptop.
- 2Check that the closed widget does not cover any button or text.
- 3Open the chat, ask a question and close it again with one hand.
- 4Rotate the phone and repeat.
- 5Ask a colleague who has never seen your site to find the chat and ask something. Watch where they hesitate.
Pro Tip: Change one thing at a time and give it a couple of weeks. If you change the position, the greeting and the timing together, you will not know which one made the difference.
Common Mistakes
The usual mistakes are auto-opening on every page, covering purchase buttons, tiny close buttons, low-contrast colours and hiding contact details.
- Opening the chat automatically on every page.
- Covering a purchase or booking button on mobile.
- Making the close button tiny.
- Using brand colours with poor contrast.
- Hiding the contact page's phone number behind the chat.
What to Watch After You Change Something
After a widget change, watch how many visitors open the chat, what they ask and whether the questions match what your bot can answer. These three signals show whether the change helped.
- Opens: are more or fewer visitors opening the chat after the change?
- First messages: do they tap a starter question or type their own?
- Unanswered questions: does the list grow with new topics, or repeat old ones?
Wait a couple of weeks before judging, because traffic varies. Change one thing at a time and write down the date, so you can connect any shift to the change that caused it.
Questions to Ask Your Team Before You Decide
Ask your team where they would expect the chat button, which pages are most important and whether any page has floating elements that could collide. People who use the site daily notice problems quickly.
- Which pages bring in the most enquiries or sales?
- Which floating buttons or banners already exist on the page?
- What do we want visitors on checkout and booking pages to see?
Conclusion
Put the widget where visitors expect it, usually bottom right, check that it never covers important buttons, let visitors open it themselves or use a gentle, relevant prompt, keep checkout quiet but available and design for the phone first. Test it on real devices and change one thing at a time.
Key takeaways
- Bottom right is the expected position; move it only to avoid collisions.
- Never let the widget cover buy, book, consent or submit buttons.
- Avoid opening automatically on page load; use gentle, relevant prompts if any.
- Design for phones first: tappable button, visible close, keyboard-safe message box.
- Test on real devices and change one thing at a time.
Quick Summary
Chat widget placement follows a few rules: keep it bottom right where visitors expect it, make sure it never covers buy, book or consent buttons, let visitors open it themselves rather than popping up automatically, and design for the phone first with a tappable button, an obvious close button and a message box that stays visible above the keyboard. Test on real devices and change one setting at a time.
Want to see grounded answers on your own site?
Start free, add your Q&A pairs and paste one script tag. No credit card required.

Founder & CEO
Writes about grounded AI chatbots for websites: how they work, how to measure them and what to check before you buy.
Topics
Get new posts by email
Guides on AI chatbots for websites, straight to your inbox.
