How to Integrate WhatsApp Into a Business Website: Forms, Chat and CRM

In this guide:

• The ways to add WhatsApp to a website
• Click to chat links: the wa.me format
• Chat buttons and widgets
• WhatsApp Business app vs the WhatsApp Business Platform
• Every method compared in one table
• How website forms work with WhatsApp
• Connecting WhatsApp to your CRM
• Tracking WhatsApp leads in GA4
• Which one do you need?
• Frequently asked questions

What are the ways to add WhatsApp to a website?

There are two layers to decide. On the website, you choose how visitors reach you: a wa.me link, a branded button or widget, or a form that hands over to WhatsApp. Behind the website, you choose where the chat lands: the WhatsApp Business app on one number, or the WhatsApp Business Platform connected to your CRM.

Much of the confusion comes from mixing the two layers. A green floating button can open a chat on the owner's phone, or it can start a conversation that is logged against a lead record, assigned to a salesperson and counted in your reports. Visitors see the same button. Your team gets a very different setup.

Click to chat links: the wa.me format

Click to chat is an ordinary web link that opens a WhatsApp conversation with your number. The format comes from WhatsApp's own help page: https://wa.me/ plus the complete number written the international way, without zeroes, brackets or dashes. It works on phones and on WhatsApp Web.

For a UAE mobile number, that means the country code 971 followed by the number without its leading 0. A link to a number written locally as 05X XXX XXXX becomes: 

You can also add a pre-filled message. WhatsApp says the text appears automatically in the chat's text field, as long as it is URL-encoded (a space becomes %20). This is more useful than it looks. Write a different message for each service page, and your team can see which page the chat came from before they reply:

Two checks before you publish: open the link on a phone that does not have your number saved, and confirm the number has an active WhatsApp account. The help page notes that the person you are linking to must have one, so a number without WhatsApp will not open a chat.

Chat buttons and widgets: what they add

A chat button or widget is the visible part of a WhatsApp link: an icon, a branded button or a small chat box that floats on every page. It makes WhatsApp easier to find, especially on mobile. It does not change what happens after the tap unless the tool behind it is connected to the WhatsApp Business Platform.

WhatsApp offers its own branded Chat on WhatsApp button in green or white and in small, medium and large sizes. Its usage guidance is short: use the button as it is, without changing it, keep it visible and easy to read, and use the latest version. WhatsApp lists contact pages, landing pages and the mobile version of your site among the places to use it. The button is currently available in English only. In code, it is simply an image inside the same wa.me link shown above.

Third-party widgets can add extras, such as a greeting bubble or a choice of team members to message. Before you install one, check three things:

• What it opens. Click it and look at the address. If it goes to wa.me, the widget is a styled click to chat link. If it connects to a messaging account, it is part of a platform setup and the provider needs access to your WhatsApp business account.
• Whether it uses official access. Meta's developer documentation says "using unauthorized third-party tools is prohibited", so pick tools that work through the official WhatsApp Business Platform.
• What it loads. A widget is a script on every page. Test your key pages on a phone after installing it, and remove it if the page feels slower or the button covers your own call to action.

One small search trap: the WhatsApp Help Center article about widgets is about adding a WhatsApp widget to your phone's home screen, not to a website. Website widgets come from plugins, your CRM or your developer.

WhatsApp Business app vs the WhatsApp Business Platform

The WhatsApp Business app is a standalone app for one-to-one conversations, run by the owner or a small team. The WhatsApp Business Platform is a set of APIs, including the Cloud API, that connects your WhatsApp number to software such as a CRM, a shared inbox or your own system. Your website can link to either.

WhatsApp describes the Business app as "built with the small business owner in mind". You get a business profile, a way to show your products and services, and messages that greet people when they start a chat or reply when you are away. Conversations stay one-to-one, answered in the app.

The Platform is described as enterprise-level WhatsApp APIs. Its customer care use cases include routing a chat to a live agent only when needed, and integrating with back-end systems like CRM and marketing automation platforms. Other listed uses are order confirmations, shipment updates and appointment reminders, plus automated flows and interactive messages with buttons, product lists and rich media. Those automated flows are the building blocks of a WhatsApp chatbot: a guided conversation that answers common questions and hands over to a person when needed. Meta's developer documentation lists the Cloud API for sending and receiving messages from your business phone number, and the Business Management API for managing accounts and templates. When people say "WhatsApp Business API", this is the platform they mean.

WhatsApp gives two ways to set up the Platform:

• Partner integration. You sign up through a WhatsApp partner, which handles the technical setup with little or no code.
• Direct integration. You connect directly and send from your own phone number. WhatsApp says this suits businesses that have developers who can integrate the Platform and want full control.

Three rules of the Platform shape how a website integration works:

• Customers start, you reply. When a customer messages you, a 24-hour customer service window opens and you can reply freely inside it.
• Messages you start use templates. Meta says templates generally require approval and are the only type of message you can send outside that window.
• Opt-in comes first. You must get a user's opt-in before sending templates, and the opt-in must make your business name and intent clear.

You do not always have to choose one or the other for ever. Meta's overview says businesses can use the Business app and the API with the same phone number, and its getting started guide explains how existing app users can connect their number to the Cloud API. Check your CRM's own rules first, though: Zoho CRM's help page says only unused phone numbers can be used for its integration.

Every method compared in one table

The right method depends on who replies, whether leads need to be recorded and how much you want to measure. A link is the simplest to set up but keeps no record of the conversation. The Business app suits one person replying. The Platform, through a partner, a CRM or your own build, suits teams that need ownership, history and reporting.

How do website forms work with WhatsApp?

A form and WhatsApp can work together in three ways: the form saves the lead and alerts your sales team on WhatsApp, the form sends the customer a WhatsApp confirmation, or the form opens WhatsApp with the visitor's answers already typed. The first two need the Platform. The third needs only a link.

1. Form to CRM, alert on WhatsApp. The visitor fills in the form, the lead is saved in your CRM, and a message goes to the salesperson's WhatsApp so nobody waits for an email to be opened. This is the setup we build on landing pages for businesses that sell through WhatsApp, with the lead also going to tools like HubSpot, Zoho CRM, Salesforce or a custom webhook. Because your system starts these alerts, plan for approved message templates.
2. Form to CRM, confirmation to the customer. The form thanks the visitor on WhatsApp and gives the next step. Add a clear opt-in on the form that names your business and says what you will send, because Meta requires opt-in before you send templates.
3. Form that opens WhatsApp. A short script turns the visitor's answers into a pre-filled wa.me message, and the visitor sends it from their own phone. There is no API to set up, but the answers only exist inside WhatsApp, so save the submission to your CRM or inbox at the same time if you want a record.

Connecting WhatsApp to your CRM

A WhatsApp CRM integration runs through the WhatsApp Business Platform, using either the CRM's built-in connector or a custom build on the Cloud API and webhooks. Once connected, each chat lands in a team inbox, attached to a lead or contact, assigned to a person and kept with its full history.

The built-in route is the quickest to explain. In Zoho CRM, an administrator starts the integration, and you need a Facebook Business Manager account, a verified business, a WhatsApp Business account and a registered phone number. During setup you choose whether new chats are added as Leads or Contacts and which users, groups or roles they are assigned to. Zoho also notes that once your business is verified, it is reviewed for compliance with the WhatsApp Terms of Service and Commerce Policy, so leave room in the plan for business verification. Messages you start from Zoho use approved templates in two categories: Utility, such as an order confirmation, and Marketing, such as a welcome text or a follow-up survey. HubSpot puts WhatsApp conversations in its shared inbox, keeps the conversation history for every customer, and lets your team reply in HubSpot or in the WhatsApp Business app on the same number, with conversations syncing automatically.

The custom route makes sense when your CRM has no WhatsApp integration, or when chats need to reach more than one system. Meta's documentation explains that the platform relies heavily on webhooks: every incoming message is delivered to your server as a webhook, and your code decides what to create, update or alert. This is API integration work: connecting the website, WhatsApp and the CRM so data moves without anyone copying it across by hand.

• Whichever route you take, decide these before anyone writes code:
• Does a new chat create a lead, a contact or both?
• Who owns a chat that arrives outside working hours?
• Which field records the page or campaign the chat came from?
• Which messages will you start, and which approved templates do they need?
• How does a chat become a qualified lead, and who marks it?

How to track WhatsApp leads in GA4

GA4 can count WhatsApp clicks without extra code. With enhanced measurement on, a click on a wa.me link is recorded as an outbound "click" event with the link URL and domain. For cleaner reporting, also send the recommended generate_lead event on each WhatsApp click, mark it as a key event, and confirm it in DebugView.

Google's enhanced measurement records an outbound click each time a user clicks a link that leads away from the current domain, with parameters such as link_domain and link_url. A wa.me link qualifies, so you can filter clicks where the link domain is wa.me. The same feature records form_start and form_submit for forms.

Outbound clicks mix WhatsApp with every other external link, so add a clear lead event as well. Google's list of recommended events includes generate_lead, triggered when a user "submits a form or a request for information". A WhatsApp click is a request for information, so send generate_lead with a parameter that says which method was used, for example whatsapp, form or call. Then:

• Mark generate_lead as a key event in Admin, under Data display, then Events. Standard properties can have up to 30 key events, and the change applies from the day you make it, not to past data.
• Click every WhatsApp button on the site yourself and confirm each click arrives once in DebugView or the Realtime report.
• If a widget opens WhatsApp with a script instead of a normal link, check that the click still appears. If it does not, add a custom event for it.
• Count each click once. If generate_lead is your key event, do not also mark the outbound click event as one.

A click shows intent; it does not prove a conversation happened. The rest of the funnel lives in your CRM. Google's lead generation events, qualify_lead, working_lead and close_convert_lead, are suited to conversions that happen offline, and sending them fills the Lead acquisition report. Connecting those CRM stages back to GA4 is part of how we set up GA4 tracking for every lead action, so WhatsApp clicks sit next to form submissions and calls in the same reports.

On the WhatsApp side, the Platform keeps its own numbers. Meta lists account analytics in the Business Management API, including how many messages were sent and delivered and how often template buttons were clicked. Use them to check message delivery, and keep GA4 and your CRM as the record of where leads came from.

Which one do you need?

Choose by how many people reply and what you need to record. If one person replies and you only need to know that chats are coming in, a wa.me link plus the Business app is enough. If several people reply and every enquiry needs an owner and a history, connect the number to your CRM through the Platform.
Use this checklist:

• One person answers, few chats a day: click to chat link or the official button, the WhatsApp Business app, and generate_lead tracked in GA4.
• A sales team shares the enquiries: the Business Platform through your CRM's integration, so chats are assigned and kept on the lead record.
• A support team answers existing customers: the Platform with automated flows for common questions and routing to a person when needed.
• Forms need an instant WhatsApp alert or confirmation: the Platform with approved templates, plus a clear opt-in on the form.
• Your CRM has no WhatsApp integration, or several systems need the data: a direct Cloud API integration with webhooks.
• Every option: a business number rather than a personal one, a pre-filled message per page, and a test from a phone that does not have your number saved.

Getting the build right

WhatsApp works best on a website when it is planned with the forms, the CRM and the tracking, not added as a plugin at the end. On our web development projects, integrations such as CRM, WhatsApp Business API and booking systems are configured and tested before handover.

Whichever level you start at, send a test chat from a new phone and check it reaches every place it should: the right person, the CRM record and the GA4 report.