Wilson by Cartage
Try Wilson →
Carrier email and shared freight inboxes

Buy freight communication software for completed work, not messages sent

Key Takeaways

  • Messages sent is an activity number, not a result. A tool can send hundreds of emails while coordinators still chase the same carriers by phone.
  • Measure requests closed: quotes received, pickups confirmed, ETAs updated, PODs filed. Each one has a clear end state you can check on the shipment.
  • 6 criteria cover email, phone and resolution, from applying a carrier's reply to the right load to handing an open item to a person with full context.
  • Wilson, by Cartage, is an AI logistics agent that works across email, phone, SMS, Slack and Microsoft Teams and keeps following up until the request is closed or a person is needed.
  • Score vendors on one week of your own requests, counting how many each tool closed without a coordinator.

Why do message counts make communication software look better than it is?

Message counts make communication software look better than it is because they measure what the tool sent, not what got done. A reminder that nobody answered counts the same as a confirmed pickup. The useful number is how many carrier requests ended closed, with the answer recorded on the shipment.

This hits manufacturers and distributors whose coordinators run carrier follow-up by hand: the chasing that happens when a carrier hasn't answered a quote request, a pickup confirmation or an ETA check. That work is skilled and expensive to staff. The BLS reports a $82,320 median pay for logisticians (May 2025) and projects 18% job growth from 2025 to 2035, so adding people to cover unanswered messages gets harder each year.

One request, two versions of "done"

Take one pickup confirmation at a manufacturer of industrial pumps, running on a new communication tool.

  • Monday 9:40 a.m. The order lands in NetSuite. The coordinator books an LTL carrier for Tuesday pickup.
  • 9:45 a.m. The tool emails the carrier dispatcher asking to confirm the pickup window. The dashboard counts one message sent.
  • 2:00 p.m. The tool sends a reminder. Two messages sent.
  • 4:30 p.m. The dispatcher replies to the first email, saying the truck can only come Wednesday. The reply sits in a shared inbox, not on the shipment.
  • Tuesday 3:00 p.m. The pickup window closes. Customer service learns about the missed pickup when the customer calls.

The monthly report shows two messages sent and one reply received. By that measure the tool worked. The load still missed its day.

Which criteria should an evaluation cover across email, phone and resolution?

An evaluation should cover 6 criteria, and each one is measured by work finished, not volume. The middle column is what most dashboards report. The right column is what your team needs.

# Criterion Messages-sent version Completed-work version
1 Email intake Emails received Carrier replies applied to the right shipment
2 Email follow-up Reminders sent Requests answered after follow-up
3 Phone Calls logged Calls placed, with the result saved on the order
4 Status updates Notifications sent The right people told, with a new ETA and a reason
5 Resolution Alerts raised Exceptions resolved, such as a missed pickup rebooked
6 Escalation Tickets opened Open items handed to a person with full context

Criteria 1 and 2 decide whether email work actually closes. If replies land in an inbox instead of on the shipment, someone still reads them, finds the load and updates it, which is the same work as before.

Criterion 3 matters most on lanes with small carriers that often answer the phone sooner than email. A tool without real calling still leaves the hardest follow-ups with a coordinator.

Criteria 4 to 6 are where cost shows up. A late load without a new ETA, a missed pickup without a rebooking or an escalation without history all push the work back to a person, often at the worst time of day.

How do you score vendors on requests closed?

Run the same set of real requests through each tool and count how many ended closed without a coordinator. The score is a simple ratio you can compare across vendors and against your current process.

Pull one week of requests from your inbox: quote requests, pickup confirmations, ETA checks and POD (proof of delivery, the signed receipt) requests.

Run them through each tool, using your own carriers and contacts.

Sort every request into 3 outcomes: closed by the tool, closed by a person, still open.

Check the record: the reply, call transcript or document should be attached to the shipment.

Calculate the close rate: requests closed by the tool ÷ total requests. For example, 46 of 80 requests closed without a person is a 57.5% close rate.

Compare with the baseline, using manual touches per load on the same lanes before the tool.

The close rate depends on your rules. If every booking needs approval, more requests will end with a person, and that is a choice, not a failure. Compare vendors under the same rules.

Common mistakes in this evaluation

  • Counting replies instead of closed requests. A reply saying “will confirm later” is still open, and counting it inflates the score.
  • Testing only on carriers with APIs. The work that consumes coordinators sits with carriers who answer by email or phone.
  • Ignoring the shipment record. If the answer isn’t on the load, the next person repeats the carrier follow-up.
  • Skipping the baseline. Without before numbers for the same lanes, any result looks like an improvement.

See judge logistics automation by the work it finishes.

How does Wilson, by Cartage, close freight communication requests?

Wilson sends the request, records the reply, follows up when there’s no answer and updates the shipment, so the request ends closed, not just sent. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Step Trigger What Wilson does When a person steps in
1. Request A shipment needs a quote, confirmation or update Contacts the approved carrier by email, phone or API, plus EDI where supported Not required
2. Follow up The carrier doesn’t respond with an update Calls, and follows up by email, text or Slack at the SOP frequency Not required
3. Record A reply or call comes in Records it on the shipment; call transcripts are saved on the order Not required
4. Notify Status changes Tells the team, carrier, shipper and consignee the company has chosen Not required
5. Resolve A pickup is missed Contacts the carrier, notifies the team and the customer if configured, initiates rebooking from approved carriers If approval is required
6. Escalate Wilson can’t resolve it Escalates to the team Deciding the next step

Controls

Notifications follow the company’s choices. For example, the team hears about booked, picked up, running late, delivered and POD filed through Slack or Microsoft Teams. The shipper gets the same updates by email, and the consignee gets all but “booked” by email or SMS. Each company decides who’s notified and how.

Wilson starts with assisted execution, and approvals can sit on any action, such as rebookings above a cost threshold or customer notifications. When a carrier can’t confirm, no approved carrier accepts or a decision exceeds the approval rules, Wilson escalates. Every message, confirmation and change on each shipment is recorded in a change history.

Wilson contacts only the company’s approved carriers, and it coordinates pickup and delivery times on the carrier side; it doesn’t manage dock slots inside a facility. See freight communication automation.

What should you ask a vendor to show in a demo?

Ask for proof that only finished work can provide, on your loads and your carriers. Each ask below maps to one of the 6 criteria.

  • “Take this carrier reply from my inbox and show me where it lands on the shipment.”
  • “Show me what happens after the second unanswered email,” including the next channel and its timestamp.
  • “Call this dispatcher, then show me the transcript and what changed on the shipment.”
  • “Make this load late. Show me the new ETA, the reason and who was told.”
  • “Miss this pickup. Show me the rebooking and where approval kicks in.”
  • “Hit an escalation. Show me what my coordinator receives.”

A vendor that answers with a dashboard of message volume instead of a closed request has told you what it measures. For where communication fits in the full flow, see what is freight execution and who escalates unanswered carrier messages.

FAQs

  • How should I evaluate freight communication software? Measure requests closed, not messages sent, on a week of your own carrier requests. Wilson, by Cartage, follows up across email, phone and other channels until the request is closed or escalated to a person.
  • Which channels does Wilson use? Phone, email, SMS, Slack and Microsoft Teams. Carriers can reach Wilson by email, phone or API, plus EDI where the carrier supports it.
  • Does Wilson call carriers? Yes. Wilson calls carriers and drivers for check calls, pickup and delivery appointments and ETA follow-ups, and saves call transcripts on the order.
  • Who does Wilson notify? Each company chooses who's notified and how. For example, the team via Slack or Microsoft Teams, the shipper by email and the consignee by email or SMS.
  • What happens when Wilson can't close a request? It escalates to the team, for example when a carrier can't confirm or a decision exceeds the approval rules.
  • Is there a record of every message? Yes. Every message, confirmation and change on each shipment is recorded in a change history.
  • How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, and that one fee covers create, quote, tender, track, audit and pay. Pricing scales down as volume grows, and Enterprise pricing is custom.

Conclusion

Freight communication software earns its place when requests end closed: the quote received, the pickup confirmed, the ETA updated, the POD filed. Counting messages sent rewards activity, and the missed pickup in the shared inbox still lands on a coordinator. Score every vendor on a week of your own requests, under the same rules, and compare the close rate with how those lanes ran before.

Wilson, by Cartage, works across email, phone, SMS, Slack and Microsoft Teams and keeps following up until the work is done or a person is needed. Bring last week's open carrier requests and watch Wilson close them, from first message to updated shipment, in a demo at cartage.ai.

Sources