To integrate WhatsApp contact into a website, add a link using https://wa.me/ followed by the business number in international digits. You can optionally prefill a message. Clicking opens the conversation; it does not send the message or prove an enquiry was received. Test the destination and measure the website click separately from the eventual incoming message.
This approach is suitable when the immediate requirement is a customer contact route. It does not, by itself, create an inbox, automated assistant, order connector or campaign permission. Bird’s official platform explanation documents the link format and these message boundaries. Bird click-to-chat guide.
How do you build the website link?
First confirm the number that the business actually controls and monitors. Convert it into its full international form, including the country code, before removing formatting. Bird’s guide specifies digits without the plus sign, brackets or dashes after https://wa.me/. A valid-looking URL pointing to the wrong number still opens the wrong conversation.
Add that URL to a normal website link or button. Use a clear label such as “Ask about this service on WhatsApp”, so the visitor understands where it leads. Place it beside the relevant offer or contact information rather than making it the only way to understand the page.
The following is a structural example, not a working contact link. Replace the uppercase placeholder with the owner-confirmed international digits before using it:
<a href="https://wa.me/BUSINESS_NUMBER_IN_INTERNATIONAL_DIGITS">
Ask about this service on WhatsApp
</a>
Do not publish the placeholder or substitute a guessed telephone number. Retain the confirmed destination in the site’s authorised configuration so a future change can be made consistently. If several pages have separate contact buttons, include all of them in the destination check.
Can you prefill the customer’s first message?
Yes. Append ?text= followed by URL-encoded text to the numbered link. For example, the text value I%20have%20a%20question%20about%20this%20service represents an ordinary enquiry sentence with encoded spaces. The customer can edit the suggested message before sending it. The link does not authorise the website to send on their behalf.
Keep the suggestion short, relevant and free of personal information. A service name or broad request can help the recipient understand the context without putting a customer’s address, account information or order problem into a public URL. Do not insert data collected from a form merely because the parameter accepts text.
Use the numbered form when the business must be the destination. Bird distinguishes https://wa.me/?text=..., without a number, as a sharing form. It is not an equivalent substitute for a link intended to open your business conversation. Numbered and sharing link formats.
Should you use a direct link or a managed short link?
A direct numbered link exposes its destination in the URL and can carry the optional encoded text. Bird also describes the managed https://wa.me/message/ short-link form, which stores the suggested text separately and uses a code. That can be useful when the suggested message needs changing after a link is printed or distributed.
The management requirements differ. The guide identifies Business Manager and the WhatsApp Business Management API as routes for managing QR codes and their short links. Do not interpret that as proof that your current account has every relevant control enabled. Confirm the actual account and destination before choosing the management route.
| Requirement | Direct numbered link | Managed short link |
|---|---|---|
| Identify the business destination | Number is part of the URL | Code represents the managed destination |
| Suggest first-message text | Encoded text in the URL | Text stored separately by the service |
| Change published suggestion | Update links carrying the old text | Manage the stored text where supported |
| Retire the route | Replace each published destination | Check distributed uses before deleting the code |
Neither option proves that somebody sent a message. A shortened URL is not an enquiry record, and a QR scan is not permission for later marketing.
How should website clicks be measured?
Google Analytics enhanced measurement describes an outbound click event when a user follows a link away from the current domain to another website. Its documented parameters include link URL, link domain and link ID. It also states that links to domains configured for cross-domain measurement do not trigger these outbound events. GA4 enhanced measurement.
If you use this measurement, inspect the actual event after clicking the actual button. Check that the destination corresponds to the intended WhatsApp route. Do not assume that every theme button, consent configuration or custom interaction produces the expected event merely because enhanced measurement exists.
Name the result honestly in reporting: “WhatsApp contact link click” describes a website action. “Enquiry received” requires an incoming message record. “Qualified enquiry” requires a further business assessment. Treating all three as the same conversion hides where visitors leave the journey and makes the report less useful.
An original click-to-enquiry acceptance card
Use this card for each important placement. It separates a proposed check from the actual observed result.
Placement: Page, visible label and intended customer question.
Destination: Confirmed business number or managed code; person responsible for changes.
Opening result: Device and browser used, conversation destination shown, and any installation or access obstacle observed.
Suggested text: Exact message presented, encoding result and whether it remains editable.
Website event: Event name, link identifier and destination recorded, or a clear note that no event appeared.
Incoming message: Whether the customer actually sent, where the message arrived and its conversation reference.
Business response: Who noticed it, what further action was needed and what remains unresolved.
Do not fill the final fields from the website event alone. Bird explicitly says opening the link sends nothing. Run the checks in a controlled conversation with an authorised participant, and avoid copying private message content into a public handover.
Test mobile and desktop journeys separately. Record what happens rather than promising a universal application-opening experience. Also test the link from the placements customers actually use; a correct contact page does not establish that an older floating button points to the same destination.
What did the public WhatsApp endpoint actually show?
On 24 October 2026, an unauthenticated public GET used the number already linked from Spout’s homepage and the fictional text “Fictional website link check – no message sent.” The encoded wa.me request redirected to WhatsApp’s api.whatsapp.com send landing page. Its actual readable body displayed the same destination number and the same prefilled words, alongside an “Open app” option. Observed official WhatsApp landing page.
This is a bounded endpoint observation, not a completed conversation test. No login, browser interaction, app opening or message send took place. It establishes that this example reached a landing page with the intended destination and text; it does not establish universal device behaviour, recipient availability or message delivery. The separate incoming-message check in the acceptance card remains necessary before recording an enquiry as received.
What must be ready after the visitor sends?
Agree who monitors the destination and how an unanswered question becomes visible. If the business later adds an API connector, assess its incoming-message handling separately. A click-to-chat button has not demonstrated that connector or created a response-time commitment.
Keep marketing permission separate from the enquiry. A person requesting help through the link has not thereby agreed to unrelated promotions. Preserve another clearly labelled contact route where appropriate, so a visitor can still understand how to contact the business if the WhatsApp journey cannot be completed.
For a broader implementation brief, see Spout’s WhatsApp Business service and web development service. Get started with the current page, intended destination and observed gap, keeping customer messages and credentials out of the initial enquiry.
By Spout Team. Prepared with AI-assisted drafting using the linked primary sources.