How to Add WhatsApp to a Company Website and Track Inquiries

The short version #

A WhatsApp button isn't decoration. It's its own conversion path, and it works only if you've decided which page the click came from, what the first message looks like when it lands in your phone, and who is supposed to reply within how many hours. Build the link as wa.me/<number>?text=<encoded> and tag it with UTM parameters. Pre-fill the message so the buyer doesn't have to type "hi". If several salespeople share one WhatsApp Business account, set up labels and Quick Replies before you ship the button. The cheat sheet at the end has placement and UTM naming for every common page type.

A real situation #

Last year we worked with a Zhejiang industrial pump exporter on their overseas site. The first version had a bouncing WhatsApp icon with a red dot in every page's bottom-right corner, copy reading "Chat now!". A month later, sales came back frustrated: 80% of inbound WhatsApp messages were a single word ("hi") with no follow-up, and the rest asked "What's the price of pump?" without telling anyone which product page they had been on.

We fixed it in three passes. The floating icon came off the homepage and blog and stayed only on product and service pages. The button now opens wa.me with UTM tags and a pre-filled message that names the product. Sales added product labels inside WhatsApp Business. The next month, total conversation volume dropped 30%, but conversations arriving with product context jumped from 20% to 65%. Sales stopped asking which pump someone had been looking at, because the buyer's first message already said so.

This article is the playbook from that cleanup, plus what's worked across a few more clients since.

Where the button goes #

Button placement isn't an aesthetics question. It's about whether the button shows up at the moment the buyer is deciding what to do next. Our default rules:

• Homepage: no WhatsApp button above the fold. The hero CTA stays as "Get a Quote" or "Contact Sales". One small WhatsApp link in the footer is enough.
• Service / product pages: a clear WhatsApp CTA at the bottom, next to the inquiry form. After the buyer reads specs, cases, and price ranges, the next step should be a clean fork: form or WhatsApp.
• Contact page: list form, email, WhatsApp, and office address together. Don't bury them in three different tabs.
• Footer: a small icon plus the number as text on every page, so people can copy it.
• Mobile floating button: fine, but only on product and service pages. A floating WhatsApp icon over a blog post or About page is just noise.

Skip "Chat now" as button copy. Overseas B2B buyers tune it out. Use a verb that names the next action: Talk to sales on WhatsApp, Ask about lead time, Request a quote on WhatsApp. The more specific the copy, the clearer the buyer is about what happens after they tap.

For how button copy fits with forms and case studies on the same page, see Corporate Website Conversion Checklist for More Inquiries.

Pre-filled messages #

The wa.me link supports a pre-filled message: https://wa.me/8613800000000?text=Hi%2C%20I%27m%20interested%20in.... Whether you write a good pre-fill decides whether the conversation starts with useful context.

A few templates we reuse:

• Product page: Hi, I'm interested in [Product Name] from [Company Website]. Could you share lead time and MOQ?
• Service page: Hi, I'd like to learn more about your [Service Name]. My company is in [Industry] and we're targeting [Market].
• Homepage / footer: Hi, I found your company on [yourbrand.com] and I'd like to discuss a project.
• Quote request: Hi, please send me a quote for [Product/SKU]. My target quantity is [Qty] for [Destination].

A few things that matter on the pre-fill itself.

The first sentence has to tell sales which page the buyer came from, either by naming the product or referencing "your service page". Otherwise the rep has to ask and the buyer has to repeat themselves, and you've already lost the rhythm. Leave one or two bracketed slots for the buyer to fill in. More than that and most people give up. Skip empty pleasantries like "Hi, I want to chat"; the whole point is to let the buyer skip the throat-clearing.

URL-encode the text properly. Spaces become %20, commas become %2C, apostrophes become %27. Hand-typing the encoded string breaks half the time. Use the templates in WhatsApp Business Setup Checklist for Overseas Sales and run them through an encoder once instead of editing them by hand.

Short links vs buttons vs QR codes #

Pick the format by where it's going to live.

• HTML buttons (in the website body): the link is https://wa.me/<number>?text=<encoded> directly. Browsers can right-click and copy it, you can attach UTM parameters, and analytics tools can read the click.
• Short links (e.g. wa.link/xxxx): email signatures, business cards, printed materials, PDF quotes. WhatsApp's official short links also support pre-filled text but don't accept UTM, so keep them off the website itself.
• QR codes: trade shows, product packaging, physical posters. Once printed, you can't change the pre-fill or attach UTM. Bake a fixed source code into the URL such as ?utm_source=tradeshow_2026q2 so you can at least tag the conversation batch later.

Rough rule: on the web, always use wa.me with UTM. Offline materials get short links or QR codes. PDF quotes get short links, because once a PDF is forwarded over email the UTM gets stripped anyway.

How to set UTM #

Tagging WhatsApp links works the same way as any outbound link. Append parameters after the wa.me URL:

https://wa.me/8613800000000?text=Hi%2C%20interested%20in%20Pump%20A
&utm_source=website
&utm_medium=whatsapp_button
&utm_campaign=pump-a-product-page
&utm_content=footer_cta

WhatsApp itself doesn't read the UTM tags. But GA4 records the user's session source on your site at the moment of the click, and if you also fire a GA4 outbound-link event you can later answer which product page, which campaign, and which CTA position the WhatsApp jumps came from.

Our naming scheme:

• utm_source = the site itself (website) or an external channel (linkedin, email, tradeshow)
• utm_medium = whatsapp_button / whatsapp_qr / whatsapp_link
• utm_campaign = the slug of the page or campaign (pump-a-product-page, going-global-it-service)
• utm_content = the button location (hero, footer, inline_cta, mobile_floating)

Same utm_campaign per page, different utm_content per position. Six months later you can read off something like "the inline CTA on product pages drives 4x more WhatsApp clicks than the floating button" without rebuilding any tracking. The full multi-channel pattern is in UTM Tracking for WhatsApp, X, Forms, and Email Leads.

For event tracking, attach a GA4 event: whatsapp_click to the button with the product SKU or service name as a parameter. Even when buyers tap and then never message, you still have a list of "people who almost messaged" you can use for retargeting.

Shared inbox #

The hardest part of WhatsApp on a B2B site usually isn't technical. It's how the sales team divides the inbox.

If one founder owns the phone, no problem. With five overseas reps sharing a WhatsApp Business account and 30 messages a day, you'll start losing leads inside a week unless someone owns the workflow.

Our defaults:

• Create labels in WhatsApp Business: new, quoting, sample-sent, waiting, closed-won, closed-lost. Every incoming message gets new first, then moves to quoting once a rep claims it.
• Set up Quick Replies for the obvious patterns: welcome, quote acknowledgement, polite nudge, out-of-hours autoresponder. Three sentences max each.
• WhatsApp's multi-device support caps you at four linked devices on one account. Beyond that you need WhatsApp Business API plus a CRM.
• Run a 15-minute Monday standup against the waiting label. Anything older than five days gets a named owner or gets archived.

The full sales handoff playbook lives in WhatsApp Sales Workflow Example. For the limits of the WhatsApp Business app itself, the official help center is the source of truth.

Don't be annoying #

A note for everyone treating WhatsApp like a magic traffic potion.

The moment your WhatsApp button becomes a sitewide floating, bouncing, red-dotted, auto-popping widget, the buyer's reflex is to close the tab. Things we've actually seen on client sites: a pop-up that fires three seconds into the homepage saying "Need help? Chat with us!" before the buyer has read the company name. A floating WhatsApp icon at the bottom-right that physically covers the mobile "Add to inquiry" button. A blog post with "Want a quote? WhatsApp us!" injected after every third paragraph, when the reader came for the article.

The healthier pattern is quieter. No WhatsApp entry on blog posts or informational pages. One clear CTA at the bottom of product and service pages. A mobile floating button that only appears on conversion-related pages. Any auto-popup gated on a real user action, like scrolling past 60% of the page.

Google's intrusive interstitials guidance doesn't target WhatsApp widgets directly, but the logic transfers. Anything that obstructs content hurts mobile experience signals.

Cheat sheet #

FAQ #

Do we have to use WhatsApp Business? #

Yes. Standard WhatsApp lacks catalog, Quick Replies, labels, and business hours. Buyers seeing the default "Hey there! I am using WhatsApp" status assume it's a personal line. Install the WhatsApp Business app at minimum; the API is only needed once you outgrow four linked devices.

What if buyers tap the button but don't actually send a message? #

Expect this. After WhatsApp opens, plenty of buyers hesitate, switch apps, or go email instead. Always keep an inquiry form on the same page as a fallback. Don't go all-in on WhatsApp. The normal ratio of GA4 whatsapp_click events to actual incoming conversations sits around 3:1 to 5:1.

Does iPhone behave differently from Android? #

The wa.me link opens a browser intermediary on both, then hands off to the app. If WhatsApp isn't installed, it sends the user to the download page. On desktop it opens WhatsApp Web or the desktop app, prompting a QR scan if they aren't logged in. The pre-filled text works the same on all three.

Anything to watch on privacy and compliance? #

WhatsApp conversations are governed by WhatsApp's own privacy terms. Don't claim "encrypted direct line" or other phrases that sound like a guarantee you can't make. If you operate in the EU, list WhatsApp in your privacy policy's third-party processors section, and disclose in your cookie banner that GA4 records the click event.

Get a diagnosis #

If you're rolling out an overseas site, or you've already shipped one but WhatsApp inquiries keep arriving without context, going unanswered, or never tying back to a campaign, send us your current button placements, your UTM naming sheet, and a week's worth of recent conversations. We'll run this cheat sheet with you in a free initial review under our overseas website build and SEO/GEO support service, and tell you which fixes are P0 (placement and UTM) versus what can wait until next quarter (full sales workflow and API).