> For the complete documentation index, see [llms.txt](https://help.trybeans.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.trybeans.com/liana/rules/inactivity.md).

# Inactivity

The Inactivity rule helps keep your business away from competitors and helps keep your customers active on your online store. The Inactivity rule works by discouraging the absence and inactivity of your customers by making them lose a particular number of points for a period of inactivity in your store.

We recommend you to set it between 50 - 70 days. Please note that after the number of days you set the customers will lose some of their points if they have been inactive.

## Settings

![](/files/-Ltz68EpWTpdxVGEDXM8)

1. **Points:** The number of points the customer will lose after a certain number of days as set by the retailer. 
2. **Inactivity Period(in days):** The number of days the points remained without been used.


---

# 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://help.trybeans.com/liana/rules/inactivity.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.