When AI Hub works a rate with a broker, it follows a deliberately careful style: it asks for a number instead of asserting one, keeps each email to a single ask, and never touches a rate confirmation unless you've told it to. The point isn't to hand off your negotiation — it's to do the back-and-forth typing while you keep every decision.
The approach in four rules
These are the guardrails the agent negotiates under. They're worth knowing because they shape every draft you'll approve.
- Rate as a question, not a claim. The agent writes "can you do $2,850 all-in?" — never "the rate is $2,850." A question keeps the door open and keeps you from being pinned to a number you didn't authorize.
- One position per email. It won't bundle a rate ask, a pickup change, and a question about a ratecon into one message. One clear ask per email keeps the thread readable and the broker's answer unambiguous.
- No ratecon until you say so. A rate confirmation is a hard line — once it lands, you're locked into accept-or-walk. So the agent will not ask for one unless you explicitly tell it to.
- Never fabricate. If a detail isn't known, the agent asks for it rather than inventing it. Same goes for numbers grounded in driver memory — those route through your approval before they can be said to a broker.
Market anchoring
The agent doesn't negotiate blind. It can pull market context for the lane — the current market rate, the RPM range, and recent rate history — the same figures you see on a load row. That gives its ask a reference point instead of a guess.
Market rate and rate history on a load row A product screenshot will be added here.
Anchoring cuts both ways: it keeps the agent from lowballing a hot lane and from chasing a rate the market won't bear. You can always override the number — the market read is context for your decision, not a rule the agent follows on its own.
Where your approval sits
Every reply the agent wants to send passes through a send classifier before it goes out — the gate that decides whether a draft is safe to auto-send or needs your sign-off. How strict that gate is depends on your AI mode:
- In Manual, you compose and send — nothing leaves without you.
- In Auto-Supervised and Fully Autonomous, drafts run through the classifier, and anything that makes a commitment or leans on remembered numbers comes back to you first.
No mode lets the agent commit money on its own. That's what Book It is for — your explicit go-ahead to send a booking email.
When the broker says yes
The agent watches for acceptance in the broker's reply. Phrases like "deal," "book it," "sending rate con," or "you got it" are read as a hard yes. At that point the load moves toward booking — but a booking only becomes final after the broker confirms against your Book It, not the moment the agent detects a "yes." You're never committed by the agent's reading of a message alone.
Related
- How the broker-outreach agent works — triage, ask, reply on a cold multi-load thread.
- AI modes — how the send gate changes per mode.
- Book It and the booking flow — the explicit commit step.
Need a hand? Email support@numeo.ai, or use Report a problem in the app.