Recognise incoming bookings
Use trusted customer rules and structured extraction to identify operational movement details from incoming email.
Outrig automation
Stop entering information your business already received.
Outrig's automation layer is being built to turn incoming transport information into structured operational records while keeping important decisions under operator control.
Built for UK haulage operators.
Incoming booking emailBooking request · Reading
Rollout featureOUTRIG EXTRACTS
CustomerLucy Electric
CollectionThame, OX9
DeliveryReading, RG2
Delivery date15 Sep 2026
Weight1,800 kg
Site contactMissing
Operator review requiredReady to create enquiry
Automation with boundaries
Remove repetitive input without giving software uncontrolled authority.
Outrig's booking-ingestion design keeps absent information null, surfaces missing fields and requires operator approval before complete booking information becomes operational work.
Create an enquiry immediately
Even an incomplete booking can become a visible enquiry instead of remaining hidden in the inbox.
Expose missing information
Missing values stay missing. Outrig is designed not to invent addresses, weights, dates or other operational details.
Keep operator approval
A complete source still requires operator approval before being linked into the operational job workflow.
Handle amendments safely
Reschedules and changes create a before-and-after proposal rather than silently overwriting an allocated job.
Preserve the audit trail
Source messages, decisions and accepted changes remain tied to the tenant's operational history.
Example workflow
From inbox to structured transport work.
The goal is not to make email disappear. It is to stop the office manually re-keying information that has already arrived.
01Customer emailBooking arrives
→02Outrig readsTrusted source
→03Extract fieldsNo invented values
→04Create enquiryMissing fields visible
→05Operator approvesHuman control
→06Job workflowDriver ready
Booking amendmentProposed job change
ReviewBEFOREDelivery: 15 Sep · 10:00Reading, RG2
AFTERDelivery: 15 Sep · 13:30Reading, RG2
Reject changeAccept amendment
Operational safety
Changes should be proposed, not silently applied.
When a live booking changes, Outrig's current design creates a before-and-after amendment proposal. An allocated, non-final job can then require driver acknowledgement once an accepted update affects their work.
Where this goes next
Automation across the transport office.
Booking ingestion is the first clear pattern. The same principle can extend to repetitive administrative workflows as they pass production acceptance.
Booking emailsIn rollout
Missing-info chasingFeature flagged
Maintenance documentsPlanned
Compliance updatesPlanned
POD chasingPlanned
Accounting integrationsPlanned
Automation availability will be described feature-by-feature at launch. Outrig will not market preview-only workflows as universally production-ready.
Let software remove the re-keying.
See how Outrig is being built to connect the information already arriving in your transport office with the operational workflow that follows.