The WhatsApp widget that turns visitors into conversations.

A WhatsApp widget is a click-to-chat launcher. It renders a floating button, bar, or tab on your site, optionally opens a small chat-styled panel with a greeting, and then hands the visitor off to WhatsApp with a link of the form https://wa.me/<phone-number>?text=<url-encoded message>. Nothing is sent from your server, no message leaves the visitor's device until they press send in WhatsApp itself, and no third party sits between you and the conversation. That is the important part: the widget is a very well-dressed link. What it is not is a helpdesk. There is no shared inbox, no ticket queue, no SLA timer, no canned-response library, no chatbot, and no agent-assignment engine. Messages arrive in whichever WhatsApp account owns the number you entered, exactly as if the visitor had typed the number in by hand. For the overwhelming majority of small businesses, storefronts, clinics, agencies, and local services, that is not a limitation, it is the point. You already answer WhatsApp all day. The widget just removes the step where the visitor has to find your number.

Every layout in the Poper WhatsApp widget resolves to the same primitive: a wa.me link. The number is normalised to digits only, in full international format, with no plus sign, no spaces, no dashes, and no leading zeros. A UK number written as +44 7700 900123 becomes 447700900123. An Indian number written as +91 98765 43210 becomes 919876543210. The prefilled message is URL-encoded and appended as the text query parameter, which is why a message containing an emoji, an apostrophe, or a line break still arrives intact. When the visitor taps the button on a phone, the operating system matches the wa.me domain to the installed WhatsApp app and opens the thread directly. On a desktop browser, the same link resolves to WhatsApp Web or the WhatsApp desktop app, depending on what the visitor has signed into. If they have no WhatsApp at all, they get WhatsApp's own landing page rather than a broken tab. You do not control that final hop, and you should not want to: it is what makes the same button work on every device without device detection, app-store deep links, or a fallback maze. One practical consequence: because the message is prefilled rather than sent, the visitor can always edit it before sending. Treat the prefilled text as a helpful starting point and a routing label, never as a form submission you can rely on arriving verbatim.

Nine layouts sounds like a lot until you match them to intent. Classic is the default and the safest choice for a general business site: a floating panel with a header, a greeting, a typing indicator, and a real message box, which reads as a live chat and sets the expectation that a human is there. Bubble strips that back to a small round launcher and a compact popover, which suits content-heavy sites and blogs where a full panel would compete with the page. Greeting proactively slides a welcome bubble in from the side with an unread badge, which is the highest-attention option and the one to use on a landing page where chat is the primary conversion action. Agent leads with a named person, a role, and an avatar, which is the right call for advisers, consultants, brokers, and anyone whose credibility is personal rather than corporate. Quick Replies replaces the message box with topic pills, each carrying its own prefilled message and optionally its own number, which is the highest-signal layout because every incoming chat is pre-categorised. Side Tab pins a slim vertical tab to the left or right edge, staying visible without covering content on long pages. Sticky Bar docks a full-width bar to the top, bottom, left, or right edge, which works well for announcements and for mobile-first sites where a corner bubble competes with a sticky add-to-cart button. Team lists your contacts, each with their own WhatsApp number, so the visitor self-routes to sales, support, or billing before the first message. Spotlight is a glossy branded hero with a headline and subtitle, best used on a dedicated contact page rather than site-wide. If you cannot decide, start with Classic, then switch to Quick Replies once you see which three questions arrive most often.

Three short strings do most of the conversion work in a WhatsApp widget, and most sites get all three wrong. The greeting is what the visitor reads inside the panel before they commit. 'Hi! How can we help you today?' is fine, but a specific greeting is better: 'Questions about sizing, stock, or delivery? Message us and we'll answer today.' The prefilled message is what the visitor sends you, and it should be written from their side of the conversation, in their voice, and specific enough to route: 'Hi! I have a question about the Florence tote' beats 'Hi'. On a product page, include the product; on an order page, include the order number; on a listing page, include the address. The reply-time caption is the one to be honest about. 'Typically replies within minutes' is a promise, and it is visible at exactly the moment the visitor decides whether to bother. If you answer within the hour, say within the hour. If you close at six, consider wording that survives the night, because the widget does not switch captions on a schedule. An overpromised reply time costs more trust than a modest one ever wins. Finally, label the launcher itself with a verb: 'Chat on WhatsApp' or 'Message the shop' outperforms a bare icon on desktop, though the icon alone is usually enough on mobile where the green glyph is instantly recognisable.

The free click-to-chat approach has a ceiling, and it is worth knowing where it sits. A wa.me widget cannot send outbound messages, cannot deliver order confirmations or shipping notifications automatically, cannot run a chatbot or automated flow, cannot show you analytics on message volume or response time, cannot support many agents working one number from separate inboxes, and cannot carry the green verified business badge. All of those need the WhatsApp Business API, which means Meta business verification, a Business Solution Provider such as Twilio, 360dialog, or Wati, approved message templates for anything you send first, and per-conversation pricing. That stack starts to make sense somewhere north of roughly a hundred conversations a day, or as soon as you need automated transactional messages. Below that, it is overhead: setup takes weeks, templates need approval, and you pay per conversation for volume you could have answered from a phone. A useful sequence is to start with the widget, watch which questions actually arrive and how many, and only move to the API when the volume or the automation requirement is real. Nothing is wasted if you do: the button and its prefilled messages stay exactly where they are, and only the number behind them changes.

Placement is the last mile. Bottom-right is the convention and the safe default, but check it against whatever else lives in that corner: cookie banners, back-to-top buttons, sticky add-to-cart bars, and cart drawers all fight for the same pixels on mobile. If your store has a sticky checkout bar, move the launcher to bottom-left or switch to the Side Tab layout. Test on a real phone at 375px wide, not just a resized desktop window. On performance, the widget is a small script and an SVG glyph, not an embedded third-party chat runtime, so there is no socket connection, no polling, and no vendor SDK loading on every page. Still, measure it: run PageSpeed Insights on your own page after embedding and confirm Largest Contentful Paint and Cumulative Layout Shift are where you want them. On privacy, the widget itself does not collect visitor data, but tapping the button sends the visitor to WhatsApp, and from that point Meta's own terms apply to the conversation. Say so in your privacy policy, mention WhatsApp by name as a channel you use, and if you operate under GDPR or a similar regime, make sure your consent banner and privacy notice reflect that a third-party messaging service is involved. Poper publishes a full GDPR statement at poper.ai/legal/gdpr/.