> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/administration/billing/plans-upgrades-and-payments-faq/using-coupons-and-promotions-at-bugsplat.md).
# Using Coupons and Promotions at BugSplat
In software development, every little bit helps, right? That's our thinking at BugSplat. We appreciate the work you do, so we sprinkle in some deals to make your day a bit brighter. Promotions and coupons are just our way of giving a nod to the awesome developers who choose us for their crash reporting needs. Here’s how you snag those savings, straightforward and simple, because every bit of savings counts.
**Applying Your Promotion Code**
1. **During Checkout:** When you're ready to upgrade your plan or kick off a new subscription, you'll find yourself at our straightforward checkout page. This is your gateway to savings.
2. **Locating the Promo Field:** Keep an eye out for the 'Add promotion code' option. You'll find this gem right below the 'Subtotal' in your order summary. It's hard to miss.
3. **Applying Your Code:** Enter your promotion code into the designated field and hit apply. Our system will then verify the code's validity. Upon successful application, you'll notice the plan information above adjusts to mirror the perks of your coupon deal, ensuring transparency and satisfaction before you proceed to payment.
**Trouble in Paradise?**
Sometimes tech has its quirks, and coupon codes are no exception. If you're experiencing any hitches with applying your promotion, or if the discount isn't reflecting as anticipated:
* **Reach Out:** Don’t fret. Simply drop us a line at . Whether it’s a hiccup in the system or just a query about the promotion's terms, we’re on standby to assist and make sure you secure your deserved discount.
---
# 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://docs.bugsplat.com/administration/billing/plans-upgrades-and-payments-faq/using-coupons-and-promotions-at-bugsplat.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.
