WhatsApp for freight forwarders
Your customers do not always write an email. They send a WhatsApp message with an origin, a destination and a photograph of the packing list. That thread sits on one person's phone.
Every email your company receives is read, understood and turned into a task for the right person, with the answer already drafted. Your team approves. Nobody lives in the inbox any more.
Connect your WhatsApp Business account and those threads are read the same way. Same task screen. Same drafted reply. Same person approving before anything sends.
- 01WhatsApp is not a side channel in freight any more. Enquiries, packing-list photographs and “any update?” messages often arrive there before they arrive anywhere else.
- 02Connect your WhatsApp Business account and FreighAI reads those threads the way it reads a company mailbox. It does the work behind each message and hands the right person a task with the reply already written.
- 03FreighAI handles RFQs and customer updates on the channel most forwarders actually use.
- 04Your team approves every reply before it sends. Nothing goes back down a customer's thread on its own.
- 05WhatsApp has rules no vendor can change. They are set out below, in Meta's own words, before you plan around them.
The enquiry that never became an email
Freight work does not wait for a channel. It arrives wherever the customer already is.
A regular customer needs three pallets moved from Chennai to Rotterdam. They do not open Outlook. They message the salesperson they know, because that is who they have always messaged. Three pallets, ready Thursday, with a photograph of the packing list.
A forwarding business grows one shipment at a time. Every shipment brings more enquiries, more emails, more rates to find, more people to chase and more hand-offs between pricing, operations and accounts. Almost none of that work lives in a system. It lives in inboxes, browser tabs, WhatsApp and people’s heads. So the only way to handle more business has been to hire more people.
Read that again with WhatsApp in mind. The enquiry exists and the customer believes they have asked you. But nothing exists in a system, nobody in pricing has seen it, and the only person who can act is holding the phone. If that person is on a flight, the enquiry is not late. It is invisible. Meta lists “Send order confirmations and shipment updates” among the things its Business Platform is for, so this is not a habit your customers will grow out of.
- Which enquiries reach a phone before they reach pricing?
- How many packing lists arrive as a photograph, not a document?
- When the person who owns the thread is away, who else can see it?
The thread becomes a task with an owner
Connecting the channel does one thing above all others. It stops the conversation being private.
The message that used to arrive on a phone arrives in FreighAI instead, where the rest of the company can see it. FreighAI writes the reply, creates the task, and puts it in front of the right person in the right department, beside the original conversation. Your team approves. They do not compose, forward, file or chase. The reply goes out in their name.
The original conversation, here, is the WhatsApp thread. It sits beside the task, so the person approving reads what the customer actually said.
A WhatsApp message is only the start. The time goes on what comes after it. It pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system. Follow-ups, chasers and reminders happen on their own, on the same conversation.
- 01WhatsApp messageFrom a customer or an agent, with whatever they attached
- 02ReadWhat it is and what it needs
- 03The legworkRate cards, the carrier, the customer's history, your agents
- 04TaskTo the right person, with the thread beside it
- GATEYour team approves
- 06ReplyBack on the same thread, from your business number
- 07Your TMSThe record goes where you keep records
Keep your TMS for the records. FreighAI runs the work around them.
WhatsApp, end to end
Not a personal account. Meta describes a WhatsApp Business account as one that “represents your business and contains phone numbers, usernames, and analytics”. It stays yours.
Every message on that number lands where the rest of your work already is, photographs attached, against the conversation rather than one message at a time.
FreighAI pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system.
It writes the reply, creates the task, and puts it in front of the right person in the right department, beside the original conversation. Whoever owns that kind of work in pricing, operations, tracking or accounts gets it.
Your team approves. They do not compose, forward, file or chase. The reply goes out in their name. It goes back down the same thread, from your business number.
What your team can do once WhatsApp is connected
Reads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans. A photograph taken on a warehouse floor is a normal way for an enquiry to arrive.
It writes the reply, creates the task, and puts it in front of the right person in the right department, beside the original conversation. The thread becomes company work with an owner, visible to the people who have to act on it.
Handles RFQs and customer updates on the channel most forwarders actually use. Suggests a price from what that customer paid on that lane before, within your margin rules. When the customer pushes back on price, a counter-offer is drafted and waits for approval.
It answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval. Nobody is moved to a portal for an answer they asked for on WhatsApp.
Follow-ups, chasers and reminders happen on their own, on the same conversation. Chasing, tracking checks, quote expiry and follow-ups run on their own. Nobody has to remember.
Your people work in FreighAI, not in the inbox. Holiday cover becomes a rota question.
need DHL quote Gurugram → Ajman, 72kg, by Friday. express.
packing list attached. urgent pls 🙏
Pls quote for shipment as below. Confirmed pkg dims attached, IEC docs to follow…
It arrived as a photograph. The quote is already drafted.
This is the screen the person in pricing opens. The enquiry is there exactly as the customer sent it, and beside it is what FreighAI went and found.
- Reads the photographReads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans.
- Asks for the missing weightSpots what is missing in an enquiry and drafts the email asking for it.
- Chases your agentsEmails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply.
What connecting it involves
- 01
Decide which number the business answers on
In most forwarding companies this is spread across personal handsets. Meta says business phone numbers are “real, or virtual”. Pick the one your customers should write to.
- 02
Connect the account
The connection is made against your own WhatsApp Business account, so the number, the display name and the account remain yours. We scope the first workflow, integration requirements and implementation plan with your team.
- 03
Say who owns which kind of message
An enquiry belongs to pricing. A booking question belongs to operations. “Where is my cargo?” belongs to tracking. A payment chaser belongs to accounts. One session decides whose name each task lands under.
- 04
Agree what may be sent, and when
Meta says template messages “generally require approval before you can send them”, and require opt-in that “must clarify your business name and intent”. Decide which messages outside a live conversation are worth writing before you connect.
- 05
Run it beside your team for two weeks
Keep answering the way you do now, and let FreighAI work the same threads in parallel. Compare what it read out of each message with what your own person read. That finds the gaps more cheaply than moving a channel across on a Monday.
What the WhatsApp connection does not do
Worth knowing before you plan around it.
- FreighAI does not decide when WhatsApp will let you send. Meta says that “when a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts”, and that “when the window closes, you can only send pre-approved template messages”. An update three days later is a template, approved in advance, not a free-text reply.
- This connection is a reply engine. It answers threads your customers and agents started. It is not an outbound list and will not message people who have never written to you.
- What is connected is the business account. Messages arriving on a salesperson's personal WhatsApp are not part of it, and nothing is imported from a personal handset. Moving that traffic onto the business number is usually the harder half of the project.
- WhatsApp is not your record. The job and the customs entry stay in the system you already run, along with direct customs filing, duty lookup, statutory books, self-service portals and warehouse and fleet management. Keep your TMS for the records. FreighAI runs the work around them.
- A message that does not say enough is still a message that does not say enough. Nothing is guessed. Spots what is missing in an enquiry and drafts the email asking for it. Here that question goes back on the thread, and the quote waits for the answer.
What stays on WhatsApp, and what never leaves your own system
A connection is only useful when everybody knows which side of it a thing lives on.
| What it is | Where it lives | What the connection adds |
|---|---|---|
| The conversation | On WhatsApp, in the app your customer already has | The thread arrives in FreighAI, with the task beside it |
| The reply | Back in the customer's WhatsApp, from your number | Your team approves. They do not compose, forward, file or chase. The reply goes out in their name. |
| Messages outside a live conversation | Governed by Meta's rules, not by FreighAI | Nothing new. The template must exist and be approved first |
| The job and its documents | Your TMS or ERP, exactly as today | A won quote becomes a job on its own, fully filled in. |
- The conversation
- Where it lives
- On WhatsApp, in the app your customer already has
- What the connection adds
- The thread arrives in FreighAI, with the task beside it
- The reply
- Where it lives
- Back in the customer's WhatsApp, from your number
- What the connection adds
- Your team approves. They do not compose, forward, file or chase. The reply goes out in their name.
- Messages outside a live conversation
- Where it lives
- Governed by Meta's rules, not by FreighAI
- What the connection adds
- Nothing new. The template must exist and be approved first
- The job and its documents
- Where it lives
- Your TMS or ERP, exactly as today
- What the connection adds
- A won quote becomes a job on its own, fully filled in.
Almost no forwarding business runs on one channel. Connecting WhatsApp and not email leaves a single enquiry as two jobs, held by two people who each know half of it.
Your customers and agents, on the app they already use, writing to your business number.
Reads the thread, does the work behind it, creates the task, drafts the reply, waits for a person.
The job, the documents and the books stay where they already are.
Common questions
Do our customers have to install or learn anything?
No. They keep using WhatsApp exactly as they do now, writing to the same number. None of the connection is visible to them, apart from a faster answer.
Can FreighAI send a WhatsApp reply without a person seeing it first?
Your team approves every reply before it sends. The draft waits beside the thread, so the person who owns that customer reads what was actually said before agreeing to it. Your team approves. They do not compose, forward, file or chase. The reply goes out in their name.
What if the customer last wrote a week ago and we need to send an update?
Then WhatsApp's own rules apply. Meta says that “when the window closes, you can only send pre-approved template messages”. So an update a week later goes out as a template you wrote and Meta approved in advance. A vendor who implies otherwise is worth asking about.
Do we need the WhatsApp Business app or the Business Platform?
Meta publishes both. It describes the app as “built with the small business owner in mind”, and the Business Platform as its messaging API, where “the WhatsApp Business Platform Cloud API enables you to programmatically message and call on WhatsApp”. Which fits depends on how many numbers you answer on. We scope the first workflow, integration requirements and implementation plan with your team.
What happens to the threads our salespeople already have on their phones?
They stay where they are unless you decide otherwise. Nothing is imported on its own. Asking a customer to write to the business number instead is a conversation your salesperson has, and it is worth planning before anything is switched on.
- Meta for Developers — About the WhatsApp Business Platform: an account “represents your business and contains phone numbers, usernames, and analytics”; business phone numbers are “real, or virtual”verified 2026-09-03
- Meta for Developers — Service messages: the 24-hour customer service window, and “when the window closes, you can only send pre-approved template messages”verified 2026-09-03
- Meta for Developers — WhatsApp Cloud API overview: template messages “generally require approval before you can send them”, and require opt-inverified 2026-09-03
- WhatsApp Business Platform — lists “Send order confirmations and shipment updates” among its stated usesverified 2026-09-03
- WhatsApp Business App — “built with the small business owner in mind”verified 2026-09-03
WhatsApp is a Meta product. Everything here about how WhatsApp itself behaves is taken from Meta's own published material on the date checked, and nothing from a third party. No pricing or message-volume figure from that material is repeated.
Pick one WhatsApp thread from last week
One that started with a photograph and ended with three follow-ups. We will show what would have been read out of it, what FreighAI would have gone and found, and who would have been handed the task. Then you can decide whether it read that thread the way your own pricer would have.