Get a Demo Get Started

Celebration & Achievement Notifications

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 routine badge and a major milestone get notified the same way. Treating them alike trains the user to tune out both.

    Small wins sent one at a time become noise. A burst of routine badges means a burst of separate pushes.

    A big achievement sent only to the inbox is missed. A milestone worth celebrating needs to reach the user where they are.

    A celebration that lands hours later falls flat. "Congrats" long after the moment means nothing.

How it works

1

An achievement happens

A user earns a badge or hits a milestone (GAMIFICATION_EVENT).

Trigger
2

Routed by how big it is

The achievement is sorted into routine, notable, or major by its significance.

Branch
3

Routine wins arrive together

Low-significance badges are batched into one in-app inbox recap.

BatchInbox
4

Notable wins batched across channels

Medium ones are batched into a single push and inbox notification.

BatchMulti-Channel
5

Major milestones celebrated at once

High-significance wins go out immediately on email, push, and inbox.

Multi-Channel

Best practices

    Match the celebration's weight to the achievement

    Reserve the loud, immediate channels for real milestones. A Branch on significance keeps routine badges quiet so the big wins still feel big.

    Batch the routine wins, do not drop them

    Small badges still matter to the user, just not one push each. Batch them into a single recap so they are seen without the noise.

    Make the major celebration feel like a reward

    A milestone is a moment to reinforce. Pair the high-significance message with what the user unlocked or the next tier, not just "nice job".

Common mistakes to avoid

    Sending everything as a major milestone

    If the event does not carry a real significance, every achievement falls to the high path and goes out on email and push. Tag each event so routine wins route to the quiet path.

    Letting the batched recap arrive stale

    Routine wins batched over too long a window land after the user has moved on. Keep the batch window short enough that the recap still feels current.

    Celebrating a milestone before it is final

    A "congrats on your 100th order" that fires before the return window can be undone by a refund, and a streak counted today can break tomorrow. Fire the celebration on the confirmed milestone, so the moment does not have to be walked back.

What users receive

The actual notifications this workflow sends, on each channel.

High Significance Celebration Events

Email
High Significance Celebration Events — Email
In-app inbox
High Significance Celebration Events — In-app inbox
Android push
High Significance Celebration Events — Android push

What good looks like

Primary signal Engagement

Users come back after a win

Users return more often when achievements are celebrated at the right weight, compared with a stream of identical badge alerts.

Fatigue signal Mutes

Achievement alerts get muted

When users turn off achievement notifications, too many routine badges are going out as their own alert.

Support

Frequently Asked Questions

Quick answers about setting up and running this workflow.

By the achievement's significance. Routine badges become one inbox recap, notable wins a batched push and inbox, and major milestones go out at once on email, push, and inbox.

Just grouped. Low-significance wins are batched into a single inbox recap so the user still sees them, without a separate alert for each.

In-app inbox for routine wins, push and inbox for notable wins, and email, push, and inbox together for major milestones.

Yes. Edit the Branch conditions to set the significance levels and which channels each one uses.

Fire a GAMIFICATION_EVENT at low, medium, and high significance and watch each route. You can trigger from the Test button in the editor, the SuprSend Agent, or the API, CLI, or MCP.

Ship Celebration & Achievement Notifications 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