Triage the RFQ inbox and convert it to a quote
Work an incoming request in the RFQ Inbox and turn it into a linked quote record — no typed-in ids.
Every request — from the quote widget, inbound email, or manual entry — lands in one place: the RFQ Inbox. This page covers working a request there and converting it into a quote, with the RFQ and quote records linked to each other the whole way through.
1. Open the RFQ Inbox
Go to /os → RFQ Inbox. The inbox lists every request for your tenant, newest
first, with a source facet (email, web lead, API, broker) and a status filter
(new / quoted / declined / expired).
The inbox has two ways to work it, over the same underlying queue:
- LIST — a table plus a detail drawer per row.
- TRIAGE — a split-pane, keyboard-driven view (
J/Kto move,Dto decline,Eto expire,Enterto convert) for working through a queue quickly.
2. Open a request
Click a row (LIST mode) or land on it in TRIAGE mode to open its detail. You'll see the parsed trip fields (origin, destination, date, pax), the raw message it came from, the linked CRM customer if one resolved, and — if the inbox flagged it as a likely repeat of another open request — a duplicate indicator you can review from the DUPLICATES panel toggle in the toolbar.
If a required field is missing or looks wrong, correct it here — origin, destination, date, and pax must all be filled in before you can convert.
3. Convert to a quote
Click CONVERT TO QUOTE.
- This runs your operator quote pipeline against the request's parsed trip fields — the same pricing engine Build and price a quote uses.
- On success, the RFQ record links to the new quote (
quote_id) and its status flips toquoted— you're taken straight into that quote in the Quotes workspace, never asked to type an id to find it. - If the request has no linked CRM customer yet, convert still works — but the inbox warns you the resulting quote won't be sendable until a customer email is attached, and offers a one-click promote-to-CRM-lead action.
Converting only runs pricing and the compliance checks every quote gets —
it never marks a trip "compliant." Each priced tail carries its own
compliance status (a pass, PENDING_VERIFICATION, or a hard-blocked
suppressed tail with its gate reason attached) on the quote itself. See
Read compliance verdicts.
4. Or hand it to a rep to build by hand
Instead of one-click convert, you can send the request's trip fields straight into the Quotes build pane, pre-filled, so a rep builds the quote manually (picking a specific tail, adjusting the itinerary, and so on). That build still records the link back to the originating RFQ and flips its status once the quote is created — it's the same record chain, just a manual build in the middle.
From here, building and pricing the quote itself — single-leg or multi-leg, and how a negotiated rate card affects the price — is covered in Build and price a quote.