> 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/release-notes/jul-3-2025-release.md).

# Jul 3, 2025 release

### Invoice preview

Now you can preview what a future invoice for an account will look like. This can be useful for testing that taxation is calculated correct and that usage records are properly recorded for an account.&#x20;

### Coupons

Coupons are back! Coupon codes can now be used on the checkout form to get one-time discount on a purchase.

### Multiple signers on quotes

In some situations quotes and contracts require multiple signers from each party. You can specify multiple users and contacts as signers on a quote. Bunny will insert the required signature fields before forwarding to e-signing.

### Event details on forms

The event panel on form has been improved to show more details for the events. More to come in this area.

### Email test buttons

The branding email form and work email fields now have a Send test email button that sends a test email to the current user. This makes it much easier to verify the format of the email.<br>


---

# 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/release-notes/jul-3-2025-release.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.
