WhatsApp is where most of MENA actually does business — and the Cloud API has matured to the point where building on it is no longer the rough edge it was two years ago. We’ve shipped platforms that handle thousands of customer conversations a day, with auto-reply trees, agent inboxes, transactional pipelines feeding from POS / CRM / e-commerce, and broadcast tooling that respects opt-in compliance. We built BigLinker on WhatsApp-class messaging at scale; the same operational chops apply here. The dashboard is yours, the data is yours, and the conversations stay where your customers expect them.

Stack & defaults

Platform
Meta WhatsApp Cloud API
Backend
Laravel / Node webhooks
Dashboard
Vue 3 + Inertia
Queues
Redis + Horizon
Approvals
Template manager
Failover
Twilio / SMS fallback
Notifications
OTP + transactional
Integration
CRM / POS bridges

What you receive

Multi-agent chat dashboard
Team inbox with conversation routing, agent presence, internal notes, canned replies, search. Built for a real support floor, not a demo.
Automated reply trees + intent routing
Decision trees for common flows, NLP intent for the messy ones, escalation to human agents on triggers you control.
OTP, order confirmations, status updates
Transactional pipeline with retries, idempotency, template versioning, and delivery receipts wired into your product.
Marketing broadcast tooling
Segment-based campaign sender with throttling, opt-in / opt-out compliance, link tracking, conversion attribution.
Template approval workflow
Submission, revision, and tracking against Meta's review process — without leaving the dashboard.
Integration into your stack
Webhooks into your CRM, POS, e-commerce, or ticketing system. Two-way sync, conflict resolution, audit trail.

Timeline

Wk 1
Setup
Meta Business verification, phone-number provisioning, Cloud API onboarding, webhook scaffolding.
Wk 2–4
Build
Dashboard, reply automation, template manager, transactional pipeline.
Wk 5
Hardening
Rate limits, abuse protection, Meta-policy compliance pass, load test.
Wk 6
Launch
Cutover, agent training, on-call handoff.

FAQ

Do you handle Meta business verification?
Yes — including the Facebook Business Manager setup, document submission, display name approval, and the back-and-forth when Meta flags something. It's part of the engagement.
What's the message-cost model?
Meta charges per conversation in tiers (utility, marketing, authentication, service). We architect to keep most volume in the utility / service tiers and surface real-time spend on the dashboard. The platform we build is yours; the conversation cost is between you and Meta.
Can it wire into our existing CRM or POS?
Yes. We've integrated WhatsApp into Laravel CRMs, Salesforce, HubSpot, Magento, Shopify, and custom ERPs. Two-way sync, message threads tied to customer records, agent assignment based on owner.
How do you handle the 24-hour customer-care window?
Inside the window: free-form messages, full conversation. Outside: pre-approved templates only. The dashboard makes this distinction explicit so agents don't accidentally try to send free-form into a closed window — and templates pre-fill from the conversation context.