WhatsApp Business API
In much of the world, WhatsApp is the inbox. The Business API turns it from a side channel into infrastructure — with template rules, conversation windows and consent mechanics that punish improvisation.
WhatsApp went from "the app customers prefer" to infrastructure when Meta opened the Business API: template messages, conversation windows, click-to-chat entry points, and (in some regions) in-chat payments. Businesses run real support and order flows on it. The API also has rules — pre-approved templates, 24-hour reply windows, quality ratings that throttle accounts that spam — and the gap between a WhatsApp button and a WhatsApp operation is exactly those rules.
The build shape depends on the brief: click-to-chat entry points wired from the site (this practice runs one — the floating button here opens a real chat), notification templates for orders/bookings/statuses through a BSP or the API directly, and routing that lands chats with a human inbox rather than a void. If automation belongs in the loop, it connects to the workflow automation side — auto-replies for hours/location, human handoff for everything that needs judgment.
Honest boundary: template approvals and account quality are Meta's process — the integration is built to pass them cleanly (useful templates, honest opt-in), not to spin up accounts that dodge them. Scope follows the brief; fixed quote.
What the engagement covers
- Click-to-chat entry points across the site — prefilled, contextual, per-surface
- Notification templates (orders, bookings, status) drafted for approval and wired to events
- Business API or BSP plumbing: tokens, webhooks, delivery statuses handled
- Routing to a real human inbox — chats land with a person, with context attached
- Optional automation layer: FAQ auto-replies with clean human handoff
- Consent and opt-out mechanics done properly — quality rating is an asset, protected as one
Honest limits
What this is deliberately not.
Not this: Cold outreach or scraped-number campaigns — template rejections and account bans follow; declined up front
Not this: A bot pretending to be a person — auto-replies are labeled as such; pretending violates both Meta rules and this practice's honesty rules
Not this: Guarantees on Meta approval timelines — their review, their queue
Not this: Regional availability assumptions — WhatsApp Business calling/payments vary by country; the consult checks yours
Questions · WhatsApp Business
Asked before building.
The free app honestly suffices for one person answering chats manually. The API earns its complexity when messages must be triggered by systems (order shipped, appointment tomorrow), when multiple staff share the load, or when entry points need routing. If none of those apply, the app is the right answer and this page is not.
Business-initiated messages must use pre-approved templates — Meta reviews them for usefulness and tone. The practical consequence: notification content gets drafted carefully before wiring, because rejections burn weeks. The build includes template drafting that passes review — written for customers, not for marketing calendars.
Yes — webhooks carry every event to wherever it should land: a shared inbox, a CRM record, a Sheet. The routing target is a scoping question (the CRM automation page covers the deeper version), and the answer is chosen for your team's actual habits, not the shiniest option.
Because the audience answers WhatsApp — this practice's own funnel runs on it, from the floating button to prefilled per-page messages. That first-hand operation is why the integration advice here includes the operational details (response times, template tone, handoff discipline) that docs skip.
Related: all integrations · the integrations stack page · the requirements template.
Also in this section
Stripe Integration · PayPal Integration · Razorpay & India Rails · POS & Inventory Syncs · Twilio: SMS & Voice · Email Stack & Deliverability · all →
Scoping something in this space?
Written scope within two business days — deliverables, milestones, timeline, terms, price at the bottom. Compare it against anyone.