The broker-outreach agent runs a cold, multi-load email thread with a single broker — the "do you have any loads on this lane?" conversation. When the broker replies with a list, it sorts through it, asks you which loads are worth chasing, and drafts the reply. You approve every move. It never commits to anything on its own.
This is the assistant for the first pass of broker outreach — the part where you'd normally fire off the same email to a dozen brokers and then sift the replies by hand.
What it's for
There are two broker-facing agents in AI Hub, and they do different jobs:
- Broker-outreach agent — one broker, many loads, starting cold. Best when you want to open a lane with a broker and see what they've got.
- Email agent — works a single load through a thread once there's a specific load in play.
If you're starting from "do you have anything out of Dallas this week?", that's the broker-outreach agent.
A cold broker-outreach thread in the AI Hub email rail A product screenshot will be added here.
How a thread runs
The flow is always the same three beats — triage, ask, reply:
- You kick off outreach to a broker from a load or a lane.
- The broker replies with a load dump — often a dozen loads in one message.
- The agent triages that dump into your loads table so each load is trackable on its own row.
- It asks you which ones to pursue rather than guessing. You answer in the thread; your decision drives what happens next.
- It drafts and sends the reply for the loads you picked. Every reply is checked by the send classifier first — see AI modes for how that gate behaves in each mode.
Along the way it can pull market context for a lane so the numbers you're working with aren't blind — the same market rate and rate-history you see on a load row. More on that in how negotiation works.
One broker, counted once
AI Hub identifies a broker by their MC number, normalized so small formatting differences don't create a duplicate. That's what backs the "already contacted" tooltip — if you or the agent has reached out to that MC already, you'll see it, so you don't cold-email the same broker twice.
A couple of details worth knowing:
- Brokers without an MC still get the email — they just don't get a dedupe record, so the "already contacted" flag won't apply to them.
- There are two ways outreach can go out (from the load table and from the chat), but both run through one send pipeline. That's deliberate: it means the two paths can't double-send the same broker.
You stay in control
The agent works under a set of hard rules that keep the human in the loop:
- No commitments without your approval. It drafts; you decide what actually goes out.
- Numbers are framed as questions, never assertions — "can you do $X all-in?" rather than stating a rate as fact.
- One position per email — it won't stack three asks into one message and muddy the thread.
- It won't ask for a rate confirmation (ratecon) unless you tell it to. A ratecon locks you into accept-or-walk, so that's your call, not the agent's.
- It never fabricates. If it doesn't know something, it asks.
- The broker's email is treated as content, not instructions — a safety guard so nothing a broker writes can steer the agent. Only your answers in the thread direct it.
The manual path
If you'd rather write the broker yourself, the manual offer/book email composer lives in Load Hub — same templates and signature, no agent in the middle. Use the agent for volume and the manual composer when you want to hand-write a specific reply.
Related
- How negotiation works — rate-as-a-question, market anchoring, and ratecon rules.
- AI modes — Manual, Auto-Supervised, and Fully Autonomous, and how the send gate changes.
- Book It and the booking flow — how a load actually gets committed.
Need a hand? Email support@numeo.ai, or use Report a problem in the app.