AI, connected to your freight operations.
From incoming documents to your team’s decisions: explore how Zach, Microsoft 365 Copilot and your own agents relate to OneChain data.
Explore the use casesRead and structure. Find and prepare. Connect your tools.
Freight invoice
Incoming document → extracted data → updated shipment
OC-DEMO-1042
- Quote
- 2 450 €
- Invoice
- 2 550 €
- Discrepancy to review
- +100 €
The same freight sources, with access and review rules defined for each use case.
The right starting point for your work.
Process an incoming document, ask a freight question or build an internal workflow: each approach addresses a different situation.
Put your documents to work.
An invoice, a booking or a freight document arrives by email. Zach identifies the relevant shipment and uses the document’s information within workflows configured for your team.
- Match documents to shipments and retain their source.
- Extract useful fields and update the shipment according to workflow rules.
- Surface items that need review.
- Expected amount
- 2 450 €
- Invoiced amount
- 2 550 €
€100 to reviewAn item missing from the quote, for your team to review.
A question, and the context to answer it.
Your team works in Microsoft 365. Explore conversations that bring freight information together to prepare the next action: daily priorities, a delay, quote comparison or an invoice discrepancy.
Accessible data, approvals and actions are defined within the scope of your Microsoft 365 project.
Explore the Copilot conversations
Example conversation · fictional dataWhat caused the invoice discrepancy on shipment OC-DEMO-1042?
The quote totals €2,450. The invoice totals €2,550. The additional €100 relates to an item missing from the quote.
For review: the supporting explanation for these charges before approval.
Example sources: the shipment’s quote and invoiceFreight context in your own workflows.
You already have an assistant, a business tool or an internal automation. Let’s define the OneChain information it needs, its authorized operations and the connection method that fits your project.
API, CLI and MCP are access methods to assess with your technical team. Scoping distinguishes reading data, preparing an action and executing it.
Understand access for your agents- Your internal routine
Which shipments are waiting for proof of delivery?
- Authorized OneChain data
References, available documents and statuses for the relevant shipments.
- A summary for your team
Missing documents linked to their shipments, ready for follow-up planning.
What connects these use cases.
Useful information needs context. Choosing an interface goes hand in hand with identifying the sources to use and defining how your team works.
- Identifiable sources
- Link the result to the document, quote or shipment that explains it.
- A defined access scope
- Specify the data and operations each team, tool or agent needs.
- Explicit review rules
- Define what can be automated, what needs review and who handles exceptions.
Which task takes up too much of your day?
Start with a document, a question or a concrete workflow to identify the approach that fits your team.