> 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/customer-portal/viewing-quotes.md).

# Viewing quotes

When you share a quote with a customer, the customer contact will receive an email with a link that brings up the quote in the portal.&#x20;

{% hint style="info" %}
You can customize this email message via **Workflows > Quotes**.
{% endhint %}

When the customer clicks the email link, they are presented with the quote inside the portal. Here they can download the quote as a PDF and start the signing process.

<figure><img src="/files/wxJ3OFtZwLUaCETmNx4L" alt=""><figcaption></figcaption></figure>

Bunny supports signing via [Docusign](/guide/advanced-guides/integrations/docusign.md), [PandaDoc](/guide/advanced-guides/integrations/pandadoc.md), [Dropbox Sign](/guide/advanced-guides/integrations/dropbox-sign.md) and [Bunny Sign](/guide/advanced-guides/integrations/bunny-sign.md), Bunny's own, free e-signing option. Every signing solution has a slightly different flow, and the Start signing button will initiate it.

Bunny Sign takes the user directly to the signing page. If there are multiple signers, they will be notified by email.

<figure><img src="/files/JQEr0FC3KPi0596LBSY7" alt=""><figcaption></figcaption></figure>

Once every one has signed the quote, the final PDF will be generated, the quote will transition to `accepted` and the account owner in Bunny will be notified.

<figure><img src="/files/LAUBsA1EjPeQ4eCnNbrT" alt=""><figcaption></figcaption></figure>

The signing process can also include capturing Tax ID and purchase number if enabled on the [invoice template](https://docs.bunny.com/guide/tour/entities/invoices#invoice-templates) used by the account.


---

# 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/customer-portal/viewing-quotes.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.
