Skip to content
nofeb

Solutions / Logistics and freight

Quote threads for freight agents

For freight brokers and logistics software

A freight desk sends the same lane to a dozen carriers, then negotiates each reply in its own thread. The work is the state of every thread, and a person steps in when the numbers look wrong.

The problem

Quote requests fan out to many carriers, replies come back in any order and format, and each negotiation has to stay in its thread with its current offer, deadline and owner visible.

How it runs on nofeb

  1. Give each desk, lane or customer its own inbox; there is no per-inbox price on paid plans.
  2. Send quote requests and reply in-thread; the threading headers are set for you.
  3. Keep lane, offered rate, deadline and owner on each thread as typed metadata, so any agent picking the thread up knows where it stands.
  4. Set follow_up_at on each quote thread; if it passes with no reply, a thread.due event wakes the agent to chase the carrier.
  5. Ask across every desk at once: all threads with stage = quote whose last message was outbound more than four hours ago, or every lane where the offered rate is above your ceiling. Ranges, decision probabilities and the age of the last message are all query terms.
  6. Search earlier quotes for the same lane across every inbox, and let extraction pull the dates, amounts, phone numbers and email addresses out of free-text replies into metadata.
  7. When a rate needs a human negotiator, the broker opens the thread in the webmail, takes it over, and the agent's sends on that thread stop until it is handed back. The metadata panel shows the lane, offer and deadline beside the mail.

Where nofeb stops

  • nofeb is not a TMS. It carries the conversations and their state; rates, loads and invoices stay in the systems you already use.

Status of everything this relies on

CapabilityWhat it doesStatus
Unlimited inboxes Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. Shipped
Send, reply, reply-all and forward Threading headers are set for you, replies default to the original sender, and forwards carry the original attachments. Shipped
Typed metadata on messages, threads and inboxes Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. Shipped
LLM-ready thread context A whole thread, oldest first, with safe_body text and the thread's metadata, in one call. Shipped
Signed webhooks with required scope Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. Shipped
Durable event feed A pull feed of every event, oldest first after a cursor, for consumers that cannot receive webhooks. Shipped
Follow-up timers Set follow_up_at on a thread and, when that time passes, a thread.due event carrying the thread's metadata goes to your webhooks and the event feed, so agents need no scheduler of their own. Shipped
Queries across threads by metadata Find threads across inboxes and pods by typed metadata values and ranges, by decision probabilities, and by the direction and age of their last message (every thread at stage quote with no reply for four hours), plus an inbox directory searchable by metadata. Shipped
Search that understands Full-text and semantic search over subjects, addresses, the new text of each message, attachment names and attachment text, across every inbox a key can see. Filter by inbox, pod, folder, thread, sender, recipient, date, attachments, keywords, authentication failures and metadata; results carry highlighted snippets and can be grouped by thread. Shipped
Built-in and custom extractors Receipts and orders, invoices (account numbers masked), calendar invitations and named entities extracted into typed metadata as mail arrives, plus your own extraction schemas run on your own model key, with the output validated against the schema. Shipped
Take a thread over from the agent A person takes a thread over; until they hand it back, the agent's sends on that thread are held for approval or refused, and an event records who is driving. Works over the API, MCP, JMAP and the webmail. Shipped
Webmail for the humans in the loop A full webmail and calendar on the same mailboxes the agents use, with an agent-activity timeline, the approval queue, a per-thread driver lock and a metadata panel, signed in through the same accounts as the console. It opens with hosted access. Shipped