WhatsApp Business API setup.
Done in 4–6 weeks. By us.

WhatsApp Business API (also called WhatsApp Business Platform or WABA) is Meta's programmatic interface for businesses to send and receive WhatsApp messages at scale. Unlike the free WhatsApp Business App — which is single-device and built for sole traders — the API supports multi-agent, multi-device usage, automation, AI chatbots, and integrations with CRM, helpdesk and payment systems. Access is gated by Meta and requires Business Verification.

There are four steps. (1) Verify your business with Meta Business Manager — supply company registration, proof of address, domain ownership. (2) Choose a Business Solution Provider (BSP) such as Meta Cloud API direct, 360dialog, Twilio or Vonage — they sit between you and Meta. (3) Submit your business phone number for migration onto WABA — typically 5–14 days. (4) Connect your messaging stack — chatbot, CRM, helpdesk — via the BSP's API. FrictionZero handles all four steps as a setup-as-a-service.

Realistic timelines: Business Verification 3–10 days; BSP onboarding 1–3 days; phone number migration 5–14 days; full chatbot + CRM integration 2–4 additional weeks. End to end: 4–6 weeks for a production deployment. Self-serve attempts commonly stall on Business Verification — South African WABA downloads grew +1,500% YoY in 2025 but completion rates lag, which is the gap we close.

Yes — but with conditions. The number must be removed from the WhatsApp Business App before migration. You lose conversation history on the old app. The number must not be a WhatsApp Business Account that has been used in the last 30 days on another integration. For most businesses we recommend migrating an existing number rather than starting fresh — customers already recognise it.

Meta charges per conversation in three categories: marketing, utility, authentication. Pricing varies by country — UK and South Africa fall into different tiers. Marketing conversations are the most expensive, utility (transactional) the cheapest. Free entry-point conversations apply when the customer messages you first. On top of Meta's fees, BSPs charge a small per-conversation markup or flat monthly fee. The FrictionZero Friction Audit gives you a precise TCO figure for your projected volumes.

Meta Cloud API is the cheapest path but requires the most engineering. 360dialog is European, GDPR-native, lowest BSP markup. Twilio adds robust telephony integration if you also need voice. Vonage suits enterprises with existing Vonage Communications relationships. We typically default to 360dialog for UK/EU deployments and Twilio for SA + voice-combined deployments. The decision lives inside the Friction Audit.

WhatsApp itself is end-to-end encrypted in transit. GDPR and POPIA compliance depends on how you configure the deployment: explicit opt-in capture at first contact, configurable retention, suppression on request, data-processing agreements with Meta and your BSP, secure handling of message content in your CRM. We include all of this in the setup-as-a-service.

Three blockers: (1) Meta Business Verification is more demanding than expected — domain ownership, registered business details and proof-of-address documents all have to match, (2) the WhatsApp Display Name has to comply with Meta's policy (which rejects many trading names), (3) the phone-number migration step has subtle requirements that fail silently. The +1,500% YoY surge in South African WABA downloads contrasts with completion rates a fraction of that — this is the wall FrictionZero unblocks.