Scout is the copilot inside FreightScout. It knows every load, account, margin and signal you have, so it doesn't just chat. It does the work: drafts the email, logs the call, sets the follow-up. You approve.
Every other "AI assistant" hands you a chat window and leaves the work to you. Scout reads your entire book, answers with the exact datapoint, then does the thing. It drafts the outreach, logs the call, sets the follow-up, updates the account. Clearing the flag is the logging. No copy-paste, no swivel-chair, no net-new data entry.
Scout is wired to your live data: loads, accounts, margins, lanes, comms, signals. Ask it anything and it answers with the number and where it came from. If it doesn't know, it says so. It will not invent a figure to sound smart.
Three lanes are below your 90-day margin floor: ATL→MIA at 9% (floor 13%), DAL→PHX at 11%, and CHI→ATL at 12%. ATL→MIA ran 22 loads in the last 30 days: that's the biggest bleed.
Rate case built: loads, dates, costs. Carrier win-back note drafted.
Scout doesn't stop at the answer. Tell it to draft the note, log the call, set the follow-up, update the account. It stages the action and hands it to you for a yes. On the tasks you trust, let it run unattended.
Marcus, capacity's tightening on ATL→MIA heading into Q3. I'd rather lock your rate now than let it drift up on you. Can we set a Q3 number this week? I've got dedicated coverage held for your volume.
No query language, no reports to build. Just ask, the way you'd ask your sharpest analyst.
The reason CRMs rot is data entry. Scout kills it. When you act on what Scout surfaces, whether that is sending the draft, taking the call or setting the task, the record updates itself. The work and the logging are the same motion.
Start supervised. Scout drafts and proposes, you say yes. As you learn to trust it, hand over the wheel: turn on autopilot per rep, per action. Reversible any time.