> 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/weekly-review-summary-email-setup-stores.md).

# Weekly review summary email setup (stores)

### What the weekly summary email includes

The **Weekly Summary Email** sends a weekly snapshot of your review activity, including **last week’s review count** and a **quick link** to view that time period.

<figure><img src="https://content.gitbook.com/content/J8asLD4FVCFagK40xEr4/blobs/awLuLajqzmA2uVIfltEd/Screenshot_2026%2002%2024_at_9.25.44_AM.png" alt=""><figcaption></figcaption></figure>

### Set up the Weekly Summary Email

1. Open the Weekly Summary Email settings\
   Find the section titled **Weekly Summary Email**.
2. Enable the weekly summary\
   Under **Weekly Summary Email**, select **Enabled**.\
   If you do not want to send the summary, select **Disabled**.
3. Add recipients\
   In **Recipient email(s)**, enter one or more email addresses.\
   Use a comma-separated list (for example: `owner@example.com, team@example.com`).
4. Choose how many products to include\
   In **Top products to show**, enter the number of top products you want included in the weekly email (for example: `5`).
5. Send a test email\
   Click **Send test email** to preview delivery and confirm the recipient list is correct.\
   Send the test email to yourself first, then add additional addresses once you’re happy with the format and content.

### Troubleshooting

<details>

<summary>I enabled it, but no one is receiving the email</summary>

* Double-check the **Recipient email(s)** field for typos and ensure multiple addresses are separated by commas.
* Use **Send test email** to confirm delivery to at least one address.
* If your inbox filters newsletters or automated emails, check spam/junk and any team email quarantines.

</details>

<details>

<summary>The recipient list format keeps failing</summary>

Enter emails as a comma-separated list with no extra characters. Example:

```
owner@example.com, team@example.com
```

</details>

<details>

<summary>What does “Top products to show” affect?</summary>

This controls how many top products are included in the weekly summary email content. Increase the number to show more products; decrease it to keep the email shorter.

</details>


---

# 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/weekly-review-summary-email-setup-stores.md?ask=<question>&goal=<user_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.