Automated Gym Dunning
Every morning, WebRun checks PushPress and Stripe for failed membership dues, builds a prioritized dunning worklist, drafts a card-update text for each member, and posts the list to Slack so staff can review and send before the membership lapses.
How do I automatically follow up on failed gym membership payments?
WebRun checks PushPress and Stripe every morning for failed membership dues, confirms the decline reason for each charge, and drafts a card-update text for every affected member. Staff review and send each draft from the Slack dunning worklist, recovering dues the same day without automating sensitive billing messages.
- Failed dues are caught and actioned the same morning they occur
- Staff see a decline-reason-sorted worklist in Slack every day
- No billing message goes to a member without staff sign-off
Built for CrossFit gym owners · gym billing staff · box operators · functional fitness studios
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.pushpress.comin a real browser with your saved login - no setup, no API keys. -
1
PushPress - find failed payments
WebRun opens PushPress to find failed payments. - Open PushPress and filter members with a failed or past-due payment status
- Capture each member's name, amount owed, and days since failure
- Note their membership tier and whether this is a first or repeat failure
Done when All members with a failed payment are listed with amount and failure date.
-
2
Stripe - confirm failure reason
WebRun opens Stripe to confirm failure reason. - Look up each failed charge in Stripe to confirm the decline reason
- Identify whether the issue is an expired card, insufficient funds, or another code
- Draft a short card-update text for each member tailored to the decline type
- Save every text as a draft for staff review before sending
Done when Each failed payment has a confirmed decline reason and a reviewed draft text ready.
-
3
Slack - post dunning worklist
WebRun opens Slack to post dunning worklist. - Post the dunning worklist to the billing channel sorted by amount owed
- Include each member's name, amount, decline reason, and draft text status
- Flag repeat failures and memberships more than seven days past due
Done when Staff have today's dunning worklist in Slack with draft texts ready to approve and send.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it text members about failed payments without staff approval?
No. WebRun drafts every card-update text and queues it for staff review. No message goes to a member until a staff member approves it, keeping all sensitive billing communication under human control.
How does it know why the payment failed?
It reads the decline code from Stripe for each failed charge, such as expired card, insufficient funds, or do-not-honor, and uses that reason to tailor the draft text sent to the member.
What if the member updates their card before staff review the draft?
Payment status is read live from PushPress each morning. If a member self-resolves overnight, they will not appear on the next day's worklist and their draft can be discarded.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.