Every subscription goes through a series of moments — a welcome, a renewal, maybe a failed payment, maybe a cancellation. The Subscription Email Sequence automatically sends the right email at each of these moments, so your customers always know what's happening with their subscription — without you writing a single email by hand.
This article covers where to find these emails, how the Default / Shared / Customized system works, how to edit an email, how to add optional Follow-ups, and what each subscription event actually means.
1. Where to Find It
Open the product's settings menu and click Email. At the top of the page you'll see two tabs: Cart Abandonment and Subscription Email Sequence. Click Subscription Email Sequence.

Product settings → Email → Subscription Email Sequence
At the top, a note explains exactly how this page works:
"Each event below sends one email to your customer straight away. Edit any of them to use your own wording for this product, or turn one off to stop it being sent."
2. The Full List of Subscription Events
Every row under SUBSCRIPTION EVENTS represents one moment in a subscription's life. All of them are currently set to "Sent once, immediately."


Events Breakdown
| Event | Fires when… |
|---|---|
| Welcome (no trial) DEFAULT | A customer subscribes to a plan with no free trial. |
| Welcome (with trial) SHARED | A customer starts a free trial. |
| Trial Ending SHARED | A free trial is about to end (no Follow-ups option on this one). |
| Trial Converted SHARED | A free trial successfully converts into a paid subscription. |
| Renewal Successful DEFAULT | A recurring payment is charged successfully. |
| Cancellation SHARED | The customer requests to cancel. |
| Cancellation Confirmed DEFAULT | The cancellation has been fully processed. |
| Payment Failed SHARED | A recurring charge is declined. |
| Paused SHARED | The subscription is put on hold. |
| Resumed SHARED | A paused subscription is started again. |
| Billing Extended DEFAULT | The billing period is extended (e.g. a grace period after a failed payment). |
| Expired DEFAULT | The subscription reaches the end of its term. |
| Payment Receipt DEFAULT | A successful payment is made (sent as a receipt). |
| Refund DEFAULT | A payment on the subscription is refunded. |
3. Understanding the Badges: Default, Shared, and Customized
Next to each event name you'll see one of three badges. These tell you where the current wording is coming from:
| Badge | Meaning |
|---|---|
| DEFAULT | This product is using FlexiFunnels' original, unedited email — nobody has customized it at any level. |
| SHARED | This product is using your account-wide version of the email — the one you (or someone on your team) customized in Settings, which applies to every product that hasn't been given its own override. |
| CUSTOMIZED | Seen on the account-level Settings page — this event's account-wide default has been edited away from FlexiFunnels' original wording. |
- FlexiFunnels' built-in default — used everywhere until you change something.
- Your account-wide version — edited once in Settings → Email → Subscription Product Email, applies to every product (shown as SHARED on the product page).
- A product-specific override — edited directly on this product's Email page. The product page note says it plainly: "Anything you don't change here uses your shared copy from Settings."
4. Editing an Email


The Edit window — subject, rich text body, live preview, and merge tags
The Edit window title reminds you: "Saving here applies to this product only." It contains:
- Subject — the email's subject line, pre-filled with a default like "Welcome to {{product_name}} — your subscription is active."
- Body — a rich text editor (bold, underline, italic, strikethrough, font size, text color, lists, alignment, links, images, expand, and an HTML code view) with a live preview of exactly how the email will look.
- Merge Tags — a reference list of placeholders you can insert into the subject or body, which get replaced with the customer's real data when the email sends.
Available merge tags include:
{{name}} {{product_name}} {{price}} {{amount}} {{next_charge_date}} {{trial_end_date}} {{trial_days}} {{support_url}} {{invoice_due_date}} {{due_since_date}} {{days_past_due}} {{pay_now_url}}
{{trial_end_date}} is useful in a trial email, while {{days_past_due}} belongs in a payment-failed email. Use whichever tags are relevant to the specific event you're editing.5. Adding Follow-up Emails
Most events (all except Trial Ending) have a Follow-ups button. This lets you queue up one or more extra emails to send some time after the main event email.

The Follow-ups window starts empty — click Add first follow-up to create one

Configure when the follow-up sends and what it says
Each follow-up step has:
- Timeline (left panel) — a numbered list of your follow-up steps for this event. Click + Add follow-up to add more steps.
- Send on — a number.
- Unit — e.g. days.
- Timing — e.g. After this email is sent.
- Subject and Body — the follow-up email's own content, with the same rich text editor as the main email.
- Remove — deletes this follow-up step.
6. Editing the Account-Wide Defaults
On the product's Email page, click Edit default emails in Settings (top-right) to jump to the account-wide version. This takes you to Settings → Email Settings, on the Subscription Product Email tab.


Settings → Email Settings → Subscription Product Email — the account-wide defaults used by every product
The note here explains it clearly: "These are default emails from FlexiFunnels. We use them for your subscription products — or you can edit any of them to make your own version. Turning an email off means it won't be sent to your customers."
Any event you've customized here shows a CUSTOMIZED badge along with a Reset to default button, which reverts that email back to FlexiFunnels' original wording.
Common Use Cases
Common Situations & Quick Fixes
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article