8 freight business processes with AI agents is the list a Mexico control tower actually uses, not a demo catalog. They run end to end: from asking for capacity to paying (or holding) with evidence. Fits with the pillar AI agents for business processes.

It is the map of work your team does today across WhatsApp, GPS portals, TMS, customer service, and AP.

Why these 8 processes (not an infinite list)

Each process has four pieces. If any is missing, it is a loose task, not a process:

  • A clear goal
  • Systems where it happens
  • Evidence it leaves
  • An exception that escalates to a person

On Mexico–US the natural cycle is capacity, trip, and delivery to payment with SAT.

#ProcessTypical KPI
1Tendering / assignment% cover on time
2Load confirmation (booking)Complete data at departure
3GPS mirror trackingMinutes to alert
4Exception managementETA / appointment recovered
5POD / ePOD capture% trips with evidence
6CFDI intakeXML tied to the trip on arrival
7Carta Porte 3.1 validation% complements OK
8Pre-pay auditMXN recovered / held
Eight processes, one cycle: from tender to pay.

Infographic: 8-process map (PDF)

One-pager for pilot kickoff: the 8 processes on a single page, with the tower vs AP cut.

The 8 processes, explained simply

1. Tendering / assignment

Goal: offer capacity, log the response, and build cover without lost WhatsApp threads.

  • Contacts carriers under rules (lane, rate, scorecard)
  • Updates the TMS and escalates if there is no unit
  • Computer use matters when the carrier’s “system” is a group chat or portal, not an API

2. Load confirmation (booking)

Goal: close the booking with data that feeds the trip (appointment, unit, operator, references). Without this, tracking and Carta Porte are born broken.

  • Confirms and validates minimum fields
  • Leaves the file ready for the tower

3. GPS tracking with mirror account

Goal: read the carrier’s read-only portals, apply geofence, and alert in minutes. Typical computer use case: there is no single API.

  • Unit idle near the DC
  • Appointment at risk from ETA

4. Exception management

Goal: classify delay, appointment impact, detention, and next action. A chatbot only narrates; the agent leaves a trail for OTIF and disputes.

  • Reschedule or find cover
  • Notify customer service
  • Update status and notify owners

5. POD / ePOD capture

Goal: tie delivery evidence (dock, app, WhatsApp, signature) to the shipment ID. Without usable POD there is no defensible delivery or safe accessorial.

  • Collects, classifies, and attaches to the trip
  • Does not “assume delivered” because GPS got close

6. CFDI intake

Goal: when the XML hits AP (email, portal, folder), tie it to the correct trip. If it fails, you pay blind.

  • Separate pretty PDF from stamped XML
  • Feed Carta Porte validation and pre-pay audit

7. Carta Porte 3.1 validation

Goal: verify the complement on the buyer side. It is not stamping. Issuance and PAC live in the how-to how to create Carta Porte 3.1.

  • Locations, commodity, unit, operator, IdCCP
  • OCL verifies; the carrier stamps

8. Pre-pay audit

Goal: match rate + CFDI + Carta Porte + GPS + POD and approve, hold, or dispute. This is where typical 5-7% recovery shows up.

Method: freight invoice audit.

How to choose where to start the pilot

  1. Honest baseline

    Capture hours, % invoices audited, minutes to GPS alert, MXN in dispute.

  2. Pick 1-2 processes

    If you pay blind, 6+7+8. If OTIF is chaos, and 3+4. If cover fails a 1+2.

  3. Freeze one lane

    One customer or corridor (e.g. Bajío–Laredo). Not the whole network.

  4. Run 6-8 weeks

    Measure and decide scale. Playbook: stop capturing shipments.

Elige un paso para ver el detalle

Detalle del paso · 01

300+ shipments/month

Filter 1

Threshold where headcount ROI usually closes.

How OCL runs them

OCL Cargo is an autonomous TMS: agents with computer use run assignment, tracking, POD, and audit on your operation. On tax it verifies CFDI and Carta Porte; it is not a PAC. It coexists with the system of record you already have or operates as a TMS that executes.

Approach comparison: RPA vs agents that operate screens. Definition pillar: agents for business processes.

Related reading

Key takeaways5 points
  1. The 8 processes close the freight cycle: tendering, booking, GPS mirror, exceptions, POD, CFDI, Carta Porte, and pre-pay audit.
  2. A useful agent runs the process with evidence; it does not only summarize chat.
  3. In Mexico the differentiator is many portals + CFDI/Carta Porte 3.1 before paying.
  4. Prioritize by measurable ROI (hours, minutes to alert, 5-7% of freight) on a 6-8 week lane.
  5. OCL is an autonomous TMS with computer use; it verifies tax documents, it is not a PAC.

Frequently asked questions

Pick one lane, 1-2 of these 8 processes, and measure hours and MXN in 6-8 weeks. That beats any “agent transformation” slide.

See the 8 processes on real shipments