Transport planning (traffic / planning loads) decides which load moves, with which carrier, and at what rate.

On Mexico–US lanes that role is often the silent bottleneck: every extra shipment is another round of messages. The useful change is assisted assignment: the agent closes the loop; your team detect, review, and intervene on capacity exceptions.

loads · offer · acceptance
Traffic
milestone on the file, not only chat
Trail
measured lane (OCL pattern)
6-8 wks
capacity and rate with team judgment
Exceptions

The problem: planning as a chat loop

The planner does not only build the trip. They chase capacity, confirm rate, fight appointments, and leave (or fail to leave) a trail tower and AP can use later.

  • Offers on WhatsApp with no milestone in the TMS.
  • Verbal acceptance nobody binds to the shipment ID.
  • Rework when the tower asks who was assigned.
  • Seasonal peaks that demand overtime or more planners.

For the process map an agent can execute (including tendering), see 8 business processes with agents.

A typical day in planning / traffic

The open is a queue of day loads. Each one means messaging two or three carriers, chat follow-up, and a late capture in the TMS.

CEDIS yard with trailers at docks: capacity and appointments traffic planning owns
Traffic: offer and acceptance with a trail on the trip ID, not only in chat.

By midday, verbal acceptances appear without a milestone. By close, the tower inherits doubt and AP has no clear rate for the pre-pay match.

  • Offer sent; no trail of who replied.
  • Carrier that “can” and then never confirms.
  • Rework because the trip ID has no bound carrier.
  • Volume spike that only survives with overtime.

Before vs now with OCL

Automating planning is not another planning module. It is tendering with a trail: offer, acceptance, and milestone on the same ID, with the planner on exceptions.

Planning / traffic

From chat offers to assignment with a trail

Before

  1. 1.Build the load

    Origin, destination, window

  2. 2.Offer by chat

    Several carriers, no milestone

  3. 3.Verbal acceptance

    Late capture; tower doubts

With OCL

  1. 1.Load on the ID

    Constraints on the same trip

  2. 2.Offer with a trail

    Agent sends and records

  3. 3.Capacity exception

    Planner decides plan B

What your team reviews

Missing capacity, out-of-range rate, or carrier no-close.

Planning scales on network exceptions, not every chat.

Impact: time, volume, and satisfaction

The bottleneck is rarely “thinking the network”. It is round-trip time with each carrier. Measure time freed, loads per planner, and fewer surprises downstream.

Role impact

Time · Volume · Satisfaction

Illustrative patterns · 6-8 wk pilot

  1. Time

    Less back-and-forth on offers

  2. Volume

    More loads per planner

  3. Satisfaction

    Fewer surprises downstream

Planning frees time when it stops chasing acceptance by hand.

Your team stays with the exceptions

Any issue can still be detected, reviewed, and acted on. The agent does not replace network judgment: it executes the routine offer and acceptance loop.

The planner supervises and decides when capacity is missing, the rate is out of range, or there is a commercial exception. Tower and CS inherit a clean ID, not an ambiguous chat.

  • Your team: capacity, out-of-range rate, and carrier plan B.
  • Agent: offer, follow-up, and acceptance milestone.
  • Result: more loads with the same planning team.

What you get in 6-8 weeks

A measured planning lane makes clear what is automated and what stays team judgment. You leave with evidence to decide the next lane.

6-8 week pilot

Four deliverables. One decision.

  1. Deliverable 1

    Baseline

    • Time to assign
    • % without acceptance
    • Rework to tower

  2. Deliverable 2

    OCL vs manual capture

    • Agent closes the offer
    • Planner decides plan B

  3. Deliverable 3

    Deltas

    • Less back-and-forth
    • More loads
    • Fewer surprises

  4. Deliverable 4

    Week 6-8 decision

    • Expand
    • Adjust
    • Stop

OCL pattern · typical 300+ shipments/month.

Key takeaways5 points
  1. Transport planning (traffic) builds the load and assigns a carrier; if that lives in WhatsApp, volume asks for more people.
  2. Automation means tendering with a trail: offer, acceptance, milestone, and escalate if there is no close.
  3. With computer use the agent operates portals; people decide capacity and commercial exceptions.
  4. Any issue can still be detected and reviewed; the planner steps in when the routine loop is not enough.
  5. Illustrative patterns and OCL canon (6-8 week lane). No invented Promologistics KPIs.

Does your planning assign, or chase chats?

In a demo we build an assignment lane with a trail: offer, acceptance, and milestone. Then we connect GPS, POD, and audit. Finished work, not another planning sheet.
Book a demoSee 8 processes with agents

Related reading

Frequently asked questions