Reactivation Campaign

While users were sorted only into arrivals and departures, the middle of the list was empty. A team still paying but no longer logging in belonged in neither column: the invoice says customer, the absence of a cancellation says not gone.

What Ravi found reading last quarter's cancellations backwards shows the size of that gap. Of 120 teams that cancelled, 100 had not opened the product once in their final two months. Cancelling was not the decision — it was the paperwork on a decision made weeks earlier. Meanwhile the dashboard carried active users and cancellations and nothing else, so the 400 teams sitting quiet on day 40 appeared in neither number.

The reactivation campaign exists for those 400. Meeting someone on the cancellation screen is too late, so the sequence moves earlier: reach out while they are quiet and get the product opened one more time. At that point the person is still a paying customer, which makes keeping them considerably cheaper than winning them back after the account closes.

Six steps, from picking who gets a message to deciding when to stop sending.

1. Set what counts as quiet. How many days since the last visit puts an account on the list. Fourteen days is a starting point for a product people use daily; thirty for one they open once or twice a week.
2. Build the list. Days alone push the list into the thousands, so it gets narrowed with churn signals, the behavior patterns that suggest someone is close to leaving. Accounts where several signals overlap get classified as at-risk users, which turns the list into specific names.
3. Lay out the stages and their timing. One message is rarely the whole campaign; three is typical — day 14, day 30, day 45. With a single send, a message that lands during someone's busiest week gets no second chance.
4. Write something different at each stage. The first one revives what was left behind, often by naming the document the person was last editing. The second reports what changed since they left. The third asks whether they need help and routes them to a person.
5. Pick the channels. Email is the default, and users who installed the app also get a push notification. Setting the timing inside a marketing automation tool, which fires messages when conditions are met, keeps anyone from having to pull the list by hand every week.
6. Attach the stopping rules. Anyone who comes back skips the remaining stages, and anyone who reaches the cancellation screen leaves this campaign for a save offer instead. Without those rules, people who already returned receive a message asking them to return.

Results are counted as the share who came back, not the share who opened the email. If 48 of the 400 teams on the list logged in at least once that month, the campaign did 12 percent. A 30 percent open rate with ten returns means the message was read and the product was not opened, so the thing to fix is the screen the email promised rather than the subject line.

Growth owns the design, but four seats are involved. Ravi writes the stages and the copy. Mia decides what counts as quiet and which behaviors are treated as signals. Theo makes sure the events behind those judgments are recorded — if creating a document is not logged anywhere, there is no basis for picking out quiet teams, which puts instrumentation weeks ahead of the campaign. Customers who arrived through a large contract skip automated email entirely and hear from Sofia directly.

Timing is counted from the last visit, which sets two boundaries. A team that signed up and never used the product is not a target: there is no memory to revive, and that case belongs to onboarding. At the other end, a message sent after a cancellation completes is not reactivation but winback, and with the account closed both the offer and the conditions change.

Send times follow the recipient's working hours. A collaborative document tool gets opened on weekday mornings, so Tuesday and Wednesday mornings work best, while a Friday afternoon message is buried by Monday.

The campaign itself gets revisited once a quarter. Copy left untouched for more than six months sees its return rate drift down: someone meeting the same email a second time does not open it, and whatever changed in the product since is missing from the text.

"Stage two went to 400 teams quiet for 30 days, and 48 of them came back."

A 12 percent return rate, and the open rate is not the result being reported.

"That's not reactivation, that's winback. The account is already cancelled."

Different audience, so the message and the terms have to be rebuilt.

"Someone who already came back got stage three. The exclusion rule is missing."

The stopping condition was never wired up.

At Pagedeck the campaign goes out automatically on Tuesday mornings. Last month the second message reached 380 teams quiet for 30 days and 41 came back, and 29 of those went quiet again within two weeks.

Looking at that table, Mia did not ask for new copy. She asked what the returning teams did once they were inside. If most of them opened the one document from the notification and left, the campaign did its job and the problem is downstream of it. The thing to fix is the first screen a long-absent team sees on return, not the email.

The most common belief is that sending more email brings more people back, since sends and returns look like they should move together. Repeating the same request to someone who has lost interest teaches them not to open it. A team that stretched three stages into six and watched the return rate go from 12 to 13 percent while unsubscribes went up fourfold has traded a point of recovery for a set of accounts it can no longer reach when something genuinely needs saying.

The other misreading is that the campaign is what brings people back. The return rate gets filed as a campaign result, which makes it look that way. All these messages do is knock on the door once; the reason to come inside has to be built into the product. The 29 teams of 41 that went quiet again in two weeks are the evidence. A team stuck at 12 percent that spends six months rewriting copy will be looking at the same number from the same place.