AI in logistics, without exposing rates and drivers
Answer tenders, claims and schedules faster, yes, but never by pasting a rate grid or a driver’s data into an AI with no guarantees.
Road transport, removals, warehousing, order preparation: your files mix negotiated rates, shipper contracts and your drivers’ data, geolocation and tachograph included. Pasted into consumer AI without a data processing agreement, they leave your control; the nLPD still holds you responsible for them.
Your dispatchers and drivers already use AI to write. The point is not to ban it, but to set what enters the tool and what never does.
- Hours lost to quotes, tender responses and claims handling
- Rate grids and shipper contracts pasted into public AI, beyond your control
- Geolocation and tachograph data handled without a frame, under your responsibility
- A damage file incomplete when the claim arrives, and liability shouldered by default
See for yourself
A prompt structured in 5 blocks: Instruction · Role and audience · Data · Constraints · Format. An unframed AI invents; the frame stops it.
In a workshop, we adapt these prompts to your operation, each with its safeguards: no driver data, no client rate ever enters a public AI.
Réponse à l’appel d’offres d’un chargeur
A response built point by point on the shipper’s specifications, missing no requirement and promising nothing your operation cannot hold.
See it in Chaptal →Répondre à une réclamation · retard, livraison manquée, erreur d’adresse
A factual reply sent the same day, conceding what must be conceded without extending your liability.
See it in Chaptal →Le message qui refuse ou décale une course impossible dans les règles
A written refusal grounded in driving and rest time rules, protecting the driver without losing the client.
See it in Chaptal →30 use cases cover your line of work in the Chaptal catalog, out of 750 in the corpus · each one states what it produces, what it expects from you, and what it refuses to do.
« Le Collaborateur, augmenté »
Your dispatchers and drivers learn to frame AI on their real files, quotes, tenders, claims, without exposing a client or a colleague.
See the training →AI usage audit
An inventory of your current AI usage, a register and clear rules before a rate grid ends up in the wrong tool.
See audit & advisory →Foire aux questions
Can I paste a shipper’s contract into an AI to summarize it?
Not as it is. Without a data processing agreement, whatever you paste leaves your control, rates and clauses included. Anonymize first, or keep it out; every card in the catalog repeats this safeguard.
Are my drivers’ geolocation and tachograph data concerned?
Yes. This is personal data about your employees, and the nLPD frames what your tools collect and who may read it. A catalog card is dedicated to what your telematics actually collects about your drivers.
Can AI build my delivery rounds for me?
It structures the approach, sectors, constraints, stop order, and drafts the plan. Knowledge of the ground and the decision remain with the dispatcher, who validates every round.
What can AI do after damage or loss of goods?
Build the file: timeline, reservations, documents, then draft the reply to the claim. It does not settle liability; that question is decided with your insurer and Swiss law.
Do I need a large fleet for this to be worth it?
No. A carrier with a few vehicles benefits first, because quotes, claims and schedules rest on few shoulders. The catalog prompts work as they are, with no technical setup.