> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/sales-and-marketing/coupons.md).
# Coupons
Create promo codes that customers enter in the booking form.
Coupons are promo codes that give customers a discount. Open **Sales & Marketing → Coupons**.
The list shows the **ID**, **Promo code**, **Type of discount**, **Discount Value**, whether it is **Multi-Use**, and when it was **Created At**.
## Create a coupon
Click **Add new**.
The Create coupon form.
| Field | What to enter |
| ------------------------------ | ------------------------------------------------------------------------------------- |
| **Promo Code** | The code the customer types, for example `SUMMER10`. Required. |
| **Discount type** | **Fixed amount** or **Percentage**. Required. |
| **Discount value** | The amount or the percentage. Required. |
| **Can be used multiple times** | Tick it to let the code be used more than once. Leave it empty for a single-use code. |
Click **Save**.
{% hint style="info" %}
The booking form has a coupon code field. You can turn its help tooltip on or off in the booking form settings.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://codico-dispatch.gitbook.io/documentation/sales-and-marketing/coupons.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
