> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/reviews/integrations/klaviyo-review-integration/review-reminder-emails.md).
# Review reminder emails
Configure reminder timing for review request emails.
Use this page to control when Roadmap sends follow-up review reminder emails after an order is fulfilled.
If you manage your full review-request flow in Klaviyo, also check [Introduction to Klaviyo review flow setup](/reviews/integrations/klaviyo-review-integration/introduction-to-klaviyo-review-flow-setup.md).
**Review Reminder Emails** are follow-up emails that prompt customers to leave a product review. Roadmap schedules them from the order's fulfilment date.
{% stepper %}
{% step %}
#### Open Review Reminder Emails
Go to **Reviews** settings and open **Review Reminder Emails**.
{% endstep %}
{% step %}
#### Enable reminders
Set **Review Reminder Emails** to **Enabled**.
Set it to **Disabled** if you want to stop sending reminder emails.
{% endstep %}
{% step %}
#### Set the first reminder delay
In **Send first reminder email after**, enter the number of days to wait after fulfilment before the first reminder is sent.
{% endstep %}
{% step %}
#### Set the second reminder delay
In **Send second reminder email after**, enter the number of days to wait after fulfilment before the second reminder is sent.
{% endstep %}
{% endstepper %}
### How the timing fields work
* **Send first reminder email after** delays the first reminder by a set number of days.
* **Send second reminder email after** delays the second reminder by a set number of days.
Reminder timing starts only after the order is marked as **fulfilled**. If an order is not fulfilled, the reminder schedule does not start.
### Recommended starting points
#### Common default
* **Send first reminder email after:** 0–3 days
* **Send second reminder email after:** 7–14 days
#### Higher-consideration products
* **Send first reminder email after:** 7+ days
* **Send second reminder email after:** 14–30 days
If review conversion is low, increase the first delay so customers have time to receive and use the product before you ask.
### Common questions
Reminders aren’t sending
Check that **Review Reminder Emails** is set to **Enabled**.
Then confirm the order has been **fulfilled**, since reminders are scheduled after fulfilment.
Customers are getting reminders too soon
Increase the value in **Send first reminder email after**.
If the second reminder also feels too close, increase **Send second reminder email after** as well.
I only want one reminder
Keep **Enabled** on, then set **Send second reminder email after** later than your normal review window.
Be careful with very short delays such as `0` days if fulfilment happens before delivery. Customers may receive a reminder before the product arrives.
### Related guides
* [Introduction to Klaviyo review flow setup](/reviews/integrations/klaviyo-review-integration/introduction-to-klaviyo-review-flow-setup.md)
* [Weekly review summary email setup (stores)](/reviews/integrations/klaviyo-review-integration/weekly-review-summary-email-setup-stores.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.roadmap.so/reviews/integrations/klaviyo-review-integration/review-reminder-emails.md?ask=&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.
