The Comeback Flow
What a returning user sees in the first thirty seconds after a long absence.
The problem it solves
Someone came back after months away. The default experience drops them into an interface they half remember with data they no longer recognise, and they leave again within a minute.
The first thirty seconds back
A comeback flow is a distinct experience for returning users. It orients them, clears the accumulated mess, and gets them to one useful action fast. Teams put real effort into first-run onboarding and almost none into this, which is odd, because the returning user has already shown they will pay attention to you twice.
Three jobs, in order
Orient, clear, restart
- Orient
- Say how long it has been and what changed in plain language. Two or three items, not a changelog. The user needs to know whether the thing they remember still exists.
- Clear
- Handle the backlog for them. Offer to archive everything older than their absence in one action. Four hundred unread items is the reason they will close the tab.
- Restart
- Point at one concrete thing to do, drawn from their own data. Not a tour. A single action that produces a result they recognise.
The clearing step does most of the work and is the one that gets cut. A returning user is facing a pile of obligations your product generated in their absence, and if the only way out is item by item, most people choose the exit. One button that says mark everything before today as handled is a mercy, and it costs nothing you were going to get anyway.
Do not re-run onboarding. Someone who used the product for a year and came back does not need the tooltip tour, and forcing it tells them their history counted for nothing. Detect prior activation and branch.
Worked example
Two returns
A returning user of a project tool could land on a board with 312 notifications, eleven overdue items in red, and a banner about a feature they have never used. Or they could land on a short screen saying it has been four months, here is what changed, and here is a button to archive everything from before. The second version keeps them. The first is a wall.
When it fits
- Usage gaps of months are normal for the product, as in tax tools, travel, or seasonal work.
- State accumulates while the user is away, so returning means facing a backlog.
- The interface has changed enough that a returning user would be disoriented.
- You can detect prior activation: The moment a new user first gets the value the product promised. and branch away from first-run onboarding.
When it backfires
- The flow becomes a second onboarding. A tour forced on an experienced returning user reads as the product forgetting them.
- Orientation turns into a feature pitch. Someone who came back to do one thing does not want four screens about what shipped while they were gone.
- The bulk clear is omitted, leaving the backlog as a barrier, which is the single most common reason a comeback ends in thirty seconds.
- The flow is triggered by a manufactured absence threshold to justify an upsell moment rather than to help someone get reoriented.
Products using it
Slack
Offers a catch-up mode that walks a returning user through unread conversations one at a time with keep-unread and mark-read actions.
Gmail
Supports select-all-conversations across a whole label, so a returning user can clear thousands of messages in one action.
Figma
Leads a returning user with recently edited files from their own history rather than with a generic home view.
The psychology under it
The takeaway
Give a returning user orientation and a single button that clears what piled up, because the backlog, not the interface, is what sends them away again.
Finished the teardown? Bank it and the day counts toward your run.