Key Takeaways

• Wilson, by Cartage, executes configured freight coordination tasks instead of only displaying shipment status.

• Wilson moves loads through quoting, booking, scheduling, in-transit monitoring, delivery, and POD filing. Invoice audit and payment remain in closed beta.

• Approval rules can permit routine actions or require review when a load exceeds defined cost, lane, or exception thresholds.

• Wilson supports LTL, FTL, ocean, drayage, parcel, and cross-border freight.

• Wilson accepts orders through ERP feeds, spreadsheets, email, or scheduled file drops and coordinates stakeholders through phone, email, Microsoft Teams, Slack, and SMS.

What an AI logistics agent is, and how it differs from a TMS or tracking dashboard

An AI logistics agent is software that reads shipment information, executes configured freight coordination tasks, and escalates decisions that require human judgment.

A tracking dashboard shows shipment status and may alert staff to a delay. An execution agent uses that information to complete the next approved action. For example, the agent can contact the carrier for an update, notify affected stakeholders, or initiate rebooking from an approved carrier list.

A transportation management system supports functions such as transportation planning and settlement. It may also maintain carrier, shipment, and network records. An AI logistics agent focuses on day-to-day execution, including quoting, booking, scheduling, carrier follow-up, and document collection. The two categories can serve different operational needs.

Wilson, by Cartage, works with or without a traditional TMS. Wilson does not integrate with TMS systems. A manufacturer that already uses a TMS can operate Wilson alongside it through separate workflows and records. A manufacturer without a TMS can use Wilson without implementing one first.

Wilson maintains searchable shipment records and acts through supported systems and communication channels. Configured approval rules determine whether Wilson completes a routine action or requests review. Logistics professionals still set carrier policies, define thresholds, and handle strategic or unusual exceptions.

The seven stages of a freight load and where Wilson acts

A freight load moves through seven operational stages. Wilson carries order information through quote, book, schedule, in-transit, deliver, audit, and pay workflows while keeping shipment records and stakeholder updates tied to the load.

Across the generally available stages, Wilson requests quotes, applies configured carrier and approval rules, books and schedules the load, monitors progress, handles configured exception steps, and follows up for proof of delivery. Approval rules can permit routine actions or route threshold breaches and non-routine exceptions to logistics professionals.

Audit and pay complete the lifecycle model, but Wilson’s invoice audit, wallet, and payment capabilities remain in closed beta or are coming soon. Buyers should not treat them as generally available. The workflow table below maps each stage to Wilson’s actions, approval patterns, and retained human decisions.

Workflow table: order intake through POD

Wilson, by Cartage, executes configured freight coordination steps while the logistics team retains strategic and exception-based decisions.

Invoice audit and payment follow delivery in the broader lifecycle, but both remain in closed beta.

Order intake: supported inputs and freight modes

Wilson can ingest orders through an ERP feed, spreadsheet, email, or scheduled file drop. Each order becomes a searchable shipment record that supports the later quoting, booking, scheduling, tracking, and documentation steps.

Supported ERP sources include NetSuite, SAP, Oracle, Dynamics 365, Odoo, Sage, Acumatica, QuickBooks, Infor, Epicor, and Zoho. Support for an ERP as an order source does not mean every named platform has a full bidirectional adapter. Wilson writes information back through an API only where Cartage has built the relevant adapter, or through EDI where a carrier supports it.

A manufacturer or distributor can start with a daily order feed instead of completing an integration project first. Cartage can deepen the connection over time when the operating workflow and available adapters support additional data exchange.

Wilson coordinates LTL, FTL, ocean, drayage, parcel, and cross-border freight. The order source does not determine the mode. Wilson uses the shipment record and the company’s configured operating rules to route the load into the appropriate quoting and coordination workflow.

Quoting and approved-carrier selection

Wilson requests quotes, follows up with carriers, compares responses, and applies the shipper’s configured selection rules. Those rules can account for approved vendors, price limits, lane preferences, and required approvals. Routine loads may proceed without case-by-case approval, while quotes above a cost threshold or outside normal lane rules can go to the logistics team.

Wilson tenders the customer’s own vendors first. If those vendors cannot cover the load, the live Cartage Vendor Network provides an additional pool of bookable carriers and brokers. Customers can use network vendors without opening separate accounts or submitting credit applications. Wilson shows the selected carrier and price, while vendors introduced by the customer remain the customer’s direct relationships.

Quote comparison and carrier selection do not imply rate negotiation. Wilson’s standard workflow gathers available rates and chooses among approved options according to configured rules. Active back-and-forth negotiation with carriers or brokers is not a standard shipped capability and remains a product-readiness item. A customer should confirm whether a specific configured workflow supports negotiation before relying on it.

Logistics professionals still set the approved carrier list, selection criteria, spending thresholds, and escalation rules. Wilson does not independently discover, vet, onboard, or select an unapproved carrier.

Booking and documentation

Wilson executes the booking once carrier selection and approval rules identify an acceptable option. It sends the tender to the carrier and records the response. Wilson confirms the booking with the carrier through email or API, while the customer’s team can receive the booked update through Slack or Microsoft Teams.

Wilson produces the standard documents needed to release and move the load. The supported document set includes rate confirmations, bills of lading, packing slips, and pallet labels. Wilson stores these documents with its searchable shipment records, which keeps the booking details and change history connected to the load.

Each company determines when Wilson can book without case-by-case approval. For example, Wilson may execute routine bookings within an approved lane and cost threshold. A higher-cost quote, an unfamiliar lane, or another configured exception can trigger an approval request. Logistics professionals retain decisions involving carrier strategy, unusual service requirements, and exceptions outside the configured rules.

Scheduling and stakeholder communication

Wilson schedules pickup and delivery windows through carrier communication and the customer’s operating preferences. Approval rules can allow routine appointments to proceed automatically, while unusual timing, capacity, or consignee constraints can require logistics staff to review the plan.

Wilson asks the carrier for shipment status and distributes updates according to the configured communication matrix.

Carrier API integrations can provide near-real-time status updates when available. Email-based status depends on when the carrier sends or answers a message, so those updates may not arrive immediately. Wilson uses the received status to notify the customer team, shipper, and consignee according to their configured channels and preferences.

Ongoing monitoring and exception handling in transit

Wilson uses in-transit status to execute a configured exception workflow rather than stopping at an alert. Wilson monitors shipments through carrier API connections where available and through carrier email communication. API connections can supply status events directly, while email-based monitoring depends on carrier responses and Wilson’s follow-up.

When Wilson detects a missed pickup, cancellation, or delay, it contacts the carrier to confirm the shipment status and request an updated plan. Wilson then notifies the internal logistics team through Slack or Microsoft Teams. It can also update the customer through email or SMS when the workflow includes customer notifications.

When a disruption requires another carrier, Wilson initiates rebooking from the company’s approved carrier list. Approval rules can let Wilson proceed automatically for routine cases or require a logistics professional to approve the proposed carrier and cost. For example, Wilson could tender an approved backup carrier when a regular carrier cancels on a standard lane, provided the quote stays within the configured threshold.

Wilson does not discover new carriers, onboard vendors, or select an unapproved carrier. Logistics professionals control the approved carrier list and set cost thresholds, lane preferences, and escalation rules. They also decide how to handle exceptions outside those boundaries, such as accepting a major service tradeoff or changing the broader carrier strategy.

Delivery and proof-of-delivery filing

Delivery confirmation and proof of delivery are separate events. Wilson asks the carrier for delivery status, records the confirmation, and follows up for the POD document. Persistent follow-up helps prevent delivered loads from remaining open because the carrier has not supplied the paperwork.

After Wilson receives the POD, it files the document with the shipment record and records the filing event. Wilson can also write the confirmation and document back to an ERP when Cartage has built the relevant adapter. A named ERP source does not guarantee a bidirectional connection.

Configured notifications keep stakeholders informed. Wilson can notify the customer team through Slack or Microsoft Teams when the load is delivered and when the POD is filed. The shipper receives email updates, while the consignee can receive email or SMS updates. Logistics professionals handle disputed deliveries, damaged freight, incomplete documents, and other exceptions that require judgment.

Invoice or rate audit follows POD filing in the broader load lifecycle. Wilson’s invoice audit capability remains in closed beta and should not be treated as generally available.

Where autonomy is configurable versus where judgment stays human

Wilson applies autonomy workflow by workflow, using rules and thresholds set by the logistics team. A routine load on an established lane can move through quoting and booking without approval when the carrier is approved and the price falls below a set limit. A higher-cost quote, unfamiliar lane, or service exception can pause while Wilson requests approval through a configured channel.

Companies can begin with assisted execution and permit more autonomous execution after Wilson proves reliable within a defined workflow. Approval rules can vary by action. For example, Wilson might book routine shipments automatically but require approval before initiating rebooking after a cancellation. Rebooking always uses the organization’s approved carrier list.

Logistics professionals retain decisions that depend on commercial context or broader operating priorities. The team determines carrier capacity strategy, negotiates contracts and long-term rates, and handles non-routine escalations that threaten production or customer commitments. Wilson can gather quotes, contact carriers, update stakeholders, and prepare an approved next step, while the logistics team makes the judgment-heavy decision.

FAQs

Does Wilson integrate with a TMS?

No. Wilson does not currently integrate with TMS systems. It maintains searchable, exportable records and can coordinate freight without requiring a TMS.

What freight modes does Wilson support?

Wilson supports LTL, FTL, ocean, drayage, parcel, and cross-border freight.

How does Wilson handle a missed pickup or delay?

Wilson contacts the carrier, alerts the internal team, and notifies the customer when configured. It can then initiate rebooking from the approved carrier list. Workflow rules determine whether rebooking proceeds automatically or requires approval.

What documents does Wilson produce?

Wilson produces rate confirmations, bills of lading, packing slips, and pallet labels. It also follows up on proof of delivery and files the POD with the shipment record.

Is the Wilson wallet available now?

No. The Wilson wallet remains in closed beta and is not generally available. Freight invoice and rate-audit capabilities also remain in closed beta or are coming soon.

Getting started with an AI logistics agent

Wilson fits manufacturers and distributors whose in-house logistics staff spend substantial time on manual carrier follow-ups, booking, shipment monitoring, status updates, and exception response. Company size, shipment volume, and location count do not determine fit.

During discovery, Cartage helps identify and map a high-impact coordination workflow within the company’s current operations. A practical starting point is a one-month pilot on a few lanes, measured against the existing process. Cartage then onboards Wilson on the company’s operating preferences and approval rules before expanding its responsibilities.