If your buyers already message you on WhatsApp, the question is no longer whether to be there. It is whether one phone, one login and one tired person can keep up. A site visit enquiry that waits four hours for a reply is a site visit that went to the next builder.
This guide is for businesses where WhatsApp is how the sale happens: real estate developers, clinics and IVF centres, coaching institutes, D2C brands, salons. It follows the working path: what Meta requires, direct or through a provider, how a lead gets from an ad into a conversation and a CRM record, and the rules that decide whether you get blocked. It carries no prices, because Meta changes them by the quarter. WhatsApp marketing is the service we run on top of this.
WhatsApp Business app vs the Business API
The WhatsApp Business app is built for one phone and a few people. The WhatsApp Business Platform, which Meta describes as enabling businesses to communicate with customers at scale, connects your number to software. That lets many agents reply, messages be automated and leads flow into your CRM. You need it when one phone is the bottleneck.
The platform is built on Meta's Graph API over HTTP and includes the Cloud API plus webhooks that tell your software when a message arrives. "WhatsApp Business API" is the name most people still search for; Meta's current name for the whole product is the WhatsApp Business Platform.
Stay on the app if one person answers, you get a handful of chats a day and you do not need records. Move when you see these signs:
- Leads arrive while the phone owner is in surgery, on a site visit or asleep, and nobody else can answer.
- Three staff share one login, so nobody knows who said what.
- You cannot say how many chats started from Meta ads last month, or how many became bookings.
What you need before you start
You need a Meta business portfolio, a phone number that is not already registered on a WhatsApp account, a display name that matches your business, and a way to receive a verification code by SMS or voice call. Decide before anything else who owns the account: it should be you.
Meta's get-started guide has you create a Meta app with the WhatsApp use case, pick an existing business portfolio or create a new one, connect a messaging account and add the phone number you will send from. Practical checklist:
Before you start
The portfolio holds the number, the templates, the quality history and the billing, so it must be yours; give an agency partner access, never ownership.
On the number: use a dedicated one. Meta's registration pages say numbers already in use with WhatsApp cannot be registered unless deleted first, and short codes are not supported. A number behind an IVR that cannot receive the registration call or SMS will not work. Landline numbers can verify by voice call but are not recommended for SMS codes.
Direct Cloud API or through a provider
You can connect directly to Meta's Cloud API with developers, or use a provider that adds an inbox, chatbot builder and CRM links on top. Direct gives control and fewer middlemen; a provider gives speed. Either way the number, the portfolio and the data should stay in your account.
Meta's documentation describes Solution Partners, who have credit lines they can extend to the clients they onboard, and Tech Providers, whose clients must provide their own payment method so Meta bills them for API usage. "BSP" is the common shorthand for both. Meta's own pages point businesses that are building their own app to the Cloud API get-started guide.
| Direct Cloud API | PickThrough a provider | |
|---|---|---|
| Time to first message | Days to weeks, needs a developer | Hours to days |
| Team inbox and chatbot builder | You build or buy one | Usually included |
| Control of data and flows | Full | Limited to what the provider exposes |
| Who needs the technical skill | You or your developer | Mostly the provider |
| Best for | Teams with developers or a CRM already built | Clinics, schools, shops with no tech team |
Ask any provider these before you sign: Is the Meta business portfolio in my name? Can I export every conversation and contact? What happens to my number and templates if I leave? Which CRM do you connect to without custom work? We do not rank providers here, and BridgeE is not a Meta partner; we mention Meta's programmes only to describe how its documentation divides roles.
The rules that decide whether you get blocked
Business-initiated messages outside a 24-hour customer service window must be pre-approved templates, and users must have opted in. Quality falls when people block or report you. So collect opt-in at the form, send only what was asked for and keep volume steady.
The customer service window. Per Meta, when a user messages or calls you, a 24-hour timer starts, and it resets to 24 hours if they message or call again. While it is open you can send free-form service messages: text, images, interactive messages. When it closes, you can only send pre-approved template messages.
Template categories. Meta requires each template to be categorised as authentication, marketing or utility. Template categories also factor into pricing. Templates are reviewed automatically on creation or after editing, and a template whose quality is poor can be paused or disabled, which stops you sending it.
Pricing in one paragraph. Meta says it charges per delivered message, not per conversation, since 1 July 2025, with rates depending on the message category and the recipient's country calling code. Messages inside an open service window are non-template messages; when a person messages you through a Click-to-WhatsApp ad on the app and you reply within the window, a free entry point window of up to seven days opens in which Meta does not charge for marketing, utility, authentication or service messages. From 1 October 2026, Meta also charges for service replies inside the window beyond 1,000 free a month per phone number, and for utility templates sent in an open window. Meta may update pricing on the first day of a quarter, so read its pricing page on the day you budget.
Opt-in. Meta's documentation states: you can only send messages to WhatsApp users who have opted in to receiving messages from you, and opt-in must clearly state that the person is opting in and the business name. A line that works on a lead form, next to an unticked box:
"Send me updates about my enquiry on WhatsApp from [Business name]. I can stop any time by replying STOP."
Quality and limits. Meta rates message quality by how people react to your messages, for example whether they block or report you. You can see the quality rating and messaging limits for each number in WhatsApp Manager. The messaging limit is the number of unique users you can message outside a service window in a moving 24-hour period, and it is set at the business portfolio level. New portfolios start at 250, with tiers of 2,000, 10,000 and 100,000, then unlimited.
Reaching 2,000 needs business verification, a partner verifying for you, or 2,000 delivered messages outside service windows within 30 days using high-quality templates. After that, automatic scaling applies when you send high-quality messages and use at least half your limit in seven days.
Connect it to your ads, forms and CRM
A lead should land in your CRM the moment it arrives, tagged with its source. Use click-to-WhatsApp ads or a WhatsApp button on your page, add UTM parameters, and pass each conversation into a CRM record. Then the first reply can go out in seconds, by a person or an automation.
From ad to CRM record
Pick the entry point
Use a Click-to-WhatsApp ad on Meta when the ad should open a chat directly. On your site, use a WhatsApp button or a lead form with a WhatsApp opt-in. Compare the two routes in Google Ads vs Meta ads.
Tag the source
Add UTM parameters to the page the button sits on, and store the campaign, ad set and ad in the CRM when the chat starts. Without it, every conversation looks like "WhatsApp".
Create the record on first contact
When a message arrives, your software receives a webhook. Create or update the contact in your CRM with the source, the phone number and the first message.
Send the first reply
Inside the 24-hour window you can reply freely. After a form submit with opt-in, with no chat yet, the first message must be an approved template.
Report on stages, not messages
Set conversion events for conversation started, qualified and booked, and send them back to GA4. Conversion tracking in GA4 shows the one-event-from-one-place rule.
Three automations worth building first
Start small: an instant acknowledgement with the next step, a reminder if there is no reply in a day, and a hand-off to a person when the lead asks for price or a visit. Keep a human visible. Bots that trap people lower trust and quality scores.
- Acknowledge. Within a minute: "Thanks, Priya. We have your enquiry about 2 BHK site visits. Would Saturday morning or evening suit you?" For a clinic: "Thanks for booking interest. Which day this week suits you for a check-up?"
- Remind. If there is no reply after about a day, send an approved utility-style template that restates the next step and offers a person. Do it once, not five times.
- Hand off. Route any message with words like price, visit, appointment, call or doctor to a named person, with the conversation history in the CRM record.
What not to automate: complaints, medical advice, negotiation, and anything where the customer asks for a human. Never hide the option to speak to a person. And do not send a marketing template to everyone who ever messaged you; volume that jumps while replies fall is the pattern that hurts a number.
What to measure
Count conversations started, qualified leads and booked visits or sales per source, not messages sent. Check read and reply rates by template and watch the quality rating in WhatsApp Manager. If replies fall while sends rise, you are hurting your number.
Keep the review to 20 minutes a week:
- Conversations started by source (Click-to-WhatsApp ad, site button, form, Google Business Profile).
- Share that reached "qualified", using your lead scoring rules.
- Booked visits, consultations or orders per source, from the CRM, not from WhatsApp.
- Reply rate and time to first reply, split by template.
- Quality rating and messaging limit for each number.
The number that matters is booked visits per source, and WhatsApp is the channel that carries them, which is the point of lead generation.
Questions people ask
The Business app is a phone app for one business with a few linked devices. The WhatsApp Business Platform, which includes the Cloud API, connects your number to software through code or a provider. That is what gives you a shared team inbox, automation, template messages at scale and CRM records for every conversation.
No. Meta's Cloud API can be used directly if you have a developer. Meta's documentation describes Solution Partners and Tech Providers as companies that offer WhatsApp Business Platform services to other businesses, such as messaging, billing and integration support. Choose one for speed, not because the API requires it.
Meta's phone number documentation says numbers already in use with WhatsApp cannot be registered unless they are deleted first. In practice, most businesses get a fresh dedicated number for the API, or plan the migration, because deleting the account removes its chat history from that number.
Yes. Meta's documentation says you can only send messages to WhatsApp users who have opted in to receiving messages from you, and the opt-in must clearly state your business name and that the person is agreeing to hear from you. Collect it on the lead form, with its own unticked box or a clear line next to the button.
Meta's rules are the same worldwide: opt-in, approved templates, and no messages people did not ask for. Lead follow-up is fine when the lead asked to be contacted on WhatsApp. Check local telecom and data-protection rules for your market with your own adviser; this article is not legal advice.
Sources and further reading
- 1About the WhatsApp Business PlatformMeta for Developers ·
- 2WhatsApp Cloud API: get startedMeta for Developers ·
- 3Pricing on the WhatsApp Business PlatformMeta for Developers ·
- 4Register a business phone numberMeta for Developers ·
- 5Service messages (customer service window)Meta for Developers ·
- 6Messaging limitsMeta for Developers ·
- 7Business phone numbersMeta for Developers ·
- 8Template overviewMeta for Developers ·
- 9Getting opt-inMeta for Developers ·
- 10Solution Partners and Tech Providers overviewMeta for Developers ·
How we wrote this. We read Meta's WhatsApp Business Platform documentation on 1 November 2026 and wrote only the rules those pages state. Meta changes these pages often, and does not publish prices here: always confirm on the linked pages before you commit.
