WhatsApp Business API integration UK businesses own end to end

What is the WhatsApp Business API, and how is it different from the WhatsApp Business app?

The WhatsApp Business API, which Meta now calls the WhatsApp Business Platform, lets software send and receive WhatsApp messages on a business number. The WhatsApp Business app is a phone app for one person or a very small team; the platform is for connecting WhatsApp to systems.

With the app, a person types every reply, perhaps with saved quick replies and an away message. With the platform, your shop can send a dispatch message the moment an order is fulfilled, a booking tool can send tomorrow's reminder, a chatbot can answer “where is my order?” at midnight, and five staff can reply from one number without passing a phone around.

Most UK businesses we speak to arrive at WhatsApp Business API integration because the app has stopped scaling. A salon owner cannot answer forty rebooking chats a day while cutting hair. A Shopify brand finds customers ignore dispatch emails but read WhatsApp. A property maintenance firm wants tenants' repair photos to land in its job system, not on an engineer's personal phone.

We are three freelance developers in India: one of us builds the integrations, another of us handles AI and cloud hosting, and the third of us plans flows and templates with you.

How do UK businesses use WhatsApp Business API integration?

The strongest use cases are transactional: messages customers expect and want, triggered by something they did. Bookings, reminders, order updates and support replies all fit; unsolicited promotions fit least well, both legally and commercially.

In the UK we see a clear pattern by sector. Online shops send order confirmations, dispatch notices with tracking links, delivery-day alerts and return confirmations. Salons, clinics and tutors send booking confirmations and next-day reminders that customers can reply to with “reschedule”. Trades and property maintenance firms collect photos and addresses before quoting. Restaurants and takeaways confirm orders and table bookings. Car garages send MOT and service reminders to customers who agreed to receive them.

• Bookings: choose a service and slot inside the chat, with reminders and easy rescheduling.
• Order updates: confirmation, dispatch, delivery and returns, from Shopify, WooCommerce or your own system.
• Support: a chatbot answers routine questions and hands the conversation to staff.
• Quotes: customers send photos and details, which land in your CRM or job software.
• Account alerts: invoices due, documents ready, appointments changed.
• Marketing: offers and launches, but only to people who opted in, and with care.

Takeaways weighing WhatsApp ordering against marketplace apps should also read our takeaway online ordering guide.

Meta Cloud API directly, or a provider such as Twilio or 360dialog?

Go direct to Meta's Cloud API when you want the simplest cost structure and a developer is building the integration anyway. Use a provider when you already rely on its other channels, need its ready-made tools, or want a supplier to handle onboarding for you.

Meta hosts the Cloud API itself, so there is no server of Meta's software to run. Your integration talks to Meta's endpoints, and Meta bills message fees to your business account. Providers, known as Business Solution Providers, sit between you and Meta: Twilio adds WhatsApp to a wider messaging and voice platform, and 360dialog focuses on WhatsApp access with its own dashboard and developer tools. Providers may add their own fees or plans on top of Meta's charges, so check the full cost before choosing.

For most small and mid-sized UK firms we recommend the direct Cloud API. It removes a middle layer, keeps the Meta assets clearly in your own business portfolio and makes costs easy to read. We use Twilio when a client already sends SMS or makes calls through it and wants one supplier, and we work with 360dialog or other providers when a client is already set up there.

What does WhatsApp Business API setup involve?

Setup has four parts: a Meta business portfolio, a phone number registered to the platform, a business display name and profile, and the integration code that sends and receives messages. The Meta part takes days; the integration takes longer.

First we create or use your Meta business portfolio, the account that owns your WhatsApp Business Account, and add a phone number. The number must be able to receive a verification code by SMS or call. A number registered on the platform is generally used through the API rather than the ordinary app, so many businesses use a dedicated number; we check the options for your existing one before anything is moved.

Next come the display name and profile: logo, description, address and website. Business verification with Meta is worth doing early, because it is one of the routes to higher messaging limits. Then we build the integration: webhooks that receive customer messages, code that sends replies and templates, and connections to your shop, CRM or calendar.

• Meta business portfolio owned by your business, with you as admin.
• Phone number chosen and registered; existing number options checked.
• Display name, logo, description and website entered.
• Business verification submitted.
• Message templates drafted and submitted for approval.
• Webhook endpoint hosted in your cloud account, secured and logged.

How do WhatsApp message templates and per-message pricing work?

Templates are pre-approved message formats you must use to start a conversation or message someone outside the 24-hour customer service window. Since 1 July 2025, Meta charges per delivered template message, with the rate depending on the template category and the recipient's country.

Meta's pricing documentation sets out four categories. Marketing templates cover promotions and offers. Utility templates cover updates about something the customer has already started, such as an order or booking. Authentication templates carry one-time passcodes. Service messages are free-form replies to customers who contacted you, and Meta states these are free.

Timing changes the bill. When a customer messages you, a customer service window opens for 24 hours from their last message. Inside it, free-form service replies cost nothing, and Meta's documentation says utility templates sent within an open window are free as well. Meta also opens a 72-hour free window when a user starts the chat from a Click to WhatsApp ad or a page call-to-action button.

Practically, this means you should design flows so customers start conversations where possible, keep order and booking updates in the utility category, and reserve marketing templates for opted-in customers. Meta publishes current per-country rates, which we use to estimate your monthly running costs in the quote. Check the WhatsApp Business Platform pricing documentation for the latest rules.

Is WhatsApp marketing legal in the UK? PECR and Meta opt-in rules

Yes, if people have opted in. Two sets of rules apply: UK law, mainly PECR alongside UK GDPR, and Meta's own WhatsApp Business Messaging Policy. Both point the same way: get clear permission before sending marketing, and make opting out easy.

The ICO's PECR guidance defines electronic mail broadly, including text messages and direct messages via social media or similar services. For individuals, marketing sent this way needs specific consent, unless the soft opt-in applies: the person bought or negotiated to buy a similar product from you, and you gave them a clear chance to opt out when you collected their details and in every message. The ICO notes the soft opt-in does not cover new contacts or bought-in lists. Read the ICO guidance on electronic mail marketing for the detail.

Meta's policy adds its own condition: you may contact people only if they have given you their number and you have received opt-in permission confirming they want to receive messages from you on WhatsApp. So even where PECR's soft opt-in might allow a marketing email, Meta still expects a WhatsApp-specific opt-in.

What we build: opt-in checkboxes that name WhatsApp explicitly, a record of when and how each person agreed, separate consent for marketing versus order updates, and a “STOP” keyword that suppresses future marketing immediately. We do not advise on your legal position; your own solicitor should sign off wording for campaigns.

WhatsApp Business API integration with Shopify and WooCommerce

Shop events trigger utility templates: order placed, payment confirmed, fulfilled with tracking, out for delivery, returned. The integration listens for those events and sends the right message to customers who agreed to WhatsApp updates at checkout.

On Shopify, webhooks for orders and fulfilments tell our integration when something changes. We map each event to a template, pull in the customer's name, order number and carrier tracking link from Royal Mail, Evri, DPD or whichever courier you use, and send it. Replies from the customer land in the shared inbox or chatbot, so “can I change my address?” reaches someone who can act on it.

On WooCommerce, the same idea runs through order status hooks or the REST API. For custom shops, we connect to whatever events your system already produces. Abandoned-checkout reminders are possible but count as marketing, so they go only to customers who opted in to marketing messages, not just order updates.

• WhatsApp opt-in at checkout, separate from email marketing consent.
• Order confirmation and dispatch templates in the utility category.
• Tracking links from your courier, not a generic homepage link.
• Replies routed to staff with the order attached.
• Returns and refund status updates triggered from the order record.

Stores that also want more organic traffic can read our ecommerce SEO guide for UK shops, since better search visibility means more orders for WhatsApp to update.

Connecting WhatsApp to a CRM, booking tool or job software

Every WhatsApp conversation should end up attached to the right customer record. Without that, messages live in an inbox nobody else can see, and the history disappears when a staff member leaves.

For CRMs such as HubSpot, Zoho CRM or Pipedrive, we create or match the contact by phone number, log each inbound and outbound message, store the opt-in status and timestamp, and let staff send templates from the record. For booking tools, a WhatsApp booking creates the appointment, and changes in the booking tool trigger confirmation and reminder templates back to the customer.

Trades and field-service firms often want photos. A customer sends pictures of a damp patch or a broken boiler display, the integration stores them in the job record, and the office sees them before quoting. Where job software offers an API we write to it directly; where it does not, we use its email-in or an integration platform.

Building WhatsApp chatbot flows that customers do not hate

Keep flows short, offer buttons for common choices, answer from your own content, and let people reach a human quickly. Meta's messaging policy requires prompt, clear and direct escalation paths when you use automation, such as transfer to a human agent, a phone number or an email.

There are three levels of automation. Button menus guide customers through fixed choices such as “Track order”, “Book” or “Talk to us”. WhatsApp Flows are forms inside the chat for structured input: pick a date, choose a service, enter a postcode. AI assistants understand free text and answer from your policies and FAQs, which suits support with varied questions.

We often combine them. A greeting offers three buttons; a booking uses a Flow; anything typed freely goes to an AI assistant limited to your approved content; and the words “human”, “agent” or “complaint” route straight to a person. The assistant never invents delivery dates, refunds or prices; it looks them up or passes the chat on.

• First message offers the three most common tasks as buttons.
• Every path includes a way to reach a person.
• Answers come from your documents, not the model's general knowledge.
• Out-of-hours replies say when a person will respond.
• Conversation summaries passed to staff at hand-off.

For a deeper look at grounding AI answers in your content, see our UK AI chatbot development page.

WhatsApp messaging limits and quality rating

New WhatsApp business portfolios start with a messaging limit of 250 unique customers per rolling 24 hours for business-initiated messages outside a customer service window. Limits rise as you verify your business or send enough high-quality messages.

Meta's documentation describes the paths to 2,000: verify your business directly, have a partner verify it, or send 2,000 delivered template messages to unique users within 30 days using templates with a high quality rating. Beyond 2,000, limits scale automatically when your messages stay high quality and you use at least half your current limit over seven days, moving up through 10,000, 100,000 and unlimited.

Quality depends on how recipients react. If many people block or report your messages, quality drops and your ability to send suffers. That is another reason to send only messages people expect: order updates they asked for, reminders for bookings they made, offers they opted into. Replies to customers who messaged you first do not count against the limit, because they fall within a customer service window.

For most UK small businesses, 250 is plenty at launch. Shops planning a Black Friday campaign or a large reminder run should verify early so the higher limit is in place before the busy period.

How much does WhatsApp Business API integration cost in the UK?

There are three cost layers: the build, Meta's message fees, and hosting or provider fees. With us, a custom WhatsApp Business API integration starts from US$600 to build; Meta fees and hosting are billed to your own accounts.

The build cost depends on scope. A single flow, such as Shopify dispatch updates with a shared inbox, sits near the starting price. A booking assistant with WhatsApp Flows, CRM logging and an AI support layer costs more. A multi-branch setup with several numbers, routing rules and a custom dashboard may belong in a bespoke software project from US$900.

Meta's fees depend on your message mix. Customer-initiated service replies are free; utility templates inside the service window are free; marketing, authentication and out-of-window utility templates are charged per delivered message at Meta's published UK rate. A shop sending dispatch updates to customers who have not messaged recently will pay utility rates on each. A salon whose customers mostly message first will pay very little.

Hosting for the webhook and integration is usually modest on a small cloud server or serverless setup, billed to your own AWS, Google Cloud or similar account. If you choose Twilio or another provider, their fees apply too. We estimate all three layers in the quote so there are no surprises.

How long does a WhatsApp Business API integration take?

Most integrations take two to four weeks from approval. Meta account setup and template approval happen in parallel with the build, so they rarely hold things up if started on day one.

Week one covers the Meta business portfolio, number registration, display name, business verification submission and first template drafts. We also agree every flow in writing: what triggers each message, the exact wording, and what happens when a customer replies.

Week two is the integration: webhooks, sending logic, connections to Shopify, the CRM or booking tool, and the shared inbox. Week three is testing with real phones, including edge cases like a customer replying to an old order or sending a voice note. Complex projects with AI assistants or several systems run into week four.

After launch we monitor template performance, delivery failures and quality rating for the first weeks and adjust wording where customers seem confused. That is covered by two months of free maintenance.

Security, data storage and ownership

Your Meta business portfolio, WhatsApp Business Account, phone number and integration code all belong to you. We work as users or developers you add, and you can remove us at any time.

On the technical side, webhook endpoints verify that requests genuinely come from Meta before processing them. Access tokens are stored as secrets in your cloud account, not in code. Messages and attachments stored for your CRM or inbox sit in your own database or storage, with retention you set, so old conversations are deleted on schedule rather than kept forever.

Under UK GDPR you remain the controller of your customers' data, and your privacy notice should explain that you use WhatsApp for updates and support. Meta and any provider you use process data under their own terms, which you should review. We document what is stored, where, and for how long, so your adviser can check the notice against reality.

• Meta assets in your business portfolio, never ours.
• System user tokens with minimum permissions, stored as secrets.
• Webhook signature verification on every request.
• Retention rules for messages and media in your storage.
• Handover document covering flows, templates, hosting and credentials.

Working with a WhatsApp developer team in India from the UK

India is four and a half hours ahead of UK summer time and five and a half in winter, so we overlap with your late morning and afternoon. Naturally, we talk on WhatsApp, seven days a week.

Kickoff is a video call on Zoom, Meet or Teams to walk through your customer journey: where people first contact you, what they ask, what your staff repeat every day. After that, testing is easy to share, because you can see every message on your own phone as we build.

Quotes and invoices are in USD, paid from the UK via Wise, bank wire or PayPal. The itemised quote comes in about two working days and nothing is billed before written approval. Invoices come from India; your accountant can confirm the VAT treatment of overseas services.

A worked example: WhatsApp Business API integration for a hypothetical Bristol bike shop

Imagine a Bristol bike shop with a Shopify store for parts and a busy workshop for servicing. Staff spend hours on the phone telling customers whether their bike is ready. This is an illustration, not a client.

The integration would have two halves. For the online shop, Shopify webhooks trigger utility templates: order confirmed, dispatched with a tracking link, delivered. Customers opt in at checkout with a WhatsApp-specific tick box. For the workshop, a WhatsApp Flow lets customers book a service slot, pick the service level and leave the bike's make and model, creating the booking in the shop's calendar.

When a mechanic marks a job complete in the workshop system, a “your bike is ready” utility message goes out with opening hours. Because many customers reply with questions, the customer service window opens, and follow-up replies are free service messages. A small AI assistant answers opening-hours and parts-availability questions from the shop's own content and hands anything technical to the workshop manager.

Marketing would be separate: a spring service reminder sent only to customers who ticked the marketing box, with a STOP keyword. The build would likely sit a little above the US$600 starting price because it connects both Shopify and a booking calendar.

WhatsApp Business API integration UK checklist

Work through this before launch. It covers the Meta setup, UK consent rules and the details that decide whether customers find WhatsApp helpful or annoying.

• Meta business portfolio owned by your business, with two admins.
• Phone number decided, and the effect on any existing WhatsApp app use understood.
• Business verification submitted early.
• Templates written for the correct category: utility for updates, marketing for offers.
• WhatsApp-specific opt-in captured and recorded, with a separate marketing consent.
• STOP or unsubscribe handling tested end to end.
• Every automated flow offers a clear route to a person.
• Replies land in a shared inbox or CRM, not one staff member's phone.
• Privacy notice updated to mention WhatsApp.
• Monthly Meta fee estimate agreed based on your expected message mix.

Want automation beyond WhatsApp, such as email triage or quote generation? Our AI automation page for UK SMEs covers what to automate first.