Managing notification recipients

Last updated: May 13, 2026

The Notifications tab in BetterReviews (Settings → Notifications) is the single place to manage who gets BetterReviews emails for your store. Each recipient can independently receive review-moderation notifications (per-pending-review pings) and/or customer-support cascade emails (chat-bubble forwards plus the V2 bundled support cascade).

If you previously configured addresses under the legacy Settings → Support panel, BetterReviews carried them forward into the Notifications tab automatically. They show with an Imported badge and are pre-set for customer support emails — flip the Reviews checkbox if you also want them on the per-review moderation list.

Adding a recipient

  1. Open BetterReviews in your Shopify admin
  2. Go to Settings → Notifications
  3. Click Add recipient, enter the work email address
  4. Decide which kinds of emails this address gets — at least one of Reviews / Support must be checked
  5. The recipient receives a one-time verification email at the new address. They click the confirmation link to activate the row

You can have up to 5 active or pending-verification recipients per store. Active and pending count toward the cap together so a forgotten un-clicked verification can’t silently use up a slot.

What the two checkboxes mean

  • Reviews — receives the per-review notification email when a review needs human action (approve, reply, archive, reject). Uses the V1 single-review action template with 4 buttons.
  • Support — receives the chat-bubble support forward when a customer flags an issue mid-conversation, AND the V2 bundled cascade for reviews classified as support tickets (3 buttons: Reply privately, Hold 5 days, Reject; up to 3 follow-up nudges over 9 days).

A recipient with both boxes checked receives the union of both surfaces. A recipient with neither box checked is invalid — the server rejects the change with a “pick at least one” error.

Verification flow

When you add a recipient, BetterReviews mints a 7-day verification token and emails it to the new address. The recipient clicks the link; the GET landing page is scanner-safe (it doesn’t activate the row), and the POST confirmation activates them. Until they confirm, the row stays in pending verification state and they don’t actually receive any notifications.

If they don’t click within 7 days, the row flips to expired — you can resend a verification email from the Notifications tab, or revoke the row.

The recipient’s email is stored encrypted at rest. In the admin you see a masked version (s••@msqc.com) so the full address never appears on a session-replay snapshot.

Removing a recipient

Click Remove on any row. The row flips to revoked state. Existing in-flight emails (already sent before revoke) still arrive in their inbox, but no further sends fire. Re-adding the same address creates a new row (with a new verification round-trip) — the audit trail of “added Jan 1, revoked Mar 4, re-added Jun 12” stays intact.

If a recipient wants to remove themselves without admin action, every BetterReviews email they receive carries an Unsubscribe link in the footer + a one-click List-Unsubscribe header that mailbox providers honor for one-click revoke. Both routes flip the same row to revoked.

What changed in the unified update (May 2026)

Before this update, recipients lived in two places:

  • Legacy Settings → Support — up to 3 addresses for chat-bubble support forwards
  • Legacy Collect → Email moderation — up to 5 addresses for per-review moderation pings

Each panel had its own UI, its own verification flow, and (for the moderation list) a role discriminator. The unification:

  • Promotes the moderation-list table (PII-encrypted, verification-required, audit-logged) as the single source of truth for both surfaces
  • Replaces the role discriminator with two independent boolean flags
  • Backfills all existing Settings → Support addresses into the unified table with the Customer support flag pre-set
  • Sends each backfilled recipient a one-time intro email so they know where to manage themselves
  • Keeps the legacy panels rendered (read-only) for one quarter so bookmarked URLs still work

The Collect → Email moderation page keeps its mode toggle (Instant / Digest only / Off), the auto-thank-you checkbox, and the Invalidate-all panic button — those settings are about how notifications fire, not who receives them.