> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kordless.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Understand quote outcomes
> What each Quote outcome means, what the customer sees, and what the owner should do about it.
Every request evaluated against a published Book produces one of seven outcomes. Each outcome has a customer meaning, an owner action, and a quote state. The interface uses customer-facing labels — not code enums.
## Exact definitions
| Outcome | Customer sees | Owner action | Quote state |
| ------------------- | -------------------------------------------------------------------- | ----------------------------------- | ------------------- |
| Exact offer | The price the Book produced | Review only when policy requires | `quoted` |
| Range offer | The price range the Book produced | Review or send according to policy | `quoted` |
| Needs input | "A few details are missing" — the request is with the business | Request or provide the missing fact | `new` |
| Needs review | "Request received" — the request is with the business | Approve, correct, or decline | `awaiting_approval` |
| Inspection required | "Request received" — the request is with the business | Arrange the supported next step | `awaiting_approval` |
| Unavailable | "This one goes to the owner" — the Book declines rather than guesses | Explain or decline | `new` |
| Failed | "Request received" — the request is with the business | Retry or contact support | `new` |
## How autonomy affects what happens
The book's autonomy rung decides whether a priced outcome sends automatically or is held for the owner:
| Outcome | Shadow | Approval-first | Send ranges | Send exact | Permit commitment |
| ------------------- | -------- | -------------- | ----------- | ---------- | ----------------- |
| Exact offer | Observed | Held | Held | Sent | Sent |
| Range offer | Observed | Held | Sent | Sent | Sent |
| Needs input | Observed | Held | Held | Held | Held |
| Needs review | Observed | Held | Held | Held | Held |
| Inspection required | Observed | Held | Held | Held | Held |
| Unavailable | Observed | Held | Held | Held | Held |
| Failed | Observed | Held | Held | Held | Held |
Non-priced outcomes are never auto-sent at any rung. A request that needs input, needs review, requires inspection, is unavailable, or fails is always held for the owner. The customer sees a neutral "request received" state — never a number.
## Customer-facing states
On hosted quote paths and embeds, the customer sees one of four states:
| Customer state | What the customer is told |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Quoted | The offer is shown with its price, range, and conditions. An accept button may appear if the book permits commitment. |
| Held | "Request received" — the business reviews requests like this before sending a price. No number is shown. |
| Unavailable | "This one goes to the owner" — the Book does not price that combination, and declines rather than guesses. No number is shown. |
| Needs input | "A few details are missing" — the Book needs more information before it can price this. No number is shown. |
A price renders only when the stored quote row itself is `quoted`. A forged outcome parameter on the URL cannot expose a held or shadowed price — the quote row is the truth.
## What the owner sees
On the quote receipt, the outcome chip shows one of six states derived from the quote's lifecycle:
| Receipt outcome | What it means |
| --------------- | ------------------------------------------------------------------- |
| Pending | The request has been received but not yet priced |
| In review | The request is held for owner review |
| Priced | The Book produced an offer and it has been sent or is ready to send |
| Committed | The customer accepted and a deposit or completion was recorded |
| Declined | The owner closed the quote without an offer |
| Expired | The offer's validity lapsed before the customer decided |
## Rules and boundaries
* Unsupported work fails closed. The Book returns `unavailable` instead of producing a plausible number.
* A Test key cannot address Live. Test requests stay in Test.
* Existing offers remain pinned to the book version that produced them. Publishing a new version does not change offers already sent.
* Shadow mode records requests for comparison but never sends an offer. The customer sees nothing.
* Inspection required means the work cannot be responsibly priced remotely. The owner should arrange the supported next step rather than guessing.
## Related tasks
Inspect the inputs, result, derivation, and review state of a quote.
Approve, adjust, or decline a quote that needs owner review.