The Membership Site Automation Playbook
The highest-impact membership site automation ideas are not the welcome email and the receipt. Those matter, but the workflows that actually move revenue are dunning sequences for failed payments, timed win-back campaigns for cancelled members, and role-based access triggers that fire the moment a subscription lapses. Krom Automation handles every stage of this lifecycle inside WordPress, on a visual drag-and-drop canvas, with no per-task fees and no code required.
Most operators set up a welcome email and call their site automated. The result is a site that handles the happy path and falls apart the moment something goes wrong: a card declines, a member stops logging in, or a cancelled subscriber decides they want back in. Those three failure points are where the real money is.
This playbook covers the full lifecycle in order of when each workflow fires. Work through it in sequence. The onboarding section comes first because broken onboarding creates churn before it even shows up in your data.
Dunning comes fourth because it consistently delivers the highest return of any automation investment. Win-back comes last because you cannot run it until the others are working.
Browse the full Krom Automation feature list to see what triggers and actions are available before you build.
Quick Summary
This playbook covers eight automation stages for membership sites, from signup through post-cancellation win-back. The stages that recover the most revenue, in order, are: dunning (failed payment recovery), win-back (lapsed member re-engagement), and renewal warning sequences. Every workflow described here can be built in Krom Automation using native MemberPress, WooCommerce Subscriptions, or Easy Digital Downloads triggers, with no external automation platform required.
Stage 1: Signup and Access Granting
The trigger for your first workflow is the moment a member completes payment. For MemberPress sites, the MemberPress integration exposes signup, subscription renewal, expiry and payment triggers directly on the canvas. For subscription products built on WooCommerce, the WooCommerce Subscriptions integration covers the same events.
The access granting workflow should do three things in sequence, with no delays between them:
- Change the user’s WordPress role to match the membership tier they purchased
- Send a transactional receipt email using merge tags to pull in the plan name, price and next renewal date
- Add the member to the correct list or tag in your email platform so subsequent sequences fire correctly
The third step is where most sites leave money on the table. If the email tag is not applied at signup, every downstream sequence, including renewal reminders and dunning, either fires for the wrong people or does not fire at all.
Fix the tagging at the source and the rest of the lifecycle runs cleanly. The FluentCRM integration and the Mailchimp integration both support contact creation, tag application and list assignment from a single action node.
Stage 2: Onboarding Sequences
Onboarding is not a single email. It is a timed sequence that runs over the first 7 to 14 days and moves a new member from account creation to their first meaningful win inside your content.
Members who reach their first win in the first week are significantly more likely to renew. Members who do not are already churning, they just have not cancelled yet.
A solid onboarding sequence for most membership sites looks like this:
- Day 0, immediate: Welcome email with login link, a one-sentence explanation of where to start, and a link to the single most important piece of content
- Day 1: “Did you find it?” check-in with a link to the next logical step
- Day 3: Content spotlight email highlighting a benefit they have not used yet
- Day 7: Community invitation or Q&A prompt, designed to create a social connection before the first renewal
- Day 14: Progress email using merge tags to show activity where available, with a prompt to explore an underused feature
Each delay in this sequence is set using Krom Automation’s delay nodes, which support minutes, hours, days and weeks. Set the day 7 email to fire 7 days after the trigger, not 7 days after the previous email, so a member who joins on a Saturday still gets the email on the following Saturday regardless of whether they opened the earlier messages.
Onboarding is not about making members feel welcome. It is about getting them to their first result before the novelty wears off. Miss that window and no renewal sequence will save you.
For sites running courses through LearnDash or TutorLMS, enrollment and completion events are available as triggers. The LearnDash integration lets you fire a different onboarding branch based on which course a member enrolled in, so a beginner gets beginner content and an advanced member does not receive emails about basics they already know.
Stage 3: Content Dripping and Progress Nudges
Drip content automation serves two purposes: it controls access so members cannot binge and cancel, and it creates regular reasons to return to the site. Both reduce churn. A member who logged in three times last week is not cancelling next month.
The standard drip setup uses a Schedule trigger combined with a Post Status Changed action to move content from private to published on a set interval. For course-based sites, LearnDash lesson and section access can be unlocked based on enrollment date rather than calendar date, so every member gets the same relative experience regardless of when they joined.
Progress nudges are a separate workflow. They fire when a member has not logged in or completed a lesson within a set number of days.
The conditional branching in Krom Automation lets you split this into two paths: members who are actively progressing get a different email from members who have gone quiet. The quiet-member path should be warmer and lower pressure, because those members are already at risk.
If you want to understand what a good nudge sequence looks like in practice, the post on improving course completion rates through automation covers the exact timing and messaging logic.
Stage 4: Renewal Warnings
Renewal warnings prevent involuntary churn. A member whose card expired three months ago does not know their payment will fail until it does.
A warning 14 days out gives them time to update their details. A warning 3 days out catches the people who ignored the first one.
Two warnings is the minimum. Three is better. Suggested timing:
- 14 days before renewal: Friendly reminder with a link to billing settings. No urgency language.
- 3 days before renewal: Direct reminder to check payment details. One sentence on what they would lose if the payment fails.
- Day of renewal (if payment succeeds): Confirmation receipt with next renewal date. This email closes the loop and reduces support tickets asking “did my payment go through?”
The renewal confirmation email is sent by the payment workflow, not the warning workflow. Keep them as separate workflows so you can edit one without breaking the other. Use merge tags to pull the renewal date, plan name and amount into the email dynamically rather than writing a separate email for each plan.
Stage 5: Dunning, the Highest Revenue Impact Automation You Will Build
Dunning is the sequence that fires after a payment fails. It is the single highest-return automation on any membership site.
A single recovered payment from a member who would otherwise have lapsed is worth, on a $49/month membership, $588 in lifetime value if they stay for another year. A dunning sequence that recovers 30% of failed payments on a site with 200 members and a 3% monthly failure rate recovers roughly 6 payments per month, or $3,528 per year, from automation that runs without any manual effort.
Failed payments are not a billing problem. They are a communication problem.
The member usually wants to stay. They just need someone to tell them their card did not work.
The dunning sequence has three parts: immediate notification, a grace period with retry attempts, and final access revocation.
Immediate notification (Day 0): Send an email within minutes of the failed payment. Be factual and helpful, not punitive.
“Your payment didn’t go through” with a direct link to update the card. Most members fix it here if you catch them quickly.
Grace period emails (Days 3 and 7): Repeat the message with slightly more urgency. Day 7 should mention that access will be suspended if the payment is not resolved. This is not a threat, it is useful information that motivates action.
Access suspension (Day 10 or Day 14): Change the user’s role to revoke membership access. Send a final email confirming suspension and providing a reactivation link. Keep the account active, do not delete it.
A suspended account with intact data is recoverable. A deleted account is gone.
The detailed case for why this sequence matters and how to tune it is covered in the post on recovering failed subscription payments in WordPress. For WooCommerce Subscriptions users, the payment failure triggers are documented in the WooCommerce Subscriptions integration guide.
Stage 6: Cancellation and Offboarding
When a member cancels, most sites do nothing. That is a mistake. The cancellation event is your last moment to learn why someone left and your first moment to start the win-back clock.
A cancellation workflow should fire three actions in sequence:
- Send a confirmation email acknowledging the cancellation with a brief one-question survey link asking why they left
- Tag the contact as “cancelled” in your CRM or email platform so they exit active member sequences
- Schedule the first win-back email for 30 days later using a delay node
The survey link is optional but valuable. Even a 10% response rate gives you a signal about why members leave, which is more useful than any retention metric. The Fluent Forms integration lets you build a single-question form and route responses back into a workflow that tags contacts based on their answer.
Stage 7: Win-Back Automation for Lapsed Members
This is the section every competitor article skips. Churn prevention gets all the attention because it feels proactive. Win-back feels like giving up.
That framing is wrong. A cancelled member who was happy for 8 months before cancelling is one of your best reactivation prospects, far warmer than a cold lead who has never heard of you.
The win-back sequence starts 30 days after cancellation and runs for 90 days. Three emails is enough. More than that crosses into harassment.
| Day After Cancellation | Email Purpose | Offer |
|---|---|---|
| 30 | Check-in. No sales pressure. “We updated X since you left.” | None. Pure value. |
| 60 | Soft offer. A specific piece of new content they missed. | Optional: downgrade to a free tier if one exists |
| 90 | Reactivation offer. Time-limited, clear expiry. | 20% discount for the first 3 months back |
The 90-day email should have a hard deadline on the discount. “This offer expires in 7 days” is not manipulation, it is information that helps someone who is already interested decide to act. After 90 days with no reactivation, tag the contact as “lapsed, low priority” and move them out of any active sequences.
Do not delete the contact. Circumstances change.
If your membership platform supports a free or community tier, the 60-day email can offer a downgrade rather than a cancellation. A member paying $0 is not paying you, but they are still in your ecosystem and still a reactivation candidate. That path is worth more than a clean unsubscribe.
A cancelled member who was happy for months is a warmer prospect than someone who just discovered you. Win-back automation treats them accordingly instead of abandoning them at the door.
Stage 8: AI-Personalized Content Recommendations
None of the competing approaches to membership site automation cover this, but it is increasingly practical. Krom Automation includes AI actions in the free version, powered by your own API key with no markup on tokens. The AI Generate Text action can be used to build a basic content recommendation email that references a member’s recent activity.
The practical setup: a scheduled workflow fires weekly for each active member, pulls their last-accessed content via merge tags, sends that data to an AI prompt, and generates a short personalised email recommending what to read or watch next. This is not a recommendation engine replacing a full platform feature. It is a weekly email that feels personal rather than generic, and it takes about 2 hours to set up once.
For larger sites, this workflow should be tested carefully before enabling at scale. The post on what breaks when automation volume grows covers the performance considerations worth reviewing before running a scheduled workflow against hundreds of members simultaneously.
What Each Stage Costs You If You Skip It
| Stage | What You Lose Without It | Estimated Monthly Cost on a 200-Member Site |
|---|---|---|
| Signup and access granting | Manual role assignments, support tickets on missing access | 3 to 5 hours of admin time |
| Onboarding sequence | Higher early churn, members who never reach first value | 2 to 4 members lost before month 2 |
| Renewal warnings | Involuntary churn from expired cards | 1 to 3% of renewals failing silently |
| Dunning sequence | Failed payments that never recover | $500 to $2,000/month depending on plan price |
| Cancellation offboarding | No data on why members leave, no win-back clock started | Qualitative loss, no direct number |
| Win-back sequence | Lapsed members who would have returned with a prompt | 5 to 15% of cancellations recoverable with a simple sequence |
Building This in Krom Automation: What to Know
Every workflow in this playbook is buildable in Krom Automation. The free version covers signup triggers, role changes, email sending, delay scheduling and merge tags, which handles stages 1 through 3. Stages 4 through 8 use Pro triggers including MemberPress payment failure events, the Schedule trigger, and email platform integrations.
Pro plans start at $119/year for a single site and include all 80+ additional triggers and 60+ actions across 24 integrations. There is no per-task fee at any tier.
A site running 10,000 workflow executions per month pays the same as a site running 100. See the full plan comparison before deciding which tier fits your volume.
One practical note on timing: delays in Krom Automation run through Action Scheduler, which is the same background processing library used by WooCommerce. On low-traffic sites where WordPress Cron fires infrequently, a delay set to “3 days” may fire 3 days and a few hours later rather than exactly 72 hours. For most membership workflows this is fine.
For the dunning sequence where timing matters more, configuring a real server cron to replace WP-Cron is worth the 15 minutes it takes. The post on WordPress Cron reliability covers exactly why this happens and how to fix it.
If you are migrating existing automations from Zapier or another external platform, the incoming webhook receiver lets you accept payloads from any external service while you migrate workflows incrementally rather than all at once. The visual email builder in Pro also means you do not need a separate transactional email tool for the sequences described here.
The free version is available now with no trial period and no execution caps. Download Krom Automation from the WordPress.org plugin directory and build the first two stages before committing to a paid plan.
Also from wpRigel
Pollify is a Gutenberg-native poll, survey and quiz plugin for WordPress. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate interface to learn. It is a practical tool for membership sites that want to collect member feedback or run engagement polls without adding another standalone tool.
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search, navigate and run admin actions from anywhere in the dashboard without clicking through menus. It is the only command palette with real WooCommerce order, product and customer commands built in, which makes it useful on membership sites that also run a store.
Verdict: Where to Start and Who Should Wait
If your membership site is taking more than 4 hours per month on tasks that repeat on a schedule, the onboarding and dunning stages alone will return that time in the first month. Start with dunning if you already have active members.
Start with onboarding if you are launching. Every other stage adds value, but those two are where the revenue is.
If your site has fewer than 50 members and you are still validating the offer, the free version of Krom Automation with a basic welcome email and access-granting workflow is enough for now. Add the paid stages when you have enough members that a 3% monthly failure rate represents real money rather than a rounding error.
Do not wait until churn is visible in your dashboard. By the time cancellations show up in a report, the members in question have already mentally left. The automations that prevent churn need to be running before the first at-risk member stops opening your emails.
Compare Krom Automation plans and start building your membership lifecycle today.
Frequently Asked Questions
What is the first automation I should set up on a new membership site?
Set up access granting first. The moment a member pays, their role should update and their receipt should send automatically.
Without this, every new signup creates a manual task and a potential support ticket. Get this working before you build anything else.
Does Krom Automation work with MemberPress?
Yes. The MemberPress integration exposes signup, renewal, expiry and payment failure triggers directly in the workflow builder. You can build the full lifecycle described in this playbook, from welcome email to win-back sequence, using native MemberPress events without any custom code.
How many dunning emails should I send before revoking access?
Three emails over 10 to 14 days is the standard approach. Day 0 is immediate notification, Day 3 is a follow-up, and Day 7 warns that access will be suspended.
Revoke access on Day 10 or 14. Sending more than three emails before revoking access rarely improves recovery rates and increases the risk of spam complaints.
Can I automate win-back emails for members who cancelled months ago?
Yes, if you start the win-back clock at cancellation. The cleanest approach is to schedule the first win-back email as part of the cancellation workflow using a delay node set to 30 days. If your cancellation workflow did not include this step, you can run a one-time import or use the schedule trigger to send to a tagged segment of lapsed contacts.
Will these automations work on shared hosting, or do I need a VPS?
Most workflows run fine on shared hosting. The exception is high-volume scheduled workflows firing against hundreds of members simultaneously.
For those, configuring a real server cron rather than relying on WP-Cron matters more than the hosting tier. A properly configured server cron on shared hosting outperforms a misconfigured VPS for automation reliability.