> For the complete documentation index, see [llms.txt](https://help.airreviews.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.airreviews.io/collect-reviews/notifications.md).

# Notifications

## Notifications

### **1. Access Notifications Settings**

Open the **Air Reviews** app in your Shopify admin and go to **Collect reviews**.

Locate the **Email notifications** card and click **Setup** to start setting up your email templates.

<figure><img src="/files/Uw4xPsU4kzxcSDu64dGt" alt=""><figcaption></figcaption></figure>

The Notifications page lists every email type Air Reviews can send. Each row has its own toggle so you can enable or disable a specific email without affecting the others. Use the master toggle next to the page title to turn the entire feature on or off.

#### Air Reviews currently supports 5 emails:

* **Review reminder** — sent based on the order's status to ask customers for a review.
* **Photo review reminder** — asks for product photos after a positive review.
* **Discount usage notification** — sends a discount code to customers after they review.
* **Review reply** — notifies the customer when you reply to their review.
* **Confirm edit review** — sends a confirmation when a customer requests to edit their review.

Click **Email settings** on any card to customize that email's content, design, and conditions.

#### Common email settings

Every email editor in Air Reviews shares the same set of fields. They are documented once here; the per-email sections below only cover what is unique to each type.

* **Subject** — the email subject line. Variables such as `{{shop_name}}`, `{{customer_name}}`, and `{{product_name}}` are supported.
* **Logo** — upload an image to appear at the top of the email.
* **Content** — edit the body with the rich text editor. The toolbar supports bold, italic, underline, color, link, alignment, lists, indent, font family, font size, custom variables, and raw HTML insert.
* **Button text** — the call-to-action label.
* **Background color** / **Text color** — control the button's appearance.
* **Footer text** — small text shown below the body.
* **Custom CSS** — toggle on to inject your own CSS for advanced styling.
* **Preview (Light mode / Dark mode)** — the right-hand panel renders the email in both themes; switch between them with the buttons at the top of the panel.
* **Send test** — use the **Send test** action at the top of the page (or the **actions** menu ⋯) to email yourself a sample.

<figure><img src="/files/2YmFhmHGDpGLdPmiM9zr" alt=""><figcaption></figcaption></figure>

To see all supported variables, click the **Variables** button in the editor toolbar.

<figure><img src="/files/aokmU4lLUHAYBFWUm7fz" alt=""><figcaption></figcaption></figure>

### **2. Review reminder**

This email invites customers to write a review for the product they purchased.

#### **2.1 Email type**

* **Simple email** — invites customers to visit your storefront to submit a review.
* **Interactive email** — let customers leave a review directly from the email. They simply click the button in the email, which opens the storefront with pre-filled content ready for submission—no need to rewrite anything.

Take a tour of the interactive email setup:

{% embed url="<https://app.arcade.software/share/I0eLoRfzGQh9karHofOu>" %}
Set up the interactive email settings
{% endembed %}

You can verify how it behaves by sending a test review reminder:

{% embed url="<https://app.arcade.software/share/g4QWAXYSdnkocgcMvLTH>" %}
Test the email workability
{% endembed %}

#### **2.2 Discount review request**

Toggle **ON** to attach a discount code to the review request — a stronger incentive for customers to follow through.

#### **2.3 Hide default email content**

Toggle on to remove the default review-request block. Useful when you've written a fully custom body and don't want the built-in copy to appear above it.

### **3. Photo review reminder**

Asks customers who already left a positive review to come back and add photos.

#### **3.1 Time settings**

* **Send after** — the delay before the email is sent (e.g. 5 minutes after the review).
* **Send email for** — the minimum star rating that triggers the email (e.g. 4 stars and up).

### **4. Review reply**

Sent automatically when you respond to a customer's review.

### **5. Confirm edit review**

Sent to a customer when you request that they edit their review (the request is initiated from **Manage reviews**).

### **6. Discount usage notification**

Send a discount code to your customer after they leave a review, as a thank-you and an incentive to come back. The email is split into 2 tabs:

* **Discount notification** — sent right after the customer's review is submitted, delivering the discount code.
* **Discount expiration reminder** — a follow-up before the discount expires, nudging the customer to use it.

{% hint style="info" %}
**Note**: The discount code itself is configured in the **Discount** feature. This email controls only the wrapper that delivers the code. To create or edit the underlying discount, see the [Discount](https://help.airreviews.io/collect-reviews/discount) guide.
{% endhint %}

***

*That’s it! You've now set up various notifications to engage with your customers and manage their reviews effectively.*


---

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

```
GET https://help.airreviews.io/collect-reviews/notifications.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.
