Every carrier quote, read and structured — before the coordinator's eyes touch it.

Carrier rate extraction is the automated process of reading an inbound carrier email and pulling structured data — offered rate, equipment type, lane (origin and destination), estimated pickup and delivery, and any detention or layover assumptions — into a database row without a coordinator reading or retyping the email. Keelway does this on every reply to every posted load using a multi-step LLM pipeline.

Keelway's parser handles all 12 carrier email formats we've documented in the field: the dispatcher rate email, the owner-op text-to-email forward, the TMS-generated PDF attachment quote, the copy-paste load board reply, the rate-confirmation-as-inquiry, the template form submission, the negotiation counter embedded in a reply thread, the multi-load rate table, the broken English abbreviated rate (common in owner-op), the auto-reply with rate in the subject line, the load board API notification parsed as email, and the plain-text SMS-to-email. See our post on why carrier quote emails arrive in twelve formats for the full taxonomy.

Keelway runs a two-model pipeline. The primary extraction model (Sonnet 4.6) attempts the parse. When confidence falls below a tunable threshold — typically on ambiguous formats like multi-load rate tables or deeply embedded reply threads — the extraction job escalates to an Opus 4.7 fallback pass. If both models return low-confidence extractions, the email is flagged for a coordinator review with the best-guess extraction pre-populated. Coordinators correct roughly 2–4% of extractions; each correction trains the brokerage-specific calibration.

Yes. Rate confirmation PDFs, scanned rate sheets, and formal quote documents sent as attachments are extracted using a document-parsing layer before the LLM pass. Keelway handles standard PDF, image-based PDFs (with OCR), and common trucking TMS rate-con templates from McLeod, Aljex, and Revenova.

The standard extraction schema includes: offered_rate (dollar amount, and whether all-in, linehaul only, or a range), equipment_type, origin_city, origin_state, destination_city, destination_state, available_date, estimated_transit_days, detention_rate (if quoted), layover_assumption, fuel_surcharge_note, and carrier_contact_name. Optional fields extracted when present: team_driver flag, HAZMAT certification mention, reefer temperature range, and partial-load percentage.

Both are stored. When a carrier quotes a range (e.g., $2,200–$2,400 depending on fuel), Keelway stores the floor, ceiling, and midpoint and uses the midpoint for ranking unless your brokerage preferences are set to use floor or ceiling. Range quotes are displayed with a range badge in the ranked list so coordinators know to expect negotiation.

Yes. Once a coordinator accepts a carrier from the ranked list, Keelway writes the accepted carrier, rate, and lane confirmation back to your TMS — Tai, McLeod, Aljex, Revenova, Turvo, or Rose Rocket. No double entry. The raw extraction record persists in Keelway's load_inquiries table regardless, so you have a full audit log of every carrier who replied and what they quoted.

Yes. Keelway's lane history view aggregates extracted rates by origin-destination-equipment corridor, showing you the distribution of carrier quotes over any trailing period. This is the data layer that powers Keelway's rate percentile feature — every new inbound quote is positioned against the trailing distribution on that corridor, so coordinators know whether a $2,300 quote on a Chicago–Atlanta 53' dry van lane is at market, below, or above.

Carriers who reply without quoting a rate — 'Interested, what's the pay?' type emails — are parsed as availability signals, not rate quotes. They appear in a separate availability queue, not the ranked list. Keelway drafts a templated 'What's your best rate on this lane?' reply that the coordinator can send in one click.