Sarbacane becomes Positive User

Subscription expiry workflow

Increase subscription renewals with a multichannel reminder sequence before and after expiry.

Goal
Encourage repeat sales
Improve retention and fight churn
Improve monetization, revenue and lifetime value
Industries
B2B
B2C
SaaS
Tourism
Web Hosting
Channels
Automation
SMS
Web Push Notifications
Mobile Marketing
Email

Description

Most subscriptions that lapse do not lapse because the customer wanted to leave. They lapse because no one reminded them at the right moment. This use case closes that gap with a three-touchpoint sequence: five days before expiry, on the expiry date itself, and one day after if the subscription has not been renewed. At each touchpoint, the system checks what channels are available for that specific contact and chooses the best one: mobile push for app users, email as the default fallback, SMS if email is not available. Every message checks whether the subscription is still active before sending, so no one receives a renewal reminder for something they have already renewed. The final touchpoint, sent one day after expiry, is a win-back attempt rather than a routine reminder, with framing that focuses on what the contact is about to lose rather than what they owe.

Implementation Effort
Impact on a goal

Take it on the next level...

Creative Assets like (ready HTML)
Recommended Data Structure
Code Snippets
Cheat Sheet
Automation templates
Unlock the full use-case

Unlock 40 Use Cases

Thank you, your message has been sent!
There was an error sending the form!

Outcome

Higher renewal rates through precisely timed multichannel touchpoints
Reduced churn by reaching each contact on their best available channel
Improved lifetime value with consistent renewal engagement at key expiry moments

How it works in practice

A subscriber has a subscription expiry date set in their profile. Five days before that date, the automation fires. The system looks at what is available for that contact: do they have a mobile device with push enabled? If yes, a push notification goes out. If not, is email available? If yes, an email goes out. If not, SMS. The contact receives their first renewal reminder through whatever channel makes the most sense for them. On the expiry date itself, the flow runs again. Before sending anything, it checks whether the subscription is still expired. If the contact renewed after the first reminder, they receive nothing. If not, another message goes through the best available channel, this time with more urgency. One day after expiry, if the subscription has still not been renewed, a final message goes out. The tone shifts: this is not a reminder, it is a win-back. The message emphasizes what access has been lost and how easy it is to restore it. After this third touchpoint, the flow ends.

1

First reminder: 5 days before expiry: The automation triggers 5 days before the subscription_expiry_date. The system evaluates available channels in priority order: mobile push if consent and device token exist, then email, then SMS. The message focuses on prevention: the subscription is ending soon and renewal is easy.

2

Second reminder: day of expiry: On the expiry date, the system first checks whether subscription_status is still expired. If the contact has already renewed, no message is sent. If not, an urgent reminder goes out through the best available channel emphasizing that access ends today.

3

Final win-back: 1 day after expiry: If the subscription has expired without renewal, a final message is sent 1 day after expiry. The tone shifts from reminder to win-back: the message focuses on what the contact has lost and how easy it is to restore access. The system again uses the best available channel for this contact.

4

Channel selection logic: At every touchpoint, the system evaluates channels in the same order: mobile push first if Consent push is TRUE and a device token exists, then email if Consent email is TRUE, then SMS if Consent SMS is TRUE and a phone number is available. If no channel is available, no message is sent and the contact is excluded from that touchpoint.

How to implement it?

Implementing use case automation involves several key steps and tools. Here's comprehensive ressources to get you started:

Used modules

Automations

Marketing on a new level with a beautiful visual, drag & drop creator.

On date & time
Push notification
Send Email Campaign
Send SMS campaign
Filters

Email Marketing

Send personalized emails that resonate with your users at the perfect moment.

SMS Messages

Automate SMS delivery based on user actions or specific conditions.

Mobile Push Notifications

Deliver personalized notifications to users of your mobile app.

Prerequisities

Set up and connect your sending domain for email delivery.
Mobile SDK integration (for Flutter)
Connection to your SMS provider

Recommanded data structure

Contact Attributes

A contact attribute is a data field stored on the contact's profile, used for segmentation, personalization, reporting, and automation.

Attribute name
Attribute type
email
(standard) string
phone_number
(standard) string
FCM key
(standard) string
Consent email
(custom) boolean
Consent SMS
(custom) boolean
Subscription active
(custom) boolean
checks if the subscription is active or not
Subscription date end
(custom) date
date on which the contact’s active subscription is set to expire

Product Attributes

A product attribute is a data field describing a property of a product stored on the product profile.

Attribute name
Attribute type
Name
string
Product URL
string
Image URL
string

Product Events

A product event tracks a contact's interaction with a specific product. First occurrence is used for anniversary calculation.

Product Event name
Customer path
Update method
Add to cart
added the product to the cart
JS SDK
Purchase
order completed with the product
API
Customer review

Trusted by fast-growing teams

“Thanks to Positive User, we not only significantly expanded our audience base, but also streamlined communication and automated many tasks that previously consumed a lot of time. This tool truly supports our sales and digital strategy.”

Somfy, Equipo de E-commerce de Somfy
Read the full customer story

Turn this use case into action

Start from a proven use case designed to help you engage faster, with relevance and impact.

More ways to engage your audience

Reward double opt-in with a discount

Compliant two-step opt-ins that deliver an instant discount and lift confirmation rates.

Announce new features in-app

In-app messages that surface new features the moment mobile users open the app.

Trigger sales actions after subscription end

Automated deal and task creation that puts sales on every expired subscription within days.