First decide which of the three you mean
| You want | The route | What it takes |
|---|---|---|
| Visitors start a WhatsApp chat with you | A wa.me click-to-chat link or button | One link; nothing to host or pay |
| The form's text arrives in that chat | wa.me with ?text= built from the fields | A few lines of JavaScript |
| A WhatsApp message to you on every submission | Business Platform via a provider, bridged from a webhook | WhatsApp Business Account, Meta Business Manager, a template, a provider |
The third row surprises people: WhatsApp has no personal-number API, so “just message me on submit” is the one that needs business infrastructure. If the point is an instant ping on your phone, the last section shows the shortcut most sites take.
Route 1: the wa.me link, straight from WhatsApp's docs
WhatsApp's click-to-chat page gives the exact format: https://wa.me/<number>, where the number is “a full phone number in international format”, and the page is explicit about the formatting: “Omit any zeroes, brackets, or dashes”. Add a pre-filled message with ?text= and URL-encoded text. Their own example: https://wa.me/1XXXXXXXXXX?text=I'm%20interested%20in%20your%20car%20for%20sale.
A plain “Chat on WhatsApp” button is this link in an anchor tag; WhatsApp publishes official button images and asks that they be used unmodified. It works on phones and WhatsApp Web, and it costs nothing. The limits are structural: the conversation happens in WhatsApp, so nothing lands in an inbox you can search or export, and a visitor without WhatsApp hits a wall, which is why this button belongs next to a form, not instead of one.
Route 2: pre-fill the chat from your form's fields
A small script can build the wa.me link from what the visitor typed, so the chat opens with the enquiry already written. Intercept the button click, assemble the text, URL-encode it with encodeURIComponent, and open the link:
const form = document.querySelector("#contact");
document.querySelector("#whatsapp-btn").addEventListener("click", () => {
const data = new FormData(form);
const text = `Hi, I'm ${data.get("name")}. ${data.get("message")}`;
window.open("https://wa.me/15551234567?text=" + encodeURIComponent(text));
});Route 3: a real WhatsApp message on every submission
To have WhatsApp itself deliver a message when the form is submitted, you are in Business Platform territory, and the requirements are Meta's, not ours. Meta's overview lists what an account needs: a display name, a phone number for the business, a WhatsApp Business Account, and a Meta Business Manager. On top of that, provider documentation (360dialog's, in our sources) states the template rule: a business cannot open a conversation with a freely composed message, so a business-initiated notification goes out as an approved template.
In practice almost nobody wires this by hand for a contact form. The working pattern is a bridge: the form backend fires a webhook per submission, an automation platform (Make, Zapier, n8n) catches it, and a WhatsApp provider step (Twilio and 360dialog are the common ones) sends the template message to your number. Formgong's signed webhooks are on every plan, so the bridge costs nothing on our side; the provider's requirements still apply on theirs.
The shortcut: the same ping without the Business Account
Step back to the actual wish, a message on your phone the second a form is submitted, and the Business Platform is the long way around. Telegram does exactly this natively: Formgong sends each submission to a Telegram chat on every plan, Free included, with Reply and Mark handled buttons, no template approval and no Business Manager. The setup is in website form to Telegram, and it coexists with a wa.me button for visitors who prefer WhatsApp: they write to you on WhatsApp, the form pings you on Telegram, and nothing is lost in either place because every submission also sits in the dashboard inbox and your email.
If your team genuinely lives in WhatsApp, route 3 is the honest answer and the bridge works; we simply will not pretend it is four clicks.
Which route did you ship?
Did the wa.me button cover it, did you build the provider bridge, or did Telegram win? Write to support@formgong.com and tell us what you built. The setups readers send are how these guides get better.
Frequently asked questions
Can a website form send submissions straight to my WhatsApp?
Not to a personal number: WhatsApp has no personal-number API. A real per-submission WhatsApp message needs the Business Platform — WhatsApp Business Account, Meta Business Manager, an approved template, usually a provider — typically bridged from a form webhook via Make or Zapier. The lightweight alternatives are a wa.me click-to-chat button, or Telegram delivery, which form backends offer natively.
What is the wa.me link format?
https://wa.me/<number> with the number in international format — WhatsApp's docs say to omit any zeroes, brackets, or dashes — plus an optional ?text= parameter with a URL-encoded pre-filled message. Their example: https://wa.me/1XXXXXXXXXX?text=I'm%20interested%20in%20your%20car%20for%20sale.
Why does my WhatsApp notification need a template?
Provider documentation for the Business Platform states that a business cannot start a conversation with a freely composed message; business-initiated messages use approved templates. Your form notification is business-initiated, so the template rule applies to it.
What is the cheapest way to get form submissions on my phone?
Telegram: form backends deliver there natively — Formgong on every plan, including Free — with no business account or template approval. Keep a wa.me button for visitors who want to chat on WhatsApp; the two solve different halves of the problem.
Sources and documentation
Official references for this guide: WhatsApp: how to use click to chat, Meta: WhatsApp Business Platform overview, 360dialog: messaging (template rule), Formgong: webhooks. HTML contact form, where data is stored.
Related guides
- Lovable form submissions to email and Telegram
- HTML contact form without a backend: a working example
- How to send website form submissions to Telegram
- Contact form not sending email? Check where it stops
- Managing website leads in Telegram without a CRM
- Form backend for Lovable, Bolt, v0, Cursor
- Telegram bot for a contact form: build or skip?
- GDPR form backend: 7 checks before you choose
- Lovable form not sending email? 6 fixes
- Netlify Forms not working? React and Bolt fixes
- Stop contact form spam without a CAPTCHA
- GitHub Pages contact form: a working setup
- Mailto Form in HTML: Why It Fails and What to Use
- HTML form to Google Sheets: 2 free methods
- Webflow form submission limit: what to do at 50
- Turnstile vs reCAPTCHA vs hCaptcha for forms
- Contact Form 7 and Elementor forms to Telegram
- Squarespace contact form not sending email?
- Shopify contact form: where do messages go?
- Google Form to Telegram: free Apps Script way
- Wix contact form not sending email? Fixes
- EU / GDPR Formspree alternatives compared
- HTML form action attribute explained
- How do HTML forms work? The HTTP request
- Types of Injection Attacks on Web Forms (2026)
- Indirect Prompt Injection in MCP
- MCP Rug Pull Attack: Detect Tool Changes
- Form without a backend: 7 ways that work
- Thank-you page after form submission (HTML)
- Indirect Prompt Injection Examples (2023–2026)
- Indirect Prompt Injection via Email
- What Is Tool Poisoning in MCP?
- WordPress contact form without a plugin
- Send email from frontend JavaScript
- How to Prevent Indirect Prompt Injection
- Honeypot Form Field: How to Add One That Works
- Contact Form with File Upload (HTML, No PHP)
- Angular contact form without a backend
- Send form submissions to Slack or Discord without Zapier
- Verify a form webhook signature (HMAC-SHA256)
- Contact forms that send nothing: 793 AI-built sites tested
- v0 contact form that actually sends: 3 ways
- How we tested AI-built contact forms, and 12 bugs we hit
- Cloudflare vs Netlify free plan: hosting that never pauses
- EmailJS 412 “Gmail_API: Invalid grant”: reconnect Gmail
- Resend “You can only send testing emails”: verify a domain
- Supabase Edge Function blocked by CORS policy: 3 causes
- Formspree “Form not found” and other errors: fixes
- Web3Forms errors: “Invalid access key” and 403 explained
- How to add customer reviews to your website for free
- Getform not working? “This form has been deleted” and more
- Next.js contact form not working? 6 errors, reproduced
- Webflow form not sending email? What to check, tested
- FormSubmit not working? “This form needs Activation” fix
- Contact form “TypeError: Failed to fetch”: causes and fixes
- WooCommerce product enquiry form
- Contact Form 7 vs WPForms
- Gravity Forms alternative free
- WordPress contact form block
- 535-5.7.8 Username and Password not accepted (Gmail)
- 535 5.7.3 Authentication unsuccessful: Office 365 SMTP
- Nodemailer “Missing credentials for "PLAIN"”: the fix
- Nodemailer “Greeting never received”: port 465 fix
- Nodemailer SSL “wrong version number”: the port fix
- Nodemailer “self-signed certificate in certificate chain”
- Nodemailer ECONNREFUSED 127.0.0.1:587: missing SMTP host
- SendGrid “authorization grant is invalid”: 401 fix
- Mailgun 401 Forbidden: why the API rejects your key
- “Edge Function returned a non-2xx status code”: the fix
- Next.js “Body exceeded 1 MB limit”: Server Action fix
- Unexpected token '<', "<!DOCTYPE "... is not valid JSON
- “TypeError: Body is unusable”: body has already been read
- Turnstile “timeout-or-duplicate” and other siteverify errors
- Turnstile vs hCaptcha vs reCAPTCHA: speed and size tested
- Judge.me reviews not showing on Shopify: how to fix it
- Judge.me review carousel not showing: how to fix it
- Yotpo reviews not showing on Shopify? Check the app embed
- Loox reviews not showing on product page: how to fix
- Shopify reviews not showing: what to check first
- How to show reviews on Shopify
- GDPR for website forms: what each type of form needs
- WooCommerce reviews not showing: how to fix it
- Stamped.io reviews not showing on Shopify: how to fix it
- Etsy reviews not showing: why and what to do
- Trustpilot widget not loading: how to fix TrustBox
- Yotpo problems in 2026: what merchants report
- Contact Form 7 “error trying to send your message” fix
- Elementor form “Your submission failed because of an error”
- Framer form not sending email or not working: what to check
- Carrd contact form not working: plans, spam and errors
- Google review link not working: what customers see and why
- tawk.to widget not showing on your website: causes and fixes
- How to add questions and answers to your product page
- “Failed to send a request to the Edge Function”: fixes
- Next.js “Failed to find Server Action”: what it means
- Brevo “unauthorized: Key not found” 401: the fix
- Amazon SES “Email address is not verified”: the fix
- Shopify contact form not working: how to fix it
- Judge.me alternative for WooCommerce after the 2025 shutdown
- Free WooCommerce review plugins compared on the free version
- WooCommerce review reminder emails without a paid plugin
- Add Voice Recording to a Website Form
- Contact Form 7 spam: how to stop it
- WPForms not sending email: how to fix it
- Contact form emails going to spam: how to fix it
- HTML form not submitting: how to fix it
- Contact form not working: how to find the fault
- Webflow form spam: how to stop it
- Website form to Notion: how to set it up