> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/quoting/quote-states.md).

# Quote states

When working with quotes, it is helpful to understad that a quote goes through different states and the operations that are possible depend on exactly which state the quote is in.

The diagram illustrates the possible state transitions.

<figure><img src="/files/ap8VgDx1IEPdmTH9SXzS" alt=""><figcaption><p>Quote states</p></figcaption></figure>

### **Draft**

The quote is still being worked on. This is the only state in which the quote can be modified. Once the quote is in the approval process or has been shared, no changes can be made.

### **Shared**

The quote has been shared with the customer, but not yet viewed. The quote can also be unshared, which will make it impossible for the customer to view it.

### **Viewed**

The customer has viewed the quote.

### **Accepted**&#x20;

The customer has been accepted and signed the quote in the portal by the customer. At this point, the typical next step is to apply the quote to the account.

### Approved

The quote has successfully gone through the approval process and has been approved by all approvers.

### Rejected

The quote was rejected by an approver.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bunny.com/guide/tour/quoting/quote-states.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.