WhatsApp Business API Integration

The WhatsApp Business API (now WhatsApp Cloud API, hosted by Meta) lets your business send and receive WhatsApp messages programmatically — critical for order updates, OTP, customer support, and marketing campaigns. Unlike WhatsApp Business App (limited to one device), the Cloud API scales to millions of messages per day.

I've built WhatsApp integrations for e-commerce order notifications (PDF receipts via WhatsApp), appointment reminders for clinics, OTP delivery, chatbot-driven customer support, and bulk marketing campaigns with opt-out handling.

In 2026, WhatsApp is often the highest-ROI channel for Indian businesses — open rates exceed 95% (vs ~20% for email, ~8% for SMS), and response rates for customer service average 3–5× higher than phone or email.

WhatsApp Business API integration process

1. Meta Business account setup — verify business, phone number, display name approval (2–5 days on Meta's side)
2. Template submission & approval — pre-register every automated message template (order confirmation, OTP, shipping update, etc.). Meta approves each template within hours.
3. Server-side integration — Laravel/PHP service to send template messages, handle media, manage conversations
4. Webhook handler — receive incoming messages, delivery receipts, read receipts, status updates
5. Session management — 24-hour customer service window logic (free-form vs template messages)
6. Chatbot / auto-reply (optional) — decision trees, LLM-powered replies, fallback to human agent
7. Opt-in management — consent capture, opt-out ("STOP") handling, compliance with WhatsApp commerce policy
8. Analytics dashboard — delivery rates, read rates, conversation metrics

Common WhatsApp Business API use cases

• Order confirmations & shipping updates — replace SMS for e-commerce
• OTP delivery — higher delivery rate than SMS in many regions
• Appointment reminders — clinics, salons, service businesses
• Customer support chatbot with human agent handoff
• Bulk marketing (with opt-in) — product launches, offers, newsletters
• Catalogue & commerce — browse and buy inside WhatsApp
• Payment requests — integrated with Razorpay / payment links
• COD order confirmation — reduce RTO (return to origin) rates

WhatsApp API pricing: what messages actually cost

Since mid-2025 Meta bills the Cloud API per delivered template message, not per 24-hour conversation. Every template is assigned one of four categories, and the category decides the rate:

• Marketing — promotions, offers, re-engagement campaigns. The most expensive category.
• Utility — order confirmations, shipping updates, payment reminders. A fraction of the marketing rate, and free when sent inside an open customer-service window.
• Authentication — OTPs and login codes, priced close to utility.
• Service — free-form replies to customers inside the 24-hour window are free.

Two practical consequences shape every build: templates must be written and categorised so transactional messages are not misclassified as marketing, and support flows should keep replies inside the free service window. Both are handled as part of this integration. Country-by-country rates are published on Meta's pricing page.

Cloud API direct vs BSP platforms (WATI, Interakt, Gupshup, AiSensy)

Most "WhatsApp marketing tools" are Business Solution Providers reselling the same Meta API behind a monthly subscription, per-seat fees, and a markup on every message. Integrating the Cloud API directly means you pay Meta's rates only — no subscription, no markup — and messages flow through your own server and database instead of a third-party dashboard. The trade-off is that direct integration needs engineering, which is exactly what this service delivers. For a business sending a few thousand messages a month, going direct typically pays for itself within the first year — and you own the code and the data.

Engineered for scale and deliverability

A production WhatsApp integration is more than an HTTP call to the Graph API. Every build ships with:

• Queued sending with retries — Laravel queue workers batch bulk sends, respect Meta's rate limits, and survive transient API failures without dropping messages
• Webhook signature verification — incoming payloads are validated against Meta's app secret, so delivery statuses and inbound messages cannot be spoofed
• Messaging-limit awareness — new numbers start at 250 business-initiated conversations per day and scale in tiers (1K → 10K → 100K → unlimited) as volume and quality grow; the sender throttles itself to the current tier instead of erroring
• Quality-rating protection — opt-out handling, frequency caps and template hygiene that keep the number's quality rating healthy, because a flagged number loses its messaging tier overnight

Works with the stack you already run

The integration layer is framework-native, not a bolted-on widget. For Laravel it arrives as a service class plus notification channel, so ->notify() can reach WhatsApp the same way it reaches mail. For WooCommerce / WordPress it hooks order-status transitions to send confirmations and shipping updates automatically. For CodeIgniter and plain-PHP applications it is a drop-in library with the same queue-backed reliability. It also pairs naturally with Razorpay payment links for collect-via-WhatsApp flows, and can be extended into a full WhatsApp chatbot with human-agent handoff.

Official Business Account — the green tick

The verified badge next to a business name is granted by Meta, not purchased outright: it requires completed Meta Business verification, an active API number with clean quality history, and either notability review or a Meta Verified subscription depending on the market. The integration includes preparing the business profile, display-name approval, and submitting the verification request with the documentation Meta expects — which materially improves approval odds, though final say is always Meta's.