whatsapp
WhatsApp Business+ PickPack

Connect WhatsApp Business Platform to PickPack for delivery updates, ETA, exceptions and POD

WhatsApp Business Platform can be the channel customers receive delivery updates through. PickPack provides the context: which real delivery events happen in the field, when to send a message, in which Template Category, what placeholders to fill, and what to do with inbound replies.

See the WhatsApp Business Platform driving real delivery updates in a 20-minute demo.

PickPack + whatsapp business api integration — delivery management visual
The Challenge

What’s broken today when WhatsApp Business meets delivery

In most organizations

The technical ability to send a WhatsApp message isn’t the missing piece.

What’s missing is context: knowing exactly when to send,

what to write, and ensuring the message is genuine and not spam.

Teams send updates manually

sometimes twice, sometimes late.

Sometimes a message gets sent after the delivery has already happened.

The Solution

PickPack adds the delivery execution layer on top of WhatsApp Business

WhatsApp Business continues to manage the records. PickPack takes the field connection from there — planning, execution, measurement and closure.

  • Real-time route optimization by vehicle capacity, time window and priority
  • AI-powered automatic driver dispatch — no manual coordination
  • Driver app with navigation, barcode scan, signature and POD capture
  • Statuses that flow back automatically to WhatsApp Business: ETA, en route, delivered, exception
  • WhatsApp and SMS updates to the customer with a live tracking link
PickPack workflow — from WhatsApp Business to POD
LayerResponsibility
WhatsApp Business PlatformWABA, Phone Number, Display Name, Message Templates, Template Categories, Approved Templates, 24-hour session window, Webhooks, Quality Rating and Opt-in/Opt-out.
PickPackDelivery events: Delivery created, Driver en route, ETA, Exception, Failed delivery, POD captured, and the decision of when to trigger a message and to whom.
The connection between themSending a payload from PickPack to WhatsApp with a Template ID and placeholders, and receiving Sent/Delivered/Read/Failed status or an inbound customer reply.
The Connection

What flows between WhatsApp Business and PickPack

The minimal data that has to pass for a delivery to happen — and what flows back when it closes.

Fields that flow

From PickPack to WhatsApp Business PlatformWhy it matters
Customer phone (E.164)The destination of the message.
Template name + Template languageSelecting the correct Approved Template.
Body placeholdersName, order number, ETA, time window, exception reason, Tracking Link.
Header media (if relevant)POD image, route map or logo.
Button payload (Quick Reply / URL)Tracking link, confirmation or a conversation with the team.
Reference IDDelivery ID for linking replies back.
Channel preferenceWhatsApp only, SMS fallback, or both.
The Experience

What the driver sees. What the customer gets. What the team controls.

Three different points of view — all running on the same PickPack layer, synced automatically with WhatsApp Business.

PickPack driver app

Driver App

Optimal route, built-in navigation, barcode scan, signature and POD capture. The driver just executes — PickPack has already coordinated.

PickPack customer updates

Customer Experience

WhatsApp or SMS with a live ETA, tracking link and delivery confirmation. The customer doesn’t have to call — they already know.

PickPack ops dashboard

Operational Control

All live deliveries, real-time KPIs, flagged exceptions and proofs of delivery — all on one screen.

Implementation Paths

Four ways to connect — you choose the pace

You don’t have to start with a deep integration. Most customers move from file → automation → native integration within 3-6 months.

1

Cloud API (Meta)

Sending messages through Meta’s Graph API directly from PickPack or via middleware.

2

Business Solution Provider (BSP)

Such as 360dialog, Vonage, MessageBird, Sinch, Infobip — they provide a managed layer over Cloud API plus templates.

3

Twilio WhatsApp

For teams already on Twilio — that page is separate, but the logical connection is similar.

4

Two-way Webhooks

Status updates and inbound messages.

FAQ

FAQ

Does PickPack send WhatsApp messages automatically?
Yes. PickPack can drive WhatsApp messages through the WhatsApp Business Platform — either directly via Meta’s Cloud API or through a Business Solution Provider you already use. The messages still travel over the WhatsApp layer and remain bound by your Approved Templates, your WABA and Quality Rating. We don’t market this as an official Meta Tech Provider or certified BSP relationship unless we confirm it with you in writing.
What should stay inside WhatsApp Business Platform?
WABA, Phone Number, Display Name, Message Templates, Template Categories, Approved Templates, 24-hour session window, Quality Rating and Opt-in/Opt-out policy stay with the platform and the BSP. PickPack neither manages nor replaces them.
Which delivery events can trigger a message?
Events like Delivery created, Driver assigned, Driver en route, ETA updated, Driver near customer, Delivery exception, Failed delivery and Delivery completed with a POD link can trigger a message, subject to the correct Approved Template and Template Category.
What’s the difference between the WhatsApp Business Platform page and the Twilio page?
Twilio is a multi-channel communications provider (SMS, Voice, WhatsApp) with its own API. WhatsApp Business Platform is Meta’s platform. You can send WhatsApp messages through Twilio, through Cloud API directly, or through another BSP. Our two pages describe different processes that may overlap, and the integration design follows whichever system you already use.
How do you handle Quality Rating?
PickPack doesn’t manage Quality Rating, but the logic of when to send affects it directly. In the demo we review message frequency, relevance, Category alignment, SMS fallback when needed, and automatic suppression of updates for customers who Opt-out or send STOP.
Can we start without a full Cloud API?
Yes — you can start through an approved BSP with basic templates, or via Twilio WhatsApp in some cases, and move to direct Cloud API once volumes grow and operational requirements are clear. Either path still respects Approved Templates, Quality Rating and Opt-in policy.
Related Integrations

More integrations in the Communications & Customer Updates category

Browse other platforms in the same category. Each card opens the full integration page.

Ready to get started?

Connect WhatsApp Business to PickPack

Send us your Approved Templates and a sample delivery scenario. In a 20-minute call, a PickPack specialist will walk you through exactly how delivery events trigger the right Template at the right moment — across Cloud API or your BSP — with ROI numbers grounded in actual field data, not slideware.

Let's Talk!

We invite you to ask anything that is on your mind, our staff will be happy to assist you whatever your need is.

Let's Talk!

Skip to content