How Review Requests Work

Once your store, booking, or payment tool is connected, review collection is fully automatic. Here’s exactly what happens after a sale — and the rules that keep it from annoying your customers.

The timeline

1. Sale — your store or booking tool notifies PraisePipeline the moment a sale is recorded.
2. The wait — we don’t ask right away. The customer gets time to form a real opinion first. This wait is configurable on your Branding page (default 7 days) — set it shorter for a service (even same-day) or leave it around a week for shipped goods.
3. Review request email — a short email from your company name inviting them to share their experience, with a link to your review page. See The review request email for exactly what it looks like.
4. Review submitted — their rating, tags, and comments land in your dashboard for moderation, and they’re invited to repost the review on Google.

Built-in guardrails

The 60-day cooldown

A customer who has recently been asked won’t be asked again for 60 days — even if they buy or visit several times in that window. Repeat customers get a breather; you get better response rates. A repeat purchase in that window, or one from a customer whose request is already scheduled, doesn’t count toward your monthly limit either: it’s skipped as soon as it arrives.

Your plan’s monthly limit

Each plan includes a number of review requests per billing period (see Plans & Billing). Requests already queued count toward it, not just sent ones. Once you reach it, further sales in that period don’t schedule a request — they aren’t queued for later — and requests resume at the start of the next period, or as soon as you upgrade.

When you reach the limit, a banner across your dashboard says so, and your account admins get one email about it per billing period. Admins can compare plans straight from the banner.

Real sales only

Requests are triggered by real, paid sales — not marketing lists. The test events your store or tool sends when you first set up a webhook are recognized as tests and never emailed to anyone.

Frequently asked

A customer’s sale didn’t trigger an email — why? Most often the 60-day cooldown (they were asked recently), or the sale happened more recently than your configured wait and the request is still scheduled. It can also be your plan’s monthly limit, or a paused account (a lapsed trial or subscription — see Plans & Billing). You can also check that your connection shows as Active in Integrations.

Can I change the wait before a request goes out? Yes — set the number of days to wait on your Branding page (default 7). The 60-day cooldown is fixed, as it’s tuned for deliverability and sender reputation.