ServiceWhatsApp Business API

WhatsApp Business API — official integration without the BSP markup

Direct Meta WhatsApp Business Cloud API integration — templated messages, two-way conversations, and Stripe-grade reliability.

Most companies access WhatsApp's API through a Business Solution Provider (BSP) like Twilio, MessageBird, or 360dialog. The trade-off is convenience for per-message margin — and at scale, the margin gets painful. We build directly on Meta's WhatsApp Business Cloud API: same official surface, no markup, full control over templates, webhooks, and conversation routing. For some teams that's the right answer. For others — especially smaller volumes or teams that want a managed dashboard — a BSP is genuinely the better choice. We'll tell you which, then build whichever you pick. The work itself includes template approval (the part where most projects stall), opt-in flows that pass Meta review, conversation routing into your CRM or support tool, two-way messaging with operator handover, rich-media handling (PDFs, images, location pins), and full audit logs for compliance. If you're running paid marketing into WhatsApp, we also wire conversion tracking back into Meta Ads and your analytics stack.

About this service

Direct API or BSP?

Both are legitimate — picking the wrong one costs real money

Direct integration with Meta's WhatsApp Business Cloud API gets you the lowest per-conversation cost and full control over the message pipeline. The trade-off is that you (or we) own everything: template submission, webhook reliability, opt-in compliance, deliverability, the lot.

A BSP (Twilio, MessageBird, 360dialog, Vonage) hides the operational complexity behind a managed surface and a dashboard. The trade-off is per-message margin — usually 0.5x–2x Meta's cost — which compounds painfully past tens of thousands of conversations a month. We'll model both costs against your projected volume and pick the one that wins for you.

Templates and opt-in

The part most projects stall on

WhatsApp Business has strict rules on what you can send outside of an active 24-hour conversation window: only pre-approved template messages, only to users who explicitly opted in, only in categories Meta has approved for your business.

We handle the template submission process (utility, marketing, authentication categories), build the opt-in capture flows that pass Meta review, and structure your messaging program so you don't get throttled or shut off. We've taken multiple programs from zero to approved-template-live in under three weeks.

Two-way conversations and operator handover

WhatsApp is a support channel, not a broadcast channel

The biggest mistake we see is treating WhatsApp like SMS — fire-and-forget. The reason WhatsApp works as a channel is because the user replies, and now you're in a 24-hour service window where you can have a real conversation. That conversation needs to route somewhere: a CRM, a support tool, an AI agent, or a live operator.

We build the routing layer: incoming messages tagged and routed to the right team, operator handover with conversation history, escalation rules, SLA timers, and a clean handoff between bot and human when the bot reaches the edge of its competence.

What we build

Real whatsapp business api patterns we’ve shipped

Not adjectives. Specific shapes of build we’ve taken to production for clients like you.

  • E-commerce order updates

    Template messages for order confirmation, shipping, delivery — with reply-to-track and reply-to-chat-with-support flows wired into your support tool.

  • Appointment reminders + reschedule

    Utility-category templates 24h and 1h before appointments, with one-tap reschedule or cancel that updates your booking system directly.

  • Two-factor and OTP delivery

    Authentication-category templates for OTP delivery, retry handling, rate limiting, and Meta-compliant template wording.

  • AI-powered support concierge

    Incoming WhatsApp messages routed to an [AI agent](/services/ai-agent-development) that handles common questions and escalates to a human operator for the rest — with full conversation handover.

  • Lead-capture from Click-to-Chat ads

    Meta Ads → Click-to-WhatsApp → automated qualifying conversation → lead written into your CRM with the right tags and source attribution.

  • Internal field-team comms

    Two-way WhatsApp surface for distributed field teams (delivery, sales, maintenance) — checking in, reporting status, uploading photos to your back-office.

  • Multilingual customer support

    WhatsApp is the dominant channel in many non-English markets — we build multilingual conversation routing with per-region templates and operator queues.

Process

How a WhatsApp Business API engagement actually runs

Five concrete steps with deliverables. No retainer fog.

  1. Volume + cost modelling

    We model your expected conversation volume against direct-Meta vs. BSP pricing, including templated vs. service conversations, and pick the architecture that wins for your numbers.

  2. Meta Business + WABA setup

    Business verification, WhatsApp Business Account creation, phone number provisioning, display name approval. We handle the back-and-forth with Meta so your team doesn't have to.

  3. Templates + opt-in design

    We write the templates (utility, marketing, authentication), submit them through Meta's review, and build the opt-in capture flows on your website or app that satisfy Meta's compliance requirements.

  4. Routing + operator surface

    Webhook receivers, conversation state, routing rules, operator handover UI, escalation timers, and full conversation logging into your CRM or support tool.

  5. Launch + ongoing optimisation

    Public launch behind your WABA, monitoring on deliverability and template approval status, and a 30-day support window for the inevitable Meta-side surprises.

Pricing

Real brackets, no surprise invoices

Starting points. Exact quote on the scoping call — written, fixed, no hourly surprises.

WABA Starter

Single-template program, 2–3 weeks

from £3,500
  • Meta Business + WABA setup
  • Up to 3 templates approved
  • Simple opt-in + reply flow
  • Webhook receiver + log
Most picked

Conversational Production

Two-way at scale, 5–8 weeks

from £11,000
  • 10+ templates approved
  • Two-way routing + operator handover
  • CRM / support-tool integration
  • Multi-language conversation flows
  • Click-to-WhatsApp ads wiring
  • 60 days of support

WABA Retainer

Ongoing template + flow work

from £3,500/mo
  • New templates submitted monthly
  • Meta policy change tracking
  • Deliverability monitoring
  • On-call for incidents
Questions

Things real buyers ask before paying

If yours isn’t here, ask on the scoping call.

Ready to scope a WhatsApp Business API build?

60-second AI consult and you’ll leave with a written plan. Prefer humans? Drop a custom quote request — we reply within a working day.