How to cover a load faster: the broker inbox triage playbook.

9:47 AM. You posted Newark NJ → Miami FL at $3,200 forty-three minutes ago. Your inbox has 38 replies and is still climbing. Three of them are quoting at rate. Two are quoting under. One says “is this still available?” and nothing else. One is a PDF you cannot read on your phone. Four are from dispatchers you have never heard of. The shipper wants a confirmation by noon.

This is the inbound-reply tax — somewhere around 40 carrier replies per posted load, ~58 minutes of broker time to cover the average load, most of it spent reading. The good news is most of that reading is the same reading, every time. Once you have a triage playbook, the math gets a lot better.

The 10-second pass: kill the noise

The first sweep is fast and brutal. You are not reading; you are deleting. Targets:

• Single-line replies that say nothing (“is this still available?”, “send me the rate con”, “what is your best rate?”) with no quote, no equipment, no availability. Either ignore or auto-reply with the load details and re-post.
• Wrong equipment. You posted a reefer; a flatbed broker replying back is not going to magically be the right truck.
• Wrong geography. Lane mismatches, empty-on-the-wrong-day.
• Duplicate threads from the same dispatcher on the same MC — collapse to the most recent.

You should be down to ten or twelve serious replies in the time it takes to drink half a cup of coffee. Anything that survives the 10-second pass goes into the 2-minute pass.

The 2-minute pass: rank the top five

Now you read. Two minutes — actually two minutes, set a timer if you have to — to pull the offer out of each surviving reply and rank them. What you are scanning for:

• The number. What rate, all-in or plus fuel? Quoted explicitly or buried in a paragraph?
• Equipment match. 53ft van vs reefer vs flatbed. Reefer temp range stated when relevant.
• Pickup window feasibility. “Empty in Memphis 4pm” on a Dallas pickup tomorrow morning is a real claim; “empty in Anchorage” for a Newark pickup is not.
• Carrier identity sanity. MC matches signature. Domain matches the carrier name. Not a brand-new MC pretending to be an established carrier.
• Has-run-this-lane signal. “We've moved this lane before” is a real cue when it comes from a carrier whose previous bookings back it up.

Rank the survivors top to bottom. The top three are your candidates. Top one is your first call.

The 10-minute pass: deep-read the one you book

Before sending a rate con, ten minutes on the carrier you actually intend to book. This is where the small percentage of fraud lives, and ten minutes here is cheaper than three days of cleanup later. You are reading:

• FMCSA SAFER snapshot. Authority active. Insurance on file. Out-of-service rate not spiking. Address not a UPS Store.
• Insurance certificate against the MC record. Entity names match (or the carrier explains the DBA in one sentence). Coverage limits adequate for the cargo.
• Email domain against the FMCSA-registered contact. Established carriers send from their own domain. Gmail or Outlook from a name that has been hauling for ten years is a stop sign — see the double brokering field guide.
• Historical relationship. Have you worked this MC before? Were they on time? Did they invoice clean?

By the time you have read all four, you have either a clean booking decision or a clear “move to the next candidate” decision. The thing you are not allowed to do is skip this pass to save five minutes.

Call vs reply: the simple rule

Reply by email when the quote is clear, the equipment is stated, and the rate is in your acceptable band. Call when:

• The quote is ambiguous — equipment unspecified, all-in unclear, pickup window vague.
• The rate is good but the carrier identity has any soft flag (new MC, mismatched domain, unfamiliar dispatcher).
• You have a counter to negotiate. Counter-offer rounds get stuck in email; one phone call closes it.
• The load is tight on pickup time. You need to hear the dispatcher commit out loud.

The whole point of replying-then-calling-when-needed (rather than calling-everyone) is to keep the inbox doing the work that inbox is good at and the phone doing the work the phone is good at. Mixing the two is what kills broker hours.

Gmail filters / labels that actually help

A few filters that pay back the ten minutes it takes to set them up:

• Auto-label by posted-load reference. If you post loads with a reference in the subject (LD-49827), filter replies into a label per active load. Now you can see all 40 replies on one load in one place.
• Auto-archive single-line “is this still available?” replies with a canned auto-reply that sends the rate con / details and tells them to quote back. You stop reading them; the dispatcher gets the info anyway.
• Star anything from a known-good MC. A label per repeat-carrier MC pulls familiar names to the top of every load's thread.
• Auto-flag suspicious domains. A filter that highlights gmail.com / outlook.com replies on loads where you usually see corporate domains. Not a delete — a yellow flag.

Gmail is not a great triage tool, but it is the tool every brokerage has, and a few filters make it materially less painful. For a fuller treatment of why brokers live in their inbox in the first place, see why brokers live in their inbox.

When to stop doing this by hand

The playbook above is enough for a one-load-per-broker-per-hour day. It breaks down somewhere around 12–15 active loads per broker. At that volume the 10-second pass alone is consuming two hours a day and the 2-minute pass is consuming four. That is the point where an inbox-triage layer starts paying back the seat price in the first month — rate extraction, automatic carrier ranking, FMCSA scoring on every reply, and a top-five list ready before you open the thread.

If you would rather not run this playbook by hand on every load, Keelway runs the 10-second and 2-minute passes for you and hands you the top five with trust scores attached — see our brokers solution page and carrier email automation for the full spec.