"Customer taps - message is already yours" - handy for briefs, not what happens technically. One click opens chat with prefilled text; the customer still taps Send. On mobile that's a fraction of a second; on desktop sometimes a full QR code and a closed tab.
After this article you'll have working button HTML, mobile vs desktop scenario clarity, and why button clicks can't count as leads in reports.
Mistake in the topic framing: "customer taps → WA opens with ready message → taps Send" presented as one seamless "one-click" flow, with "5 minutes for the webmaster."
Fix: technically only chat with prefilled text opens in one click. Sending is a separate in-app action - some users never reach it. Integration time is modest: basic HTML button takes 3–10 minutes - that part is fair. Link format details in wa.me article.
Minimal working implementation - plain link, no scripts or widgets:
<a href="https://wa.me/14155551234?text=Hi%21%20Please%20tell%20me%20about%20your%20service"
target="_blank"
rel="noopener noreferrer">
Chat on WhatsApp
</a>
target="_blank" and rel="noopener noreferrer" aren't cosmetic. First opens chat in a new tab without closing your site; second blocks Tabnabbing - where the new tab can rewrite the original page.
Same logic for other channels:
<a href="https://t.me/yourcompany">Message on Telegram</a>
<a href="tel:+14155551234">Call us</a>
User path - several steps, not one:
Site has no access to visitor's contacts or WhatsApp account - company learns name/number only after step 4 when message actually arrives. Until then - local device events the site can't verify.
Button click is intent, not an inquiry. Real send opens 24-hour inbound window - if auto-funnel is set up.
| Parameter | Mobile | Desktop |
|---|---|---|
| After click | Direct deep link to app | Intermediate page, then WhatsApp Web or QR |
| Click-to-send conversion | 70–85% practitioner observation | Up to 50–60% loss at WhatsApp Web step |
| vs Telegram | Comparable | Telegram ~40–50% higher on desktop - native app, no browser layer |
On phones WhatsApp is installed for nearly all messenger users - short path. On PC without Web session in that browser - QR scan; many drop off.
Law firm ran ads to landing with WhatsApp as sole CTA. Mobile lead conversion ~12%; desktop <1.5%. Session replay: PC users scared off by WhatsApp Web QR and closed the page.
Fix: channel picker - tel:, Telegram, WhatsApp. Overall site conversion leveled to 9.5%.
Desktop visitors need alternatives, not WhatsApp Web persuasion.
E-commerce set GTM goal on button click. Month report: 1000 leads; sales logged 600 inbound chats.
Click counted as send - different events. ~40% opened WhatsApp but erased prefilled text or closed without Send.
Label metric "WhatsApp button clicks" - not inquiries or leads - or sales and marketing argue over different numbers for the same channel.
tel: on smartphones opens Phone app cleanly. On PC without VoIP (Skype, FaceTime, corporate softphone) - "No application to handle link" - factor in if both tel: and WhatsApp target same desktop audience.
Telegram wins on desktop vs WhatsApp: native client opens without browser auth layer - practitioner observation in several markets.
Mobile UX: sticky button bottom-right - thumb zone. Plain HTML link beats heavy JS widgets for PageSpeed.
Trap: site opened in in-app WebView (Instagram, Facebook, Telegram) - wa.me may white-screen; social in-app browsers sometimes block third-party app handoff. No universal fix in open sources - test per traffic source.
Add basic button with code above; split analytics click vs real inquiry; show desktop alternative - call or Telegram - beside WhatsApp.
Practical rule:
One click opens the door, not the client in the room - they still send themselves, and analytics must remember that.