PlatformCollaborative

Reach the recipient
on the app they actually open.

WhatsApp, SMS and anonymous voice, driven by the same delivery events as the rest of the platform. Messages go out in the recipient's language, from your own WhatsApp Business Account, and you can see which ones were delivered and read.

01Why it matters

An SMS nobody opens
is a delivery nobody is home for.

Recipients have been trained to ignore SMS — it looks like spam, and increasingly it is. Meanwhile the one message that would have saved the delivery, the one asking where exactly the front door is, never gets answered. Reaching people where they already read their messages is not a nicety; it is the difference between a first-time delivery and a second van.

Messages that get read

WhatsApp carries a read receipt, so you know. When a number turns out not to be on WhatsApp, the message falls back to SMS by itself.

Addresses corrected before departure

When a geocode is doubtful, the recipient is asked to drop a pin. The delivery address updates from their answer, with the change traceable in task history.

Numbers stay private

Driver and recipient reach each other through a masked line, so neither keeps the other's number after the delivery.

One thread per delivery

Every message on every channel, automatic or sent by hand, in one chronological view on the task — with its delivery status beside it.

02Features

What goes out, and when.

Configured once per platform by your administrator, then driven by the delivery itself.

The moments that matter

Round started, ETA approaching, time window approaching, driver a set distance from the door, previous task completed, task completed, task failed. Each one on or off, per channel.

Three channels, one configuration

WhatsApp, SMS and email are set up the same way, with the same variables. A trigger can fire on more than one at once.

The recipient's language

Taken from the contact, falling back to the platform's language and then the notification's default. No per-recipient work.

Your WhatsApp account

You connect your own WhatsApp Business Account and keep your own number and templates. We are registered with Meta as a technology provider, not a reseller.

Fallback without a rule to write

A number that is not on WhatsApp falls back to SMS automatically — except where the recipient opted out, which is honoured rather than worked around.

Address confirmation

Sent only when the address could not be placed with confidence, so it reaches the deliveries that need it rather than everyone.

Anonymous calling

A driver who cannot find the door calls through a masked number. The call is traceable; the phone numbers are not shared.

Delivered, read, failed

Per-message status on the task and across the platform in the system monitor, with an API to pull the same history into your own tools.

03In context

Where it sits.

Pillar
Collaborative
Requires
Your own WhatsApp Business Account
Works with
CommunicationCustomer Track & TraceTicketing

Outbound today. A recipient can answer the address request, and that answer is acted on — but replies to an ordinary message are not yet shown in the platform, and a dispatcher cannot open a WhatsApp conversation by hand. Both are being built. WhatsApp message costs sit on your own Meta account, and templates are approved by Meta before first use.

How many of your deliveries
fail at the front door?

Tell us what you send recipients today and on which channel. We will show you the same journey on WhatsApp, including the address request.

Stay on top of the latest industry insights

Subscribe to our newsletter.