How to avoid losing orders between email, WhatsApp and phone calls

In brief

Email, WhatsApp and the phone are not “wrong tools”. They are highly effective communication channels. The problem starts when they also become the only record of operations. A delivery may be ordered by email, changed by phone and confirmed in chat: a few hours later, no one knows which information takes precedence.

The answer is not to ban the channels used by customers and drivers. It is to introduce one rule: every piece of information that changes the work must go into the operational source for the order. The message remains evidence or context; the order record contains what has to be carried out.

The problem is not WhatsApp: it is fragmentation

In a very small company, the owner often knows everything by heart. With three or four trucks, the system seems to work because one person keeps calls, customers and drivers together. As orders, vehicles or colleagues increase, individual memory becomes a bottleneck.

The signs are easy to recognise:

• someone looks for “the last email” before calling a driver;
• two people have different versions of the same address;
• a change received on a personal phone does not reach a colleague;
• the customer asks why an instruction was not followed when it had not been recorded;
• billing and operations have to reconstruct afterwards what happened.

Establishing one operational source

The single source does not necessarily have to be sophisticated software. At an early stage it can be a well-designed spreadsheet or a shared database. It must, however, meet four requirements:

1. every order has an identifier;
2. there is one current version of the operational information;
3. relevant changes can be traced;
4. authorised people can access the data when needed.

This logic is often called a single source of truth: it does not mean there is only one document in the whole company, but that it is clear which source takes precedence for each item of operational information.

How to handle email, phone calls and chats

Email

It is useful for receiving structured orders, attachments and confirmations. When it contains a new assignment, the data must be recorded in the order record. The email can then be linked or archived as a reference.

Phone call

It is the fastest and least structured channel. If an address, time or quantity changes during a call, the change should be recorded as soon as possible. A later written confirmation can be useful for sensitive or disputable information.

WhatsApp or other chats

They are excellent for speed and updates, but a personal chat may be difficult for the rest of the company to access and mixes information from different orders. An important operational message must be entered in the order system; documents and photographs must be handled under company procedures and data-protection rules.

Contracts, orders and evidence of changes

Italian Legislative Decree 286/2005 regulates contracts for third-party road freight transport and gives relevance to written form and to the elements of the relationship. How email, orders, confirmations and other documents help prove the content of the relationship depends on the individual case.

For this reason, when a change has an important economic or operational impact — for example, a different destination, additional waiting time, a second unloading point or a significant change to the goods — it is useful to keep a clear record and associate it with the order. There is no need to turn every call into a contract: there needs to be a way to reconstruct who requested what and when.

Access, backups and retention

Centralising orders does not mean making everything visible to everyone. An SME should at least ask these questions:

• who can change an order?
• who can see prices and commercial terms?
• do drivers see only the information necessary for the assignment?
• what happens if the dispatcher's computer fails?
• is there a backup?
• are accounts of former employees or collaborators disabled?
• are personal data retained only for the necessary time and purposes?

Among other principles, the GDPR requires purpose limitation, data minimisation, accuracy and appropriate security. Even a simple order process should therefore avoid needlessly duplicating personal data across dozens of devices.

A minimum method for an SME

A very simple flow can be:

1. The request arrives. Email, phone, chat or portal.

2. The order is created. Identifier, customer, collection, delivery, goods, date and notes.

3. References are attached or linked. Email, documents, commercial agreement.

4. The work is assigned. Driver and truck.

5. Every change updates the record. The original channel does not remain the only source.

6. The order is closed. Delivered status and relevant documents.

7. It is archived with consistent criteria. Not one folder per person, but a criterion that makes the transport retrievable.

Practical example

At 09:00, an order from Milan to Genoa arrives by email. At 11:00, the customer calls and asks to bring the collection forward. At 13:00, they send a new reference number on WhatsApp to be given to the warehouse.

Without one source, there are three pieces of truth. With a structured flow, the order contains the updated time and new reference, while the email and message remain linked as context. The colleague taking over in the afternoon does not have to read the whole story to understand what must be done.

Checklist

• Is every new assignment recorded in one shared place?
• Are important telephone changes entered on the order?
• Are chats not the only archive?
• Is it clear which version of the order is current?
• Do prices and personal data have appropriate access controls?
• Is there a backup procedure?
• Is it possible to reconstruct the history of an important change?