# Product Browsing Recovery

## Best Practices for running a product browse recovery campaign

**What to do:**

* Use **multi-step nudges** instead of one-off reminders.
* **Personalize** based on user type (new vs returning).
* Include **social proof**, product quality assurance, and **feedback capture**.

**How to do:**

1. **15 mins later**: Reminder about the browsed product with **testimonials** or user reviews.
2. **4 hours later**: Highlight **product quality, hygiene**, or brand trust—especially for new users.
3. **24 hours later**: Send a **limited-time discount offer**.
4. **48–72 hours later**: Request **feedback** on why they didn’t purchase.

**Why this works:**

* Keeps the product top-of-mind.
* Supports high AOV users who need more time.
* Helps low AOV products stay competitive.
* Feedback aids in better segmentation and future targeting.

## Sample templates for a product browse recovery campaign

<div><figure><img src="/files/hp58zl35dRvzCVX2fY4Z" alt=""><figcaption><p><strong>15 mins later</strong></p></figcaption></figure> <figure><img src="/files/q0iJaZ5Ge4873IjJo6se" alt=""><figcaption><p><strong>4 hours later</strong></p></figcaption></figure> <figure><img src="/files/IwBioz95ngwo5NiPAP2Y" alt=""><figcaption><p><strong>24 hours later</strong></p></figcaption></figure> <figure><img src="/files/9zioLzq3J0ZER3vti7lu" alt=""><figcaption><p><strong>48–72 hours later</strong></p></figcaption></figure></div>


---

# 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.quickreply.ai/product-modules/campaigns/sample-drip-campaigns-for-shopify-users/product-browsing-recovery.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.
