> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/loyalty-manager/loyalty-concepts/point-accelerators.md). # Point accelerators A **point accelerator** is a promotional tool. Accelerators multiply the collected points based on the accelerator rules. For example, you might set up accelerators for club members, where club members receive 2x more points than non-club members. (In a club member scenario, the accelerator has be connected to a customer group.) You might also set up a promo for a specific date or range of dates, such as July 4th, where shoppers receive 4x more points. Similarly, you might also set up a "happy hour" accelerator for a normally slow time of the day, such as Tuesday mornings, where shoppers receive 5x more points. Refer to the following topics for more information: * [**Accelerator types**](/loyalty-manager/create-point-accelerators/accelerator-types.md) * [**Accelerator rules**](/loyalty-manager/create-point-accelerators/accelerator-rules.md) --- # 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.rmhpos.com/loyalty-manager/loyalty-concepts/point-accelerators.md?ask=&goal= ``` `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.