LOGISTICS · SYSTEM

AI booking automation for hauliers

IN SHORT

Every inbound booking read, validated against capacity and drivers' hours, priced from your rate structure and put in front of a planner as a decision — not a data-entry job.

The problem

Bookings arrive as free text: an email with a postcode and a pallet count, a forwarded spreadsheet, a phone call scribbled on a pad. Someone re-keys each one into the TMS while the phone rings, and the errors that creep in — wrong postcode, wrong window, wrong rate — surface later as failed deliveries and credits.

How it works

Inbound bookings are read and the details extracted: collection, delivery, window, goods, vehicle type, references. The system checks them against your live capacity and the relevant drivers' hours, prices from your rate card or the customer's agreed schedule, and presents the planner with a complete booking to accept, amend or reject. Anything ambiguous or off-schedule is escalated rather than guessed.

Where the money is

Two places. Planner hours returned to actual planning, and fewer re-key errors reaching the road, where each one costs a wasted run plus a credit.

What you get

  • Booking details extracted from email, attachments and forwarded threads
  • Validated against live capacity, vehicle type and drivers' hours
  • Priced from your rate card or the customer's agreed schedule
  • Off-schedule rates and ambiguous bookings escalated to a person
  • Confirmation sent to the customer once a planner accepts

Questions we get asked

Can it handle customer spreadsheets?
Yes — recurring customer formats are the easiest case, because the layout repeats. Irregular one-off formats are read too, with a lower confidence threshold for escalation.
Does it book work without a human?
Only if you explicitly want that for a named customer on standing traffic. The default is that a planner accepts every booking.
How long does it take to build?
Typically four to six weeks for a first version covering your highest-volume customers, then extended as it proves itself.

TRUST & CREDENTIALS

How we work, and what stands behind it

This page is maintained by Forth Systems. Everything listed below describes our own team, hosting choices and the technologies we build on — it is a statement of practice, not an independent certification or an endorsement by the vendors named.

UK team & data residency

Who builds it, and where your data sits while they do.

  • UK-based engineers

    Edinburgh-headquartered. Every system is designed, built and supported by our own UK-based engineering team — no offshore delivery pool.

  • UK / EU hosting by default

    Applications and databases are provisioned in UK or EU regions unless you require otherwise, with encryption in transit and at rest.

  • Human-in-the-loop by design

    Every AI system we ship keeps a manual override. Nothing irreversible happens without an operator able to review, edit or stop it.

  • Audit trails as standard

    Automated actions are written as first-class records — who or what did it, when, against which input — so operations stay evidence-ready.

Systems we build on

The platforms our systems run on. These are the technologies we deploy and support — not sponsorships or reseller badges.

  • OpenAI, Anthropic & Google models

    Model-agnostic delivery. We route each workload to the model that fits it on cost, latency and accuracy, and can switch without a rebuild.

  • Supabase & Postgres

    Row-level-security Postgres as the operational spine under every platform we run.

  • Stripe payments

    Payment capture, checkout and reconciliation wired directly into job and permit workflows.

  • Xero, Sage & HubSpot integrations

    Production integrations into the finance and CRM systems UK operators already run, so automation lands where the business keeps its records.

Streetworks & industry credentials

Operational domains we build in daily, with the sector systems we integrate against.

  • DfT Street Manager integration

    The permit chain we built for Kerbco creates and tracks streetworks permit applications against DfT Street Manager and local highway authority processes.

  • NRSWA-aligned workflows

    Permit, reinstatement and traffic-management workflows built to the New Roads and Street Works Act process contractors are inspected against.

  • Traffic management planning

    Roadplan produces signing and guarding layouts for council submission and for the crew installing them on site.

  • Operator-built, not consultancy-built

    Our platforms are built around real operating workflows — including the permit chain we built for our client Kerbco, a Scottish drop kerb contractor.

Insurance certificates, registration numbers and security documentation are available on request — ask the team.