Stop Losing Leads: How to Send WhatsApp Notifications from Contact Form 7
A customer in Faisalabad visits your WordPress site at 11:30 PM looking for a generator rental quote. They fill out your Contact Form 7 form. The default configuration of WordPress sends an email to your Gmail account. Because of SMTP delays or spam filters, that email lands in your promotions tab, or you simply do not check your inbox until 9:00 AM the next morning.
By the time you open your email, that lead is dead. They already messaged a competitor on WhatsApp, got an instant reply, and paid a deposit. In Pakistan and India, email is where business conversations go to crawl; WhatsApp is where they happen instantly.
Connecting Contact Form 7 to WhatsApp is the most effective way to stop losing these leads. This guide shows you how to set up this connection reliably, without relying on fragile workarounds that will get your phone number banned.
The Two Paths: Official API vs. Grey-Market Shortcuts
Before writing code or installing plugins, you must choose how your messages will travel. There are two ways to do this, and one of them is a trap.
The Grey-Market Way (Avoid This)
You will find cheap services or scripts online that ask you to scan a QR code with your personal WhatsApp app. They use headless web browsers (like Puppeteer or Selenium) to mimic a human typing on WhatsApp Web.
Do not use these. Meta actively scans for automated behavior on personal accounts. Your number will get banned within days, often hours. Once Meta flags your physical device's MAC address and SIM card, getting that number back is nearly impossible.
The Official Meta Cloud API Way
This is the official, stable method. You connect your WordPress site directly to Meta's servers. Your messages will always deliver, your number will not get banned, and you can send notifications 24/7 even if your phone is switched off.
The Real Cost of Sending WhatsApp Notifications
Meta does not charge you to use the Cloud API platform itself, but they do charge per conversation. A conversation is a 24-hour window that starts the moment your message delivers.
Because these notifications are business-initiated, they fall under Meta's "Utility" category. You must pay for these. In India, a utility conversation costs about 0.12 INR. In Pakistan, it is about 1.50 PKR. These rates fluctuate based on exchange rates and Meta's policy updates. You can check the current rates directly on the Meta Developer Pricing Directory.
If you send 500 lead notifications a month in India, your bill will be around 60 INR. That is a negligible cost compared to the value of a single converted customer.
Step 1: Set Up Your Meta Developer Account
To start, you need a Meta Developer account and a verified Meta Business Manager. If you are in India or Pakistan, make sure you have a business registration document (like an NTN in Pakistan or a GST registration in India) to verify your business manager account. Without this, Meta will limit your sending capability.
- Go to developers.facebook.com and log in with your Facebook account.
- Create a new App, select "Other", and choose "Business" as the app type.
- Scroll down on the app dashboard and click "Set Up" under the WhatsApp icon.
- Meta will assign you a temporary test phone number and a temporary Access Token.
Do not use the temporary token for your live website. It expires after 24 hours. You must go to your Business Settings, create a "System User", generate a permanent access token, and assign it to your WhatsApp app.
Step 2: Create a Message Template
Meta does not allow businesses to send custom, free-form text messages to start a conversation. You must use a pre-approved template. If your template contains spammy language, Meta's automated system will reject it within minutes.
Go to your WhatsApp Manager, find the "Message Templates" section, and create a new Utility template. Use a structure like this:
Template Name:new_website_lead
Template Body:
"Hello Admin, you have received a new inquiry from {{1}}. Phone number: {{2}}. Message: {{3}}"
The curly brackets containing numbers are variables. Your WordPress site will replace these variables with the actual data the user typed into Contact Form 7.
Step 3: Connect Contact Form 7 Using Custom PHP
Many third-party plugins charge high annual fees just to send this data. You do not need them. You can write a simple PHP function in your theme's functions.php file or use a code snippets plugin to handle the API call.
This code hooks into Contact Form 7's wpcf7_mail_sent action. When a user submits the form successfully, WordPress intercepts the data and sends it to Meta's API.
add_action('wpcf7_mail_sent', 'send_whatsapp_on_cf7_submission');
function send_whatsapp_on_cf7_submission($contact_form) {
$submission = WPCF7_Submission::get_instance();
if (!$submission) {
return;
}
$posted_data = $submission->get_posted_data();
// Extract your form fields (change these to match your CF7 tags)
$name = isset($posted_data['your-name']) ? sanitize_text_field($posted_data['your-name']) : 'Unknown';
$phone = isset($posted_data['your-phone']) ? sanitize_text_field($posted_data['your-phone']) : 'No Phone';
$message = isset($posted_data['your-message']) ? sanitize_text_field($posted_data['your-message']) : 'No Message';
// Meta API Details
$token = 'YOUR_PERMANENT_ACCESS_TOKEN';
$phone_number_id = 'YOUR_PHONE_NUMBER_ID';
$recipient_phone = '923001234567'; // Your admin phone number with country code, no plus sign
$url = 'https://graph.facebook.com/v17.0/' . $phone_number_id . '/messages';
$body = array(
'messaging_product' => 'whatsapp',
'to' => $recipient_phone,
'type' => 'template',
'template' => array(
'name' => 'new_website_lead',
'language' => array(
'code' => 'en_US'
),
'components' => array(
array(
'type' => 'body',
'parameters' => array(
array('type' => 'text', 'text' => $name),
array('type' => 'text', 'text' => $phone),
array('type' => 'text', 'text' => $message)
)
)
)
)
);
$args = array(
'body' => json_encode($body),
'headers' => array(
'Authorization' => 'Bearer ' . $token,
'Content-Type' => 'application/json',
),
'timeout' => 15,
'blocking' => true,
);
$response = wp_remote_post($url, $args);
// Optional: Log errors for debugging
if (is_wp_error($response)) {
error_log('WhatsApp API Error: ' . $response->get_error_message());
}
}
Replace YOUR_PERMANENT_ACCESS_TOKEN, YOUR_PHONE_NUMBER_ID, and the recipient_phone with your actual details. The recipient phone must include the country code without any plus signs or zeros at the beginning (for example, 92 for Pakistan or 91 for India).
The Alternative: Simplifying with WA Link
If configuring the Meta Developer Console, setting up system users, and writing PHP code feels too complex, you can use WA Link to simplify the process. WA Link provides a streamlined API wrapper that sits between WordPress and Meta. It handles the message delivery and connection stability without requiring you to write custom curl requests in PHP.
However, keep in mind that WA Link cannot bypass Meta's fundamental rules. You still need an official WhatsApp Business phone number, and you must still use pre-approved templates for any messages you send to customers outside the 24-hour window.
Three Critical Mistakes to Avoid
If your integration stops working, it is almost always due to one of these three issues:
1. Failing to Clean Up Phone Numbers
Users type phone numbers in every format imaginable. A user in Delhi might type 09876543210, +91 98765-43210, or 9876543210. Meta's API is strict; it expects a clean string of numbers starting with the country code. If you send a phone number with spaces, hyphens, or a leading zero to Meta's API, the API will return a 400 Bad Request error. Use PHP's preg_replace('/[^0-9]/', '', $phone) to strip out non-numeric characters before sending the API request.
2. Blocking the Admin's Phone Number
If you set up the system to send a notification to your own phone number every time a form is submitted, your number is receiving messages from your own API. Make sure your business phone has opted in to receive these messages. If you report your own API number as spam by accident, Meta will suspend your developer account instantly.
3. Ignoring the API Timeout
When a user clicks "Submit" on Contact Form 7, the browser waits for the server to process the form, send the email, and call the WhatsApp API. If the WhatsApp API takes 10 seconds to respond, the user will see a spinning loading icon on the form for 10 seconds. They might click it multiple times or close the page. Always set a reasonable timeout (such as 5 or 10 seconds) in your wp_remote_post arguments to prevent your website from hanging.
Frequently Asked Questions
Can I use my personal WhatsApp number to send these notifications?
No. You can send the notifications *to* your personal number, but the sending number must be registered on the Meta Cloud API platform. Once a number is registered on the Cloud API, you cannot use it on the standard mobile WhatsApp app anymore. You must manage your chats using the Meta Business Suite or a third-party inbox tool.
What happens if the WhatsApp API goes down?
Because this code runs alongside Contact Form 7's native functions, the email notification serves as your backup. If the WhatsApp API fails, the email will still be sent as usual. Your website visitor will still see a green success message on the screen.
Can I send a notification to the customer instead of myself?
Yes. You can change the $recipient_phone variable in the PHP code to pull the phone number submitted by the user in the form. Remember, you must have their explicit consent to message them on WhatsApp, and you must use an approved template that welcomes them or confirms their submission.
Is there a limit to how many notifications I can send daily?
New Meta Developer accounts start at Tier 1, which limits you to sending business-initiated messages to 1,000 unique recipients per 24-hour period. This limit automatically increases to 10,000 and then 100,000 as you maintain a good quality rating and send more messages.