Payment-triggered without being payment-platform dependent
Connect a supported payment app or use Zapier and authenticated custom triggers. The payment is the signal; ReviewNudger owns the review-request decision from there.
Choose the delay
Send after the delay you set instead of interrupting the customer at checkout. Quiet hours can move a due send to the next allowed time in your business timezone.
Use text, email, or both
The request follows the channels you enable and skips a channel visibly when the required contact or sending setup is unavailable.
Pause without disconnecting
An account-level pause stops new automated requests and queued sends while billing, Google syncing, and the dashboard remain available.
Every trigger is checked before it can become a customer journey
Retries and duplicate provider events are normal. ReviewNudger keeps the trigger receipt, canonical event, customer journey, and individual send attempts separate so a retry does not silently become a second request.
Duplicate protection
Stable receipt, event, journey, and send keys collapse replays at each boundary instead of relying on timing or a best-effort memory check.
Cooldown rules
A configurable cooldown prevents the same customer from being asked again too soon, even when another payment arrives.
Consent and suppression checks
SMS opt-outs, email opt-outs, do-not-contact status, missing contact details, and disabled automation all stop the affected request or channel visibly.
The request does not depend on predicted sentiment
Automation is based on the payment and your sending policy—not whether ReviewNudger thinks a customer will leave a positive review.
One neutral standard
Every customer receives the same honest request. ReviewNudger does not hide the Google review link from unhappy customers.
Private feedback stays optional
You can offer a private feedback path, but every negative or below-threshold pre-screen path still shows the public-review link.
Visible outcomes
Created, suppressed, skipped, failed, and sent states remain visible so an operator can understand what happened instead of guessing.
From paid job to review request
The customer-facing send is the end of a deliberate chain, not a side effect fired directly from a webhook.
- 1A connected app reports a completed payment, or an approved manual trigger starts the same review-request policy checks.
- 2ReviewNudger normalizes the event, resolves the customer, and checks automation status, cooldowns, contactability, and consent.
- 3One review-request journey is scheduled with the location’s default ordered campaign and your chosen initial delay.
- 4Each due text or email is reserved before the provider call, so an application retry cannot create a duplicate send.
See the workflow
A customer can go to Google or leave private feedback. The public review path stays available to everyone.
What this feature does not promise
ReviewNudger is deliberately clear about provider boundaries, consent, and outcomes.
- Automated payment triggers require a supported native integration, Zapier connection, or authenticated custom trigger.
- Customer-facing text messages send only after your business texting number is approved; there is no temporary shared-number fallback.
- Email requests require a usable business postal address so the message can include the sender information commercial email rules require.
- Automation cannot guarantee a customer will leave a review or that Google will publish it.
Frequently asked questions
Can I send review requests manually too?
Yes. Dashboard manual sends and the staff-facing quick send link run through the same automation-enabled, consent, contact-channel, and cooldown checks as payment-triggered requests.
What happens when the same payment event is delivered twice?
ReviewNudger uses stable duplicate-protection keys at ingestion, normalization, journey creation, and sending. A replay can resume visible processing, but it cannot create a second journey or provider send for the same boundary.
Does ReviewNudger send only to happy customers?
No. Eligibility is based on your neutral sending policy, not predicted satisfaction. Optional pre-screen modes never remove the public-review link from a negative or below-threshold path.
Can I control when messages arrive?
Yes. Set the initial delay and optional quiet hours. Campaign follow-up steps add their own wait days after the previous accepted or visibly skipped delivery.
Keep exploring
Follow the feature into the relevant workflow, free tool, or practical guide.