Hire another freight coordinator or automate the follow-up?

Key Takeaways

Before approving a freight coordinator requisition, sort every task in the job description into two lists: follow-up and repetitive coordination, or judgment, relationships and exceptions.
The list that is growing decides the answer. If follow-up is growing, a new hire mostly buys more chasing. If judgment work is growing, a hire is usually right.
Weigh what a hire brings (coverage, flexibility, ramp-up, knowledge that can leave) against what automation needs (written rules and an owner for approvals).
Hiring is the right call when the gap is relationships, escalations, a new mode or a missing decision owner, not messages per load.
Wilson, by Cartage, is an AI logistics agent that runs the follow-up side of a coordinator role under the company's rules, so the requisition can be rewritten around judgment work.

Should the open coordinator role be a hire or automated follow-up?

Hire when the growing work in the job description needs judgment, relationships or ownership of exceptions. Automate first when the growing work is follow-up: chasing quotes, confirming pickups, asking for ETAs and requesting PODs.

A requisition usually opens after a rough stretch, and the job description written afterward lists everything the team does, as if the new person were one more unit of the same work.

But a coordinator role is a bundle. Some tasks repeat on every load with the same steps. Others exist because someone has to decide, negotiate or own a problem. A new hire takes both; automation takes only the first. The useful question is which part of the bundle is pushing the team over the edge.

If the team still needs to size the shortfall, the capacity-per-load model answers how many loads it can carry.

A three-step guide to deciding the requisition

The job description is the working document. Each line gets sorted, tested and then kept, moved or rewritten.

Step 1: Split the job description into two lists

Follow-up and repetitive coordination: quote requests, chasing carriers that have not replied, tendering to the next carrier after a decline, confirming pickup windows, check calls, customer ETA updates, POD requests, matching invoices to the booked rate.
Judgment, relationships and exceptions: paying above target on a load that must ship today, talking to a carrier after repeated service failures, a key customer's escalation, a damage claim, a new lane or mode, a broken process.

Mixed lines get split. Manage exceptions contains a follow-up part (contact the carrier, find who can cover) and a judgment part (approve the costlier rebooking, decide what to tell the customer).

Step 2: Test which list is growing

Pull recent shipment history, email or spreadsheets and ask which list is rising faster than load count. Follow-up grows when the LTL share rises, more carriers lack tracking feeds, or new customers want an update on every order. Judgment grows with strict appointment rules, more claims, a new mode or carrier rates that keep moving.

Step 3: Weigh the factors, then rewrite the requisition

Apply the decision rules below to each list. If follow-up dominates the growth, automate it first and check whether the remaining judgment work still fills a role. If judgment dominates, hire, and keep follow-up off the new person's plate.

What each option actually requires after the decision

Neither option adds capacity on day one. A new coordinator has to learn the operation, and automated follow-up has to be given the rules.

A new coordinator learns which carriers answer email and which only answer the phone, which customers need appointment numbers and which lanes run late on Fridays. Once trained, the person can handle almost anything new. Much of what they learn lives in their inbox, and it leaves with them.

Automated follow-up needs the team to write down what it already knows: approved carriers and tender order, rate targets, approval limits, contacts and update cadence per customer. Someone owns the approval queue, because routine actions start under assisted execution. Escalations still need a named owner. But the rules are written and every message, confirmation and change is recorded in the shipment history, so the knowledge stays when people change roles. The preparation list is in how much work a team does during AI onboarding.

Which factors should tip the decision?

Score each factor against the two lists from Step 1, not against the team in general.

Peaks. A hire sized for peak sits underused off-season; one sized for the average still drowns at peak. Follow-up rises with load count, so it is the part of a peak rules can absorb. Peak judgment calls still need people.
Coverage. A hire adds one more person's hours. Automated follow-up runs on the schedule the rules set rather than one person's shift, but an escalation still waits for someone on duty.
Ramp-up. A hire needs training, often from your busiest coordinator; automation needs rules and a period of approvals.
Knowledge loss. If the role has turned over before, written rules shrink what leaves next time.
Rules setup and approvals. If nobody has time to write rules or approve actions, start with one workflow on a few lanes.
Cost. Use your own loaded labor cost for the role, from finance, not a published salary. To price the follow-up side, what carrier follow-up costs a manufacturer counts it from your own loads.

When hiring is the right call

The growing list is judgment: key accounts, claims, carrier conversations beyond rate targets.
Nobody owns exceptions today. Escalations need a person who can decide.
The team is entering a mode or region with no expertise or carrier relationships.
The rules do not exist yet: no approved carrier list, rate targets or approval limits.
The function depends on one person, and a second is about resilience, not volume.

Worked example: sorting one coordinator job description

A sample job description, sorted. Everything in it is illustrative, not drawn from any customer.

Task from the job description	List	Growing? (illustrative)	Who should take it
Request quotes from approved LTL carriers	Follow-up	Yes, LTL share rising	Automate
Chase carriers that have not replied	Follow-up	Yes	Automate
Confirm and reconfirm pickup windows	Follow-up	Yes	Automate
Send ETA updates to customers who ask on every order	Follow-up	Yes, two new accounts	Automate
Request PODs and attach them to the order	Follow-up	Flat	Automate
Match carrier invoices to the booked rate	Follow-up	Flat	Automate under approval rules
Approve a rebooking above the rate target	Judgment	Flat	Team
Work damage claims with carriers	Judgment	Flat	Team
Set up appointment rules for a new retail customer	Judgment	Yes	Team, or the new hire
Review service and rates with core carriers	Relationship	Flat	Team

How to read it: six of ten lines are follow-up, and four of those are growing. Only one judgment line is growing. A new hire here would spend most of the week on work rules can carry. The better move is to automate the follow-up first, then decide whether the retail setup and carrier reviews justify a narrower role focused on accounts and carriers.

How Wilson, by Cartage, takes the follow-up side of the role

Wilson runs the follow-up list from the worked example under the company's rules and hands the judgment list back to people.

Wilson is an AI logistics agent that replaces the TMS for freight execution and connects to the company's ERP or order flow: an ERP feed, scheduled file drop, spreadsheet, email or API.

Wilson requests quotes from the company's approved carriers, tendering its own carriers first, and negotiates against rate targets within approval limits. It books, confirms pickups and tracks each load through the best source available: carrier API, GPS or ELD data where available, the carrier's website by PRO number, and email or calls otherwise. It updates the team in Slack or Microsoft Teams and customers by email or SMS, collects PODs, audits and reconciles carrier invoices, and pays carriers from the Wilson Wallet under approval rules. When no approved carrier accepts, or a decision falls outside the rules, Wilson escalates.

Wilson starts with assisted execution, and scope expands step by step. It is onboarded like a new team member, with its own email address on the company's domain; Cartage helps map the first workflow during discovery. Timing depends on scope: most teams start on a few lanes and expand from there.

Bring the job description for the coordinator role you are hiring for and see in a demo which of its tasks Wilson would run, and which still need the person you hire.