WhatsApp

WhatsApp is the chat that drivers, carrier dispatchers and many consignees answer. The Business Platform is Meta's official Cloud API for messaging them from a number your company owns. Connected to Cargofy, that number becomes a working channel: digital workers ask for documents, send updates and collect quotes, and every reply lands on the load. Dispatch managers usually switch it on, with IT holding the Meta access token.

What teams use it for

Collect the signed POD on delivery day

PODs often come back days later with the driver's paperwork, or as a blurry photo in a personal chat. When Tracking marks the stop complete, a digital worker sends the driver a template message asking for the signed POD. The driver replies with a photo, which is attached to the load in Documents. The read receipt shows the driver saw the request, and the invoice can go out the same day.

Send customers status updates

When a load changes status in Tracking (picked up, in transit, delivered), a digital worker sends the customer's contact a template message with the load number and new status. Customer replies come back over the webhook and are attached to the load. If a reply reports a problem, the worker raises an exception for the operator. The customer service rep sees the whole thread on the load and steps in when a person is needed.

Chase carrier quotes in one thread

A load in Load Hub needs cover. A digital worker sends a WhatsApp quote request to each carrier contact on the lane, with lane, equipment and dates. Carriers answer in chat, and each reply arrives over the webhook. The worker parses the quoted rate and writes it onto the load in Load Hub. The dispatcher compares the quotes on one screen and books the carrier from there. Carriers install nothing.

Remind before detention and demurrage accrue

Detention is usually noticed after it is billed. A digital worker sends the carrier or consignee contact a reminder before free time runs out, with the load and the deadline in the message. If the driver taps a quick reply to confirm arrival, the timestamp lands on the load. The dispatcher sees who was warned and when, which is the record you need when the carrier's invoice arrives.

Turn a driver's delay message into an exception

A driver stuck at a border crossing who writes to a personal number is easy to miss. When he writes to your business number, the message arrives over the webhook and a digital worker raises an exception on the load, with the original message attached. Interactive lists and quick replies let drivers send structured answers with one tap. The operator handles the exception in Cargofy.

How it fits your stack

The load stays the system of record in Cargofy; WhatsApp is the channel. Cargofy sends template and interactive messages from your WhatsApp Business number and reads replies, media and delivery receipts back onto the load. Setup is an API key: your admin enters the phone number ID and permanent access token in Cargofy settings and points the Cloud API webhook at Cargofy. A conversation older than 24 hours can only be reopened with a registered template, and personal WhatsApp accounts are not covered.

Who it is for

Shippers and forwarders whose drivers, carriers and consignees answer on WhatsApp, which in most markets is nearly all of them. Dispatchers chase PODs and quotes, customer service sends updates, and the IT admin owns the Meta Business access token. Fleet owners with their own drivers get the same POD flow.