One ordered timeline instead of a generic campaign builder
The first step is the initial request. Later steps wait from the previous accepted or visibly skipped delivery, so the sequence advances from facts the system can verify.
SMS and email steps
Choose either supported channel per step and arrange the exact order. The initial step starts at the journey’s scheduled time.
Wait days per follow-up
Set a nonnegative wait after the prior step. Quiet hours still apply when the calculated send time lands inside the blocked window.
Named campaigns
Keep more than one campaign for a business, with exactly one default sequence used by new journeys unless another is selected.
Each step says exactly what that moment needs
Campaign copy belongs to the step. A blank field falls back to your account template override or ReviewNudger’s built-in neutral default.
Text message body
Write concise SMS copy for each text step while ReviewNudger supplies the customer’s review-request link at send time.
Email subject and body
Email steps own their subject, body, and button label, with the sending business’s required postal address included by the renderer.
Edits apply going forward
A campaign stays attached to its journeys, and edits affect unsent steps in those in-flight journeys instead of cloning stale copy.
A follow-up never outranks consent or operator control
Every due step rechecks whether its channel is usable and whether the journey should continue.
Opt-outs are immediate gates
SMS opt-outs, email opt-outs, and do-not-contact status prevent the affected customer from receiving another message.
Stop remaining follow-ups
An operator can stop a journey’s future campaign steps without deleting its delivery history or changing what already happened.
Skips stay visible
When one channel is unavailable but a later step can still work, ReviewNudger records a skipped delivery and advances from that timestamp instead of failing silently.
How an ordered campaign advances
The sequence uses recorded delivery outcomes to decide what is due next, which keeps retries and edits understandable.
- 1Create or edit the named campaign, put steps in order, choose SMS or email, and set the copy and wait days for each step.
- 2A new review-request journey uses the business’s default campaign and schedules its first step from the request delay.
- 3After an accepted or visibly skipped delivery, the next enabled step waits its configured number of days before becoming due.
- 4Before every send, ReviewNudger rechecks the account pause, follow-up stop, opt-outs, contactability, quiet hours, and channel readiness.
See the workflow
The campaign editor keeps channel, timing, and step-owned copy together in one ordered view.
What this feature does not promise
ReviewNudger is deliberately clear about provider boundaries, consent, and outcomes.
- Campaigns support ordered SMS and email steps only. They do not include branches, audience segments, conditions, or trigger-rule builders.
- Changing a campaign affects its unsent steps for in-flight journeys; it does not rewrite messages already sent.
- A skipped step means the channel was unusable at that moment. It does not create a provider send attempt.
- Texting and email setup still determine whether each channel can send, regardless of the campaign configuration.
Frequently asked questions
How many campaigns can I create?
You can keep multiple named campaigns for the business, with exactly one default. The default is the sequence new review-request journeys use unless another campaign is explicitly selected.
When does the wait for a follow-up begin?
Wait days count from the previous step’s accepted delivery or its visible skipped-delivery timestamp. That gives the next step a stable, replay-safe anchor.
What if a customer has no email address for an email step?
If a later usable step exists, ReviewNudger records the email step as skipped and continues the ordered sequence. The dashboard keeps the skip reason visible.
Can I stop follow-ups for one customer?
Yes. Stop remaining follow-ups on that review-request journey. The action is written once, and the earlier delivery record remains intact.
Keep exploring
Follow the feature into the relevant workflow, free tool, or practical guide.