A lot of brands land on Skio after a migration from another subscription app. The subscriptions move over, the customer portal looks new, and then a week later someone notices that the failed payment flow in Klaviyo hasn't sent a single email since the switch. Skio email marketing starts with that unglamorous part: making sure the right Skio events reach Klaviyo, and that every one of them has a flow behind it.
This guide walks through the Skio events we use, the flow on each, how to divide work between Skio's own messages and Klaviyo, and what to check after a migration. If you want the bigger picture on subscription retention first, start with our subscription email marketing guide.
Find out what Skio actually sends
With the Skio integration connected, subscription activity appears in Klaviyo as metrics, and subscriber details like status or next order date show up as profile properties. The exact list depends on your Skio configuration and can change as Skio updates the integration. So we won't pretend to know your event names. Check them in Klaviyo under metrics, and cross-check with the Skio help docs.
In general you are looking for events that cover these moments:
- A new subscription is created
- An order is coming up
- A payment fails
- An order is skipped
- A subscription is cancelled
Then pick a test profile with an active Skio subscription and look at its properties. If the product, the next order date or the cancellation reason are there, your flows can use them. If they're not, you write more generic copy or ask Skio whether that data can be passed through.
The Skio email marketing flows we build
| Event | Flow | Goal | Timing |
|---|---|---|---|
| Subscription created | Subscription welcome | Show what ships when and how to manage it | Right away, plus one product email a few days later |
| Upcoming order | Order reminder | No surprise charges, easy skip or swap | 3 to 5 days before the order |
| Payment failed | Failed payment | Get payment details updated before the order is lost | Within hours, then follow-ups over about a week |
| Order skipped | Skip follow-up | Suggest a swap or a longer interval | 1 day after the skip |
| Subscription cancelled | Cancellation save | Win back people who left for a fixable reason | Within 24 hours |
| Subscription cancelled | Win-back | Restart churned subscriptions | From about 3 weeks after the cancel, over 1 to 2 months |
Order reminder
The order reminder is where most subscription brands either earn trust or lose it. Show the date, the amount and the products in the first screen. Then make skipping and swapping obvious.
Skio puts a lot of weight on making the customer portal easy to get into, and depending on your setup subscribers may be able to log in without a password. If that's the case for you, use it. A reminder that links into the portal in one tap converts far better than one that sends people to a login page they've forgotten the password for. Check how your Skio portal links work before you write the CTA.
Decide whether Skio or Klaviyo sends this reminder. Skio can send its own notifications, by email and possibly by text, so map that out first.
Failed payment
Skio handles payment retries on its side. Your job in Klaviyo is the human part: a short, friendly email within a few hours asking the subscriber to update their card, with a direct link. Then two or three follow-ups. Each one should check first whether the payment went through in the meantime, so you don't chase people who already fixed it.
Keep the tone calm. Most failed payments are expired or replaced cards. Nobody needs an email that reads like a collection notice.
Skip follow-up and subscription welcome
After a skip, send one email. Suggest a longer interval if they have too much product, or a different variant if they might be bored. Don't stretch it into a sequence.
The welcome is the reverse. It sets the tone for the whole subscription, so explain clearly what happens next and where the controls are. A second email a few days later can cover how to use the product and what results to expect, in the brand's real words and numbers.
Cancellation save and win-back
Skio has cancel flow options in the portal, where subscribers can see alternatives like pausing or swapping before they confirm. Look at what yours shows. The save email should pick up where the portal stops, with a personal question and a different solution, not the same discount they just clicked past.
If the cancel reason reaches Klaviyo, split the flow on it. Then start the win-back a few weeks later. Our win-back flow guide has the detail on offers and spacing.
Skio messages vs Klaviyo: avoid sending everything twice
Skio has its own customer notifications, and SMS plays a bigger role there than in many subscription apps. Depending on your setup, subscribers might be able to manage parts of their subscription by replying to a text. Skio's docs describe what is available on your plan, and that's the source to trust here, since features change.
For email, our default split looks like this:
| Message | Usually sent by | Why |
|---|---|---|
| Order reminder email | Klaviyo | Brand design, testing, segments |
| Failed payment email | Klaviyo | Personal tone, split by customer value |
| Cancellation follow-up | Klaviyo | Can branch on the cancel reason |
| Subscription management by text | Skio, if you use it | That logic lives inside Skio |
| Login and account messages | Skio or Shopify | Leave these alone |
If you also run SMS through Klaviyo, write down which texts come from Skio and which from Klaviyo. Two texts for one order feel like spam, even when both are correct. Our SMS marketing guide covers the Klaviyo side.
Once your list is done, switch off every Skio email notification that a Klaviyo flow now replaces. Then trigger each event with a test subscription and count what lands in the inbox.
After a migration to Skio
This is where we see the most broken setups. When a brand moves to Skio from another app, the old app stops sending events, and every flow, segment and filter built on those events quietly goes dead. Nothing errors. The emails just stop.
- List every flow triggered by a metric from the old subscription app.
- Rebuild each trigger on the matching Skio metric.
- Update segments and flow filters that use the old app's properties, like subscription status.
- Keep the old flows paused, not deleted, until the new ones have sent for a couple of weeks.
- Check campaign exclusions, so active subscribers still don't get first-order offers.
We run this audit for subscription brands as part of our subscription marketing service, usually in the first week.
Questions we get a lot
Does Skio integrate with Klaviyo?
Yes. Skio has a Klaviyo integration that sends subscription events and subscriber properties into Klaviyo. Which events and properties arrive depends on your Skio setup, so check the metrics list in your Klaviyo account and the Skio docs before building flows.
What happens to my Klaviyo flows when I move from Recharge to Skio?
Flows triggered by Recharge metrics stop firing once Recharge stops sending events. You need to rebuild those triggers on the Skio metrics, update segments and flow filters that use Recharge properties, and test everything with a real Skio test subscription.
Should Skio or Klaviyo send SMS to subscribers?
Decide per message type. Skio offers SMS features around subscription management, so check which ones are active in your account. If Klaviyo also sends subscription texts, map out who sends what so subscribers don't get two texts for the same order.
Which Skio events matter most for retention?
The upcoming order, a failed payment and a cancellation. Those three decide most of your churn. Build those flows first, then add skip follow-ups and the subscription welcome.