Build the pickup request payload: origin facility address, contact name and phone, pickup ready time and close time as ISO 8601 local timestamps, total freight weight, pallet count, and freight class; include the PRO number or BOL number generated at rating time
Submit the pickup request via the carrier's pickup scheduling API or via project44 Capacity API if using managed carrier connectivity; receive a pickup confirmation number and the carrier's assigned pickup window
Subscribe to pickup status webhook events or poll the pickup status endpoint using the pickup confirmation number; monitor for CONFIRMED, DRIVER_ASSIGNED, EN_ROUTE, and PICKED_UP status transitions
On DRIVER_ASSIGNED, retrieve the driver name and estimated arrival time from the event payload; send a facility notification to dock staff with the expected arrival window and driver information
If PICKED_UP status is not received within 30 minutes of the pickup close time, trigger a carrier check-call workflow: call the carrier's dispatch center with the confirmation number and document the outcome
On PICKED_UP confirmation, capture the actual pickup timestamp and piece count from the event; compare against the scheduled pickup window and booked piece count; flag discrepancies for exception management
Known gotchas
Carrier pickup APIs for LTL have a minimum lead time (commonly 2 hours before pickup close) and a daily cutoff (often 3:00 PM local time for same-day pickup); submitting a pickup request after the cutoff returns a rejection without suggesting the next available pickup date
Some LTL carriers assign pickup windows in 3-4 hour blocks rather than specific times; displaying the pickup window to dock staff as a precise time causes confusion and unnecessary wait; always display the full window range
Pickup confirmation numbers and PRO numbers are separate identifiers in most LTL carrier systems; referencing the pickup confirmation number in a tracking query will return no results because tracking is indexed by PRO number
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp