A shipper emails quotes@ at 4:40 on a Thursday. The subject line says "rate?" The body says "2 pallets Allentown to Atlanta, need it Monday." A PDF is attached, along with a phone photo of a packing list. The phone number in the signature has a typo.
Someone has to turn that into a quote request. Usually it is whichever broker opens the inbox first, and the next broker who opens it does the same reading all over again.
A shared quotes inbox is where brokerages lose freight without noticing. No voicemail light blinks. The message just ages, and the shipper emails the next broker on their list.
Decide what the inbox is for
One inbox, one owner per shift, and a status on every thread. "Unread" is not a status. Use something your team will actually set: new, needs details, ready for broker, quoted, closed. If a thread has no status, nobody owns it.
Settle evenings and weekends too. Who looks at quotes@ at 7 p.m.? If the answer is "whoever sees it," the answer is nobody.
Pull the same fields from every email
Messy emails are normal, so write down what a broker needs before pricing anything. A workable list:
- Shipper company, sender name, reply address, and a phone number - Pickup city, state, and zip - Delivery city, state, and zip - Pickup date or window, and any delivery deadline - Equipment the shipper asked for, in their words - Commodity as the shipper wrote it - Weight, piece count, and dimensions - Special handling such as liftgate, appointments, or temperature - Where each value came from: the body, an attachment, or a signature
That last line matters more than it looks. When a broker sees "42,000 lbs" they should know whether the shipper typed it or a packing list said it.
Plan for the usual mess. A forwarded chain where the real details sit in the third message down. A spreadsheet with thirty rows and one lane per row. "Same as last time." "Next Friday," sent on a Wednesday. A city name like Portland or Springfield with no state. Convert relative dates to calendar dates and show them back to the shipper. Never guess a state.
Flag conflicts and gaps, do not resolve them
Sort every field into one of three buckets: stated, conflicting, or missing. Do not add a fourth bucket called "probably."
If the body says 8,000 lbs and the attached packing list totals 11,300, do not pick one. Record both and send the question to the shipper. If the email says "pallets" and nothing about equipment, leave equipment blank. A reasonable guess about a dry van is still a guess, and it will end up in a quote.
Weight, delivery zip, and pickup date are the usual holes. Tally them for a few weeks to see which question to ask first.
Acknowledge fast, and ask only for what is missing
Shippers send the same request to several brokers. The first reply that shows someone read the email gets a seat in the conversation. A reply that asks for what the shipper already wrote gets ignored.
Here is a hypothetical acknowledgment for the request above:
> Thanks, got your request for 2 pallets from Allentown, PA to Atlanta, GA, with pickup Monday, [date]. To get this to a broker with what they need, can you send: 1) the total weight, 2) the delivery zip code, and 3) whether the receiver needs a liftgate or appointment. A broker will follow up with pricing. Reply here or call [direct number].
Rules for that message:
- Restate what you understood in one line so the shipper can correct it. - Ask only for missing or conflicting items, and name each one. - Name a human or a desk and a direct number. - Say what happens next, but do not promise a time for the rate unless a person has committed to it. - Never include a rate, a carrier name, or "we can cover that."
Rates stay with a broker
Pricing depends on market conditions, carrier availability, your margin, and your history with that shipper. Those are judgment calls, and the broker answers for them. Whatever helps with intake should hand over a complete, labeled file and stop there.
There is also a records reason to keep the thread attached to the load. Under 49 CFR 371.3, a broker must keep a record of each brokered transaction for three years. The record covers items like the consignor's name and address, the bill of lading number, and compensation. The rule also says each party to the transaction has the right to review that record. It does not list email threads, but when someone asks how a rate was set, you will want the original request and your reply in the same place as the load. Ask your own counsel what applies to your operation.
Treat odd senders as a different queue
The FBI's Internet Crime Complaint Center has warned that business email scams often use spoofed addresses, and it recommends verifying the sender's address and confirming requests through a second channel ([IC3, September 2019](https://www.ic3.gov/PSA/2019/PSA190910)). A quote inbox is an open door by design, so write rules for the strange ones:
- A first-time sender domain asking for fast pickup goes to a person before any detailed reply. - A reply-to address that differs from the from address goes to a person. - Any request to change pickup, delivery, or payment details on an existing load gets confirmed by phone at a number already on file. - The acknowledgment for an unknown sender stays generic and gives away nothing about carriers or rates.
Test with last month's mess
Pull thirty real emails from last month, the ugly ones included. Run each through your fields and reply rules by hand, or with whatever tool you are considering. Then check:
- How many had a field wrong, and which ones? - How many conflicts between body and attachment did you catch? - How many replies asked for something already given? - How long from arrival to a first reply, for emails that landed after 5 p.m.?
Fix the rules before you turn anything on. A bad template sends the same bad question to every shipper.
If you want help setting up quote-email triage that keeps rate decisions with your brokers, [book a call with Chosen AI Solutions](https://chosenai.co/book).
Sources
- U.S. Federal Bureau of Investigation, Internet Crime Complaint Center. "Business Email Compromise: The $26 Billion Scam." September 10, 2019. [ic3.gov](https://www.ic3.gov/PSA/2019/PSA190910) - 49 CFR 371.3, Broker records. [Cornell Legal Information Institute](https://www.law.cornell.edu/cfr/text/49/371.3)