Get a Demo Get Started

Milestone Progress Reminders

Get Started

Ship this workflow

Pick how you want to build it.

Try it in the dashboard Fastest Go to Workflows → New Workflow → Use sample workflow in your workspace, and select this workflow. Try it
Build with the SuprSend Agent Try the agent
Build with SuprSend MCP Set up MCP

When to use this workflow

    A missed day breaks a streak the user worked to build. One slip ends the run and the habit it was forming.

    A reminder early in the day is forgotten by the deadline. The user means to act, then runs out of time.

    A generic nudge does not say what is about to be lost. "Come back" carries no weight without the streak behind it.

    A streak save has only a short window to land. Once the deadline passes there is nothing left to save.

How it works

1

Streak at risk

When a user's streak is at risk (STREAK_AT_RISK), a reminder goes out right away.

TriggerSmart Channel Routing
2

Waits for the user to act

It then waits, watching for the user to complete the action.

Wait Until
3

Last chance before the deadline

Two hours before the streak deadline, a final reminder goes out if the action is not done.

Wait UntilSmart Channel Routing
4

Acting ends it

Completing the action (ACTION_COMPLETED) stops the reminders.

Wait UntilExit

Best practices

    Time the last reminder close to the deadline

    Two hours before is recent enough to feel urgent and still leaves time to act. A nudge the night before is forgotten by morning.

    Name the streak the user is about to lose

    "Your 12-day streak ends in 2 hours" carries more weight than "come back". Say what they have built and what breaks if they do nothing.

    Link the reminder straight to the action

    The window is short, so the reminder should open the exact task to complete, not the app home. One tap to act is the difference between saving the streak and losing it to friction.

Common mistakes to avoid

    Sending the save to users without a streak at stake

    A save only lands if there is something to lose. Fire STREAK_AT_RISK for users with an active streak worth keeping, not every account, or the reminder reads as a nag.

    Guilt-tripping the user into acting

    "You're about to lose everything" reads as pressure. Keep it encouraging, like "one action keeps your streak alive", so it pulls the user back instead of pushing them off.

    Leaving the final save to one channel at a time

    Smart Channel Routing tries channels one at a time, cheapest first, until one is seen. With minutes left on the clock, you can send the last chance on every channel at once instead, so it is not still waiting on a quiet channel when the deadline hits.

What users receive

The actual notifications this workflow sends, on each channel.

Few Minutes Left for Streak Completion

Email
Few Minutes Left for Streak Completion — Email
In-app inbox
Few Minutes Left for Streak Completion — In-app inbox
Android push
Few Minutes Left for Streak Completion — Android push

What good looks like

Primary signal Streaks kept

More streaks survive

More users keep their streak when a last-chance reminder reaches them in time, compared with no nudge.

Fatigue signal Mutes

Streak reminders get muted

When users turn off streak reminders, the saves are firing too often or for streaks they do not care about.

Support

Frequently Asked Questions

Quick answers about setting up and running this workflow.

Two hours before the streak deadline by default. Adjust the Wait Until offset to send it earlier or later.

Email, in-app inbox, and mobile push. Smart Channel Routing picks among them, cheapest first, one at a time until the reminder is seen, rather than sending all at once.

Your own STREAK_AT_RISK event, which you fire when a streak is genuinely close to breaking. The workflow then runs the reminders and stops as soon as the user acts.

After the last-chance reminder the workflow ends and the streak breaks. To bring the user back later, pair this with Re-engagement With Inactive Users.

Set streak_deadline a few minutes out and fire STREAK_AT_RISK, then fire ACTION_COMPLETED with the same streak_id to check the stop. Use the Test button, the SuprSend Agent, or the API, CLI, or MCP.

Ship Milestone Progress Reminders in under 5 minutes.

Try directly in SuprSend

Fastest

Sign up and test the workflow directly in the dashboard.

Get Started

Build with the SuprSend Agent

Copy the prompt, paste it into the Agent in your SuprSend dashboard, and the workflow gets built for you.

Try the agent

Build it with SuprSend MCP

Set up SuprSend MCP in Claude Code, Cursor or Windsurf, copy the prompt, and the workflow builds itself in your workspace.

Set up MCP