> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/earning-rules/promotions-and-bonus-earnings/time-bonus.md).

# Time bonus

**Accessing the time bonus feature**

To access the time bonus feature, follow these steps:

1. From the Dashboard, click on "Loyalty Program" in the left navigation.
2. Click on the "+" icon next to "Bonus Earnings" toward the bottom of the page.
3. Click on "Time."

**Using the time bonus feature**

When setting up a time bonus, you can:

* **Select earning rules:** Choose the earning rules that you want to incentivize.
* **Set point multiplier:** Specify the point multiplier, such as 2x. For example, if a customer usually earns 5 points per visit, setting the multiplier at 2x will change this to 10 points per visit.
* **Select valid earning locations:** Choose the locations where the bonus will be applied.
* **Categorize the bonus:** Optionally, select the category to display the bonus under if applicable.
* **Choose time periods:** Specify the days of the week and times of the day that the bonus will be applied.


---

# 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.perkville.com/features/earning-rules/promotions-and-bonus-earnings/time-bonus.md?ask=<question>&goal=<user_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.
