Planning

WhatsApp on a website: button, form or chat

A WhatsApp link takes minutes; a chat widget is a project. Here are the options, what each tracks, the privacy points and the mistakes that cost enquiries.

Published 11 October 2026 · 4 min read

For many Indian businesses the real contact form is WhatsApp. Customers already have it, they are used to messaging a business on it, and a reply is quick. “Website with call and WhatsApp buttons” and “WhatsApp website integration” describe a need that is easy to meet at the basic level and easy to overbuild at the next.

A link that opens a chat with your number. On a phone it opens the WhatsApp app; on a computer it opens WhatsApp Web or the desktop app. The number is written in international format, for example 91 followed by the ten-digit number, with no spaces or symbols.

  • Good for: every business. It costs nothing and takes minutes.
  • Does not do: anything else. You do not know who tapped it, and no message exists until they write one.

The same link can carry text that appears in the message box, such as “Hi, I would like to ask about a website”. The customer reads it, edits it if they like and presses send.

  • Good for: knowing what an enquiry is about, and saving the customer typing. A different pre-filled message per page or per package tells you which page the enquiry came from.
  • Watch for: do not put anything private in it, and make sure the text reads well in the customer’s voice. They can change it.

Option 3: a form that opens WhatsApp

A short form (name, need, a few details) that builds the message from the answers and opens WhatsApp with it ready. The customer presses send.

  • Good for: getting the details you need in a consistent format.
  • How mine works: the enquiry form on the sites I build does exactly this. Nothing is stored on a server and nothing is sent until the customer presses send in WhatsApp, which the page says clearly.
  • Does not do: save or e-mail the enquiry for you. Storing or forwarding is backend work; see connecting website enquiries to a CRM or sheet.

Option 4: a chat widget or business integration

A floating chat panel, an automated greeting, quick replies or a link to a business account’s catalogue. Some of these use a business account provided by WhatsApp or by a reseller.

  • Good for: a business with a team answering many chats and a need for automation.
  • Costs: setup, a provider’s fees, and rules about message types and consent that the provider sets. It needs an account and often a backend, so it is not part of my packages unless agreed in a written proposal.
  • Watch for: a bot that answers badly is worse than a human who answers an hour later. See AI chatbot on a business website.

Counting WhatsApp enquiries honestly

A click on a WhatsApp button is a tap, not a message sent and not a sale. You can count taps with GA4 if tracking is set up; Growth and Complete include that setup with your account access, and Essential does not. For real enquiries, keep a list of chats you receive. Counting enquiries from WhatsApp and phone calls explains the limits.

Mistakes that cost enquiries

  1. The button only on the contact page. It should be within one tap on every page of a phone.
  2. A floating button that covers content or the form. Check it on a small screen.
  3. A wrong or old number. Test the link from a phone that does not know your number.
  4. No hours or expectations. Say when you reply, honestly.
  5. No call link beside it. Some customers prefer to call.
  6. A button that is only an icon. Give it a text label and an accessible name for screen readers.

What to do

Put a plain link and a pre-filled link on every page first. Add the form if you want consistent details. Treat everything beyond that as a project with a cost. If you would like a site with these routes built in, they come with every package; the details are on the pricing page, and you can message or call Harman.

CallWhatsApp