New order
Please find attached our transport request from Lyon to Lille.
order_2847.pdfAI operator for transport workflows
Your transport files, connected across your tools, guided by your rules.
Your operations do not have to adapt to Vigilo. Vigilo adapts to the way they actually work. It connects emails, portals, documents and software, rebuilds the context, carries out the approved action, verifies the outcome and hands decision-ready exceptions back to your team.
One product foundation, configured for your operation.
The same building blocks — detection, transport files, rules, actions, verification and supervision — are configured around your environment, then extended with your team.
Your tools
API, file exchange or an existing interface: the right interaction method is selected for each system.
Your operating practices
Documented rules, useful operating habits and exceptions are translated into an explicit scope.
Your evolution
When a tool or operating practice changes, the workflow is updated and verified before it resumes.
Controlled expansion
Start with one bounded workflow, then add new cases after operational approval.
A transport file never lives in a single tool.
It starts in a message, takes shape across documents and moves forward through operational decisions.
Recent orders
No.DestinationStatus
Order ASite 1New
Order BSite 2New
Order CSite 3Review
UNH+1+ORDERS:D:96ABGM+220+ORDER-SAMPLE+9NAD+BY+SHIPPER+SITE1NAD+DP+DESTINATION+SITE2DTM+137:20260729:102QTY+21:12:PCENew order
UNH+1+ORDERS:D:96ABGM+220+ORDER-SAMPLE+9NAD+BY+SHIPPER+SITE1NAD+DP+DESTINATION+SITE2DTM+137:20260729:102QTY+21:12:PCENew order
Please arrange this shipment for Thursday morning.
order_2847.pdfOrders arrive by email, portals, EDI and phone.
A new event reaches the transport file.
Every new piece of information can change what happens next. Vigilo detects the change, identifies its source and connects it to the right transport file.
Order receivedNew email
Consignment note addedDocument received
Time slot confirmedStatus changed
Vigilo captures the signalIncoming event detected
Active monitoring · the right event reaches the right transport file
Context carried forward
The transport file moves forward.
The request, actions, checks and decisions stay connected to the same file.
End-to-end traceability
The file gains context without losing its history.
Requests, changes, cancellations, proof and invoice discrepancies remain connected to the same file.
Request receivedNew email from a shipper
Transport request to assess
File createdTransport file created
Data connected to its sources
Action completedTMS updated
Change received within 24 hours · trace retained
Events recordedWaiting time +42 min
Change received within 24 hours
Actual waiting time recorded
Invoice receivedInvoice discrepancy detected
Waiting-time and change fees not applied
Candidate ruleApproval required
Control proposal submitted to the team
Beyond execution
Your company’s operational memory.
Documented rules, observed decisions and outcomes remain connected to the files that explain them. A recurring decision first becomes a candidate rule, whose scope and exceptions must be approved by the team.
Governed learningFrom observation to an approved rule
Documented ruleDefined with the team
Starting pointRepeated decisionComparable cases identified
To assessCandidate ruleScope and exclusions proposed
Approval requiredOperational approvalEnabled only within the approved scope
Human decisionOperationalmemoryKnowledge connected to real transport files
Transport filesFrom request to invoice
Operating rulesConstraints and practices
DecisionsApproved with their rationale
ExceptionsHandled in context
HistoryPlanned, delivered, corrected
ChecksOutcomes and invoicing
The company can finally ask
ReliabilityWhich shippers cancel at the last minute?
Real complexityWhich transport files are changed most often?
QualityWhere do invoice errors keep recurring?
PerformanceWhich customers are eroding margins?
CapacityWhich orders are easiest to absorb?
NegotiationWhich rules should be included in the next contract?
One file, from event to decision
A transport file never lives in a single tool.
Vigilo connects scattered information and maintains one continuous context, from order intake to invoice control.
EmailsPortalsEDICalls
What Vigilo does
Context becomes actionable.
Detect the relevant event
Each new email, document or status change reaches the right file and can change what happens next.
Identify the operating intent
Vigilo extracts the relevant facts and compares them with documented rules and decisions made in similar situations.
Rebuild the context
The request, its source, history, constraints and stakeholders are brought together.
Act in your existing tools
Vigilo uses an available connection or the existing interface, only within the approved scope.
Verify the outcome
The resulting state is read back, checked against the intended outcome and recorded.
Hand off sensitive decisions
The team receives the sources, relevant rule, attempted action and reason work stopped.
End-to-end traceability
The file gains context without losing its history.
Requests, changes, cancellations, proof and invoice discrepancies remain connected to the same file.
- Request received
New email from a shipper
Transport request to assess.
- File created
Transport file created
Data connected to its sources.
- Action completed
TMS updated
Change received within 24 hours, trace retained.
- Proof connected
Consignment note verified
The actual waiting time is recorded in the file.
Waiting time: +42 min - Invoice received
Discrepancy detected
Waiting-time and change fees have not been applied.
- Candidate rule
Approval required
The proposed control must be approved by the team before it is enabled.
Beyond execution
Your company’s operational memory.
Documented rules, observed decisions and outcomes remain connected to the files that explain them. A recurring decision first becomes a candidate rule, whose scope and exceptions must be approved by the team.
- Transport files, operating rules and decisions connected
- Exceptions and history retained
- Recurring decisions proposed as candidate rules
The company can finally ask
Which shippers cancel at the last minute?
Where do invoice errors keep recurring?
Which customers are eroding margins?
Trust
Technology that shows what it did — and where it stopped.
Defined scope
Approved actions, operating rules and exceptions are explicitly defined.
Verified outcome
The resulting state is checked against the intended outcome before an action is marked complete.
Decision-ready handoff
Sensitive cases return to the team with their sources, the relevant rule and the reason work stopped.
Resources & analysis
Practical guidance for making every step of a transport workflow more reliable.
In-depth guides, operating methods and analysis for operations, customer administration, finance and leadership teams.
Your starting point
Which workflow still keeps your team busy?
Tell us about the flow, tools and decisions that still require manual work.
Assess this workflow