# How Long It Takes To See Lift

Redux gets to work the moment you turn it on. It immediately starts classifying failures and scheduling optimized retries. But here's the thing: those retries don't all happen on day one. Redux runs them when they're most likely to succeed, which could be hours, days, or even a week later depending on the failure type.

### **What to expect:**

#### **1. Immediate start**&#x20;

Redux begins analyzing failures and scheduling retries right away.

#### **2. First results in a few days**&#x20;

As the first wave of scheduled retries runs, you'll start seeing early recoveries coming through.

#### **3. Clear lift within 30 days**&#x20;

Most recoverable failures will respond within the first billing cycle once Redux optimizes the timing.

#### **4. Peak performance at 6 to 8 weeks**&#x20;

Redux keeps learning your specific patterns. It gets better at handling your issuers, understanding your customer behavior, and nailing your subscription timing. The system hits its stride after about 6 to 8 weeks of learning from your real payment data.

#### **The bottom line:**&#x20;

You'll see early results within days, meaningful lift within your first month, and fully optimized performance once Redux has had 6 to 8 weeks to learn your unique payment patterns.


---

# Agent Instructions: 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:

```
GET https://docs.reduxpayments.com/recovery-performance/how-long-it-takes-to-see-lift.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
