The Review Reminder Message

Follows up with customers who were asked for a review and haven’t left one. It doesn’t choose who — the Review Request already did that. This only decides how long to wait.

Where: Settings → Automated messages → Review Reminder

---

What it does

The reminder’s audience is whoever the Review Request asked and didn’t hear back from. That’s why this message has no Product Rules and no prioritisation of its own — it inherits the request’s audience by construction.

Reorbit stops reminding 30 days after the request went out, whatever you set. Past that the customer has moved on, and a reminder about a month-old purchase reads as spam rather than a nudge.

---

When to remind

The same three-way choice as the request, counted from when the request was sent rather than from delivery:

Option	What happens	The number field
Automatically, from what your customers do (Recommended)	Reorbit picks the gap from how long your customers typically take to review.	Hidden — there isn’t one
Automatically, but never sooner than my minimum	Learned timing with a floor you set. It may wait longer, never less.	Never remind before (days)
Always exactly my number	Reminds exactly that many days after the request.	Days after the request was sent

The number accepts 3 to 30 days. Three is the floor because a reminder any sooner arrives while the first email is still in the inbox; thirty is the ceiling because that’s when reminding stops regardless.

---

The other fields

Field	What it does
Variant Name	Your own name for this set of settings.
Channel	Klaviyo, as with every Reorbit message today.

There is no Product Prioritization and no Product Rules here. Both belong to the request.

---

Worked example

Field	Value
When to remind	Automatically, but never sooner than my minimum
Never remind before (days)	7

Why seven. A week is long enough that the first email has been dealt with or forgotten, and short enough to land inside the 30-day window with room for the learned timing to push later if it wants to.

---

Tips

• One reminder is enough. There’s no second follow-up, deliberately — the return on a third email is close to zero and the unsubscribe cost isn’t.
• Don’t set it near 30. That leaves the learned timing no room to move, and anything past 30 days never sends.
• Remember it shares your weekly limit. A request and a reminder in the same week both count against Most messages per customer, per week. (See Delivery settings.)
• One Klaviyo flow serves both. Request and reminder arrive on the same Klaviyo metric, so you can’t currently write separate copy for the follow-up.

---

FAQ

Can I write a different email for the reminder?

Not today. Review Request and Review Reminder arrive on the same Klaviyo metric, Reorbit Sparks - Review Request, so one flow handles both.

Why can’t I choose which products the reminder covers?

Because it follows up on requests that already went out. The audience was decided by the request’s Product Rules.

What if a customer reviews before the reminder is due?

They drop out. The reminder only goes to people who were asked and haven’t left one.

Is the number counted from delivery?

No — from when the request was sent. The request’s own timing is counted from delivery.

---

Next steps

• Next: Welcome — the message new members get.
• Related: Review Request · How Review Requests Work