A lane nearly stops
One origin and destination falls far below its own frequency while the shipper's other lanes continue.
Freight brokerage
Brokerage volume moves too quickly for a quarterly account review. ChurnRisk compares each lane with its own tender rhythm, then puts claims, service failures, and rate objections beside the change.
Lane-level volume stays separate from market rate movement, with TMS and EDI gaps shown as confidence limits.
How the work repeats
A shipper may run several facilities, modes, and lanes through one account. Losing one lane can be hidden by stable volume elsewhere, especially when daily load counts and spot work make the total noisy.
Lane-level exit is cleaner. A route that handled 12 to 18 loads a month and suddenly runs three deserves review when the shipper's other lanes remain unchanged.
Useful changes
Load count, lane mix, margin, and service evidence stay separate.
One origin and destination falls far below its own frequency while the shipper's other lanes continue.
Volume falls across repeated tenders without a matching change in the rest of the account.
Margin per load moves down while rate objections or competitor prices appear in connected threads.
Late pickup, late delivery, damage, accessorial disputes, or credits begin to cluster on the same lane.
Warning examples
These sample lines use the freight pack's high-frequency context.
Chicago to Dallas ran 12 to 18 loads a month for a year. Three loads ran last month. The shipper's other four lanes are unchanged.
Two late-delivery complaints appeared on the same lane before its load count fell.
Margin per load compressed while rate objections increased. Tenders sent only through the TMS remain outside the record.
Illustrative warning copy. Figures and events are sample data from the industry pack.
False alarms
A lane change needs market and shipper context before action.
A shipper's production cycle can create sharp, normal swings in weekly load count.
The shipper may have lost a customer or moved production, removing the lane for every broker.
Spot volume can shift on price without reflecting service dissatisfaction.
A broker's own capacity constraint can push loads away and changes the recovery conversation completely.
ChurnRisk does not chase volume during an active claim, answer a service failure with rate copy, or use text messaging for a dispute.
Connector limits
The freight pack has a medium ceiling until TMS, load-board, and EDI data is connected.
QuickBooks can show load-related invoice lines, lane revenue, margin, payment changes, credits, and disputes when the lane reference is present. Connected mailboxes can show quote requests, rate objections, claims, and traffic-contact changes.
ChurnRisk does not connect to transport management systems, load boards, EDI tendering, or carrier portals today. Daily tender volume can be missing even when the accounting connection is current.
Missing TMS data caps confidence at 70%. Load boards and electronic tenders cap it at 72%, and carrier portals at 80%. Those ceilings remain even when the lane pattern in QuickBooks looks sharp.
Read the current connection boundaries for QuickBooks and Gmail or Outlook. The How It Works page explains how missing data becomes an unknown instead of a healthy reading.
Monday workflow
Service recovery and rate review are different jobs.
Compare load count, mode, margin, and normal tender gap for the same origin and destination.
Confirm seasonality, production changes, discontinued lanes, and whether the other routes remain active.
Bring late pickup, delivery, damage, and accessorial disputes into the review before discussing price.
Choose service recovery, a lane-loss inquiry, or a quarterly volume call. Claims block volume chasing.
See the full product workflow, including evidence, confidence, and approval before any customer contact.
Related industries
For transaction volume where outside demand can look like a lost relationship.
For repeat orders where a product family can move away before the account total falls.
Compare plans on Pricing, or use the demo to test one account with labeled sample data.
Start with your lane and load history, or bring one shipper with a noisy volume change to a walkthrough.
TMS, load boards, EDI tenders, and carrier portals are not connected. Missing TMS data caps confidence at 70%.