Add a floating WhatsApp chat widget to your website

Most website visitors who leave without buying were never against talking to you — they just hit a question your page did not answer, and the effort of finding a contact form felt bigger than closing the tab. A floating chat widget removes that friction. It is visible on every page without occupying layout space, it signals a real human is reachable, and it moves the conversation into WhatsApp, where people already spend their day and where your reply will actually be seen. Industry reports suggest chat entry points typically engage a meaningful single-digit percentage of visitors — small numbers on paper, but these are your highest-intent people: they had a question specific enough to ask.

Placement decides whether the widget helps or annoys. Bottom-right is the convention most visitors expect; bottom-left is the right call when the corner is already occupied by a cookie banner, a scroll-to-top control or a cart drawer. Whatever you choose, keep the launcher clear of your money moments: it must never cover a checkout button, a form submit or a sticky add-to-cart bar on mobile. On phones, also respect the system safe areas — a button flush against the bottom edge collides with gesture bars on modern devices, which is why the generated widget floats 20 px in from each edge. The welcome text deserves as much thought as the colour: a specific line such as “Ask us about sizing or delivery” consistently outperforms a generic “How can we help?” because it tells visitors what the chat is for.

Performance is the quiet reason this widget stays light. The embed is one async script tag: a small vanilla-JavaScript file with no frameworks, no trackers and no further network requests, rendering only after your page is interactive. Your configuration travels inside the tag itself, so changing a message means updating one attribute — no dashboard, no account. Because the pre-filled message can carry {{page_url}} and {{page_title}}, every conversation arrives with its context attached.

• Use WhatsApp green if instant recognition matters more than brand purity; use a brand colour when the widget must sit inside a tightly designed page.
• Keep the pre-filled message short and specific — it lowers the effort of sending that first message, and the URL parameters tell your team which page the chat came from.
• Auto-open sparingly: "open by default" with the 24-hour re-open policy respects visitors who closed it, which protects the widget's welcome.

Once chats start arriving, the widget is only the front door. Routing the same number through the WhatsApp Business API gives your team a shared inbox, chatbots for after-hours replies and reporting on every conversation the widget starts — which is exactly what InfiQ does.