Logistics & trade compliance · Solution

Creating a shipment shouldn't take twelve screens. Dispatch builds the job.

Each request is checked against your minimum requirements. Anything missing becomes one drafted chase email; anything complete becomes a CargoWise job, waiting for a person to confirm it once.

Sits on top of
CargoWiseOutlookShared mailboxesMicrosoft Teams

Every shipment starts the same way: check the request is complete, chase what's missing, key it into CargoWise, then go back and fix the record. Urgent jobs wait behind the incomplete ones.

15–30 min

absorbed by a job that should take 5

10,000

shipments a month created from email, at one UK forwarder

3 passes

check, chase and key, then fix the record later

What it does

What Dispatch handles.

  1. 01

    Check it's complete first

    Each request is checked against your minimum requirements before anyone starts keying, so gaps are found at intake, not halfway through.

  2. 02

    One chase, not five

    Everything missing goes into a single drafted email to the customer, which a person reviews and sends.

  3. 03

    Confirm once, then it's built

    A complete request becomes a CargoWise job with the references in the right fields, after one confirmation.

  4. 04

    Keep the record clean

    Incomplete or inconsistent jobs are flagged with what's wrong, so fixes happen before billing or customs trips over them.

  5. 05

    After the job exists

    Proof of delivery attaches to the job, milestones update, and the customer notification is drafted for review.

See it working

From request to job, with one confirmation

Two sample requests: one complete, one missing details. Each goes where it should, and nothing is written until a person says so.

Live demoSwitch the request, then confirm the job.

How it plugs in

How it plugs in

Dispatch sits between the inbox and CargoWise. The only write it makes is the one a person confirms.

Where requests arrive today

OutlookShared mailboxes
Requests, read by Relay
Dispatch

Checks the request, then builds the job.

  • Checked against your minimums
  • One chase for everything missing
  • The job built and waiting
The built jobYou confirm

When it's complete

CargoWise

The job is written with the fields in place.

Drafted chaseYou press send

When something's missing

One chase email to the customer
Rule

Nothing reaches CargoWise without the confirm step, and nothing reaches a customer without a person pressing send.

01

Agree the minimums

What a request must contain before a job is built, per service and mode.

02

Map to your job templates

Fields land where your team expects them in CargoWise, in your reference formats.

03

Confirm in one place

Review the built job and approve it, in the browser or in Teams.

04

Watch the record

Incomplete jobs stay flagged with what's missing until someone fixes them.

What Dispatch works with

CargoWiseOutlookShared mailboxesMicrosoft GraphShipment documentsMicrosoft TeamsExcelFirstTracMicrosoft Entra IDCargoWiseOutlookShared mailboxesMicrosoft GraphShipment documentsMicrosoft TeamsExcelFirstTracMicrosoft Entra ID

Questions people ask first

Dispatch

Keying every job by hand?Stop.

Tell us how a shipment request reaches your team and what gets keyed into CargoWise. We'll show you what confirm-once looks like on your jobs.