Skip to content
New: a sample workflow audit report
Scenox Studios

Draft freight quotes from customer rate requests

Rate requests arrive by email in many formats. The system reads the lane, equipment and dates, pulls contract rates and recent market data you already hold, and drafts a quote for a rep to adjust and send. For brokers where reps quote from memory and spreadsheets.

Draft freight quotes from customer rate requests

6 steps

  1. 01

    Read the request

    Model
  2. 02

    Validate the lane

    Rules
  3. 03

    Pull the pricing inputs

    Rules
  4. 04

    Apply margin rules

    Rules
  5. 05

    Set the price

    Person
  6. 06

    Draft the response

    Model

At a glance

Trigger
A customer rate request arrives by email or portal.
Typical inputs
  • Rate request emails and spreadsheets
  • Customer contract rates and margin rules
  • Recent loads and carrier rates on the lane
  • Fuel schedule and accessorial tables
Systems it usually connects to
  • Outlook
  • McLeod
  • Salesforce
  • Google Sheets
How the work splits

3 rules, 2 model, 1 person steps

How it runs, step by step

6 steps, each tagged by what does the work. Rules are fixed logic, a model reads or drafts, and a person decides.

  • Rules Fixed logic in code
  • Model AI reads or drafts, with a confidence score
  • Person A named person decides
  1. 1

    Read the request

    Model

    A model extracts origin, destination, equipment, weight, dates and any special requirements from the message or spreadsheet.

  2. 2

    Validate the lane

    Rules

    Locations are standardized and checked, and requests with missing details are queued for a question back to the customer.

  3. 3

    Pull the pricing inputs

    Rules

    Contract rate, recent buy rates on the lane, fuel and accessorial tables are collected from your own systems.

  4. 4

    Apply margin rules

    Rules

    A suggested sell rate is computed from your margin rules, with the basis shown to the rep.

  5. 5

    Set the price

    Person

    The rep decides the final rate, based on market feel and the customer relationship.

  6. 6

    Draft the response

    Model

    A model writes the quote email, and the rep sends it. Won and lost outcomes are recorded against the quote.

Where people approve

The decisions that stay with your team, whatever the confidence score says.

  • The rep sets and sends every quote.
  • Quotes outside the margin floor need manager approval.
  • Spot quotes for new customers follow your credit rules.

KPIs to track

What to measure, before and after. Targets come from your own baseline.

  1. 01Minutes from request to quote
  2. 02Quote win rate by lane and customer
  3. 03Quotes below the margin floor
  4. 04Requests lost to slow response

Questions about this workflow

Does the model set the price?

No. Pricing is rules and the rep's judgment, and the model is used only to read the request and write the email. We prefer it that way because pricing errors cost money directly.

What market data does it use?

Only data you already have the right to use, such as your own recent loads and carrier quotes, and any rate source you subscribe to. We do not scrape sites that forbid it.

Which steps use rules, a model and a person?

Rules: validate the lane; pull the pricing inputs; apply margin rules. Model: read the request; draft the response. Person: set the price. Rules are fixed logic in code. A model reads or drafts and reports its confidence. A named person decides.

What do we need to start?

Typically: rate request emails and spreadsheets; customer contract rates and margin rules; recent loads and carrier rates on the lane; fuel schedule and accessorial tables. You also need read access to Outlook, McLeod, Salesforce and Google Sheets, or the equivalents you use. A workflow audit measures your volumes and past cases first, then gives a fixed price for the build, so you can decide with real numbers.

Where this fits at Scenox

More use cases like this one

All 60 use cases

Plan how to draft freight quotes from customer rate requests with an engineer.

A 30-minute call with an engineer. You will leave knowing what a system could do for that workflow and what it would take to build.

What happens next

  1. 1

    Strategy call

    We learn how the workflow runs today and what a good outcome would be.

  2. 2

    Workflow audit

    We map the process and measure where a system would save the most time.

  3. 3

    Proposal

    A written scope, timeline and fixed price for your first system. No obligation to build.