Skip to main content

They opened the form, then left

Nudge Customers Who Clicked but Stopped

Someone who clicked the link already decided to help. Something interrupted them: a phone call, a camera they were not ready for, a form they meant to finish later. From Pro, an automation can start on that click, wait to see if the testimonial arrives, and send a short, different nudge only to the people who stalled.

  • Starts on the click, not on the original send
  • Waits for a finished testimonial before nudging
  • One nudge, one last offer, then it stops

The problem, solved

Why a click without a testimonial happens, and what to do

Situation 1 of 5

They clicked, and nothing came back

A click is the moment someone said yes in their head. Losing them at that point hurts more than losing someone who never opened the email.

How StoryProof solves it

From Pro, an automation can start when a review request is clicked, so this group gets its own flow.

Dated plan

Plan the days after a click

Pick the day a customer clicked and see when each step of the flow happens. Use the offsets as the waits in your automation.

  1. Day 0

    Click starts the automation

    The clicked trigger enrols the contact. Nothing is sent yet.

  2. Day +2

    Check: did a testimonial arrive?

    The wait for an event ends here. If they submitted, the run stops and they hear nothing more.

  3. Day +2

    Nudge for people who stalled

    One short email: "You started, here is the link again, and you can write or leave a voice note instead of video."

  4. Day +6

    Second check

    Wait again for a testimonial, branching the same way.

  5. Day +6

    Last offer

    A final two-line email that makes stopping easy: "If now is not a good time, no problem."

  6. Day +7

    Run ends

    No more email from this flow. Read the logs for runs that ended without a testimonial.

Dates are worked out in your browser. Nothing is saved or sent.

In StoryProof

Build the click nudge in StoryProof

  1. 1

    Choose the clicked trigger

    In the automation builder, start the flow when a review request is clicked. Work saves automatically and nothing runs until you publish.

  2. 2

    Wait for the testimonial, then branch

    Add a wait for an event, the testimonial arriving, with a limit of a couple of days. Branch on whether it happened.

  3. 3

    Write the nudge on the no branch

    Send one email on the branch where nothing arrived. Name the other formats and resend the link.

  4. 4

    Set quiet hours and a cap

    Limit sends to working hours and cap messages per person, so this flow and your other reminders do not pile up.

  5. 5

    Test with your own contact, then publish

    A test runs every step for real. Click your own request, leave it unfinished, and watch the nudge arrive in your inbox.

What happens next: Check the logs after a week. If almost everyone stalls, fix the form or prompts before adding more email.

Before you start

Honest limits of nudging on a click

  • A click is a signal, not a start

    The trigger tells you the link was opened, not how far into the form the person got.

  • Overlap with other reminders

    If a standard follow-up flow also runs, the same person could get both. Use the per-person cap, or stop one flow for clicked contacts.

  • Logs do not last forever

    Run history is kept for 30 days. Note anything you want to keep.

  • Needs automations

    The clicked trigger is part of automations, from Pro.

  • No pressure tactics

    Two messages is plenty. Someone who stops twice has given you an answer.

FAQ

Questions people ask

Short answers to what usually comes up next.

Why not just send the normal reminder to everyone?

People who clicked are in a different place from people who never opened the email. A nudge that says "you started" fits them better than a repeat of the first ask.

How long should the automation wait after the click?

A day or two gives people time to finish on their own. The plan above uses two days before the first nudge.

Will someone who submits get the nudge anyway?

Not if the flow waits for the testimonial and branches on whether it arrived. Test it with your own contact to confirm.

What should the nudge say?

Keep it short, resend the link, and offer the easier formats: an audio note or a few written lines instead of video.

Still have a question? Ask the StoryProof team or book a demo.

Win back the people who almost said yes

Start on the click, wait for the testimonial, and nudge only the people who stalled.

Last updated 2026-11-18.