Recover failed coaching payments before clients churn
Each morning, WebRun checks Paperbell and Stripe for any failed or declined payments from the last 24 hours, logs the affected clients and amounts, and drafts a polite, on-brand recovery email for each one in Gmail so you can follow up and resolve issues before anyone loses programme access.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically follow up on failed coaching payments?
WebRun checks Paperbell and Stripe every morning for failed or declined payments, notes the decline reason for each affected client, and drafts a polite recovery email in Gmail with a link to update their payment method. Every draft waits for your approval before reaching the client, protecting the relationship while recovering revenue quickly.
- Failed payments are caught and acted on within 24 hours, not weeks
- Clients get a polite, on-brand recovery message before losing programme access
- Revenue recovery happens without awkward manual conversations
Built for life coaches · business coaches · coaching programme sellers · solo coaching practices
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
paperbell.comin a real browser with your saved login - no setup, no API keys. -
1
Paperbell - find failed payment records
paperbell.com
WebRun opens Paperbell to find failed payment records. - Open Paperbell and go to the Billing or Payments section
- Filter for payments that failed or were declined in the last 24 hours
- Note the client name, programme, amount, and failure date for each
Done when Every failed payment from the last 24 hours is listed with the client and amount details.
-
2
Stripe - confirm decline reason and amount
stripe.com How to Automate Stripe
WebRun opens Stripe to confirm decline reason and amount. - Open Stripe and find the corresponding failed charge for each client
- Capture the decline reason code, such as insufficient funds or card expired
- Note whether a retry has already been attempted automatically
Done when Each failed payment has a confirmed decline reason from Stripe.
-
3
Gmail - draft recovery emails for review
gmail.com How to Automate Gmail
WebRun opens Gmail to draft recovery emails for review. - Draft a polite, non-alarming recovery email for each affected client mentioning the payment issue without specifying the decline reason
- Include a direct link to update their payment method in Paperbell
- Save each message as a Gmail draft, not sent, for your review
Done when A recovery draft sits in Gmail for every client with a failed payment, ready for your review 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 email clients about payment issues automatically?
No. Every recovery message is saved as a Gmail draft for your review. Nothing is sent to a client until you approve it, so you control the tone and timing of sensitive financial communications.
Does it share the Stripe decline reason with the client?
No. The draft uses a neutral, non-alarming tone and does not expose technical decline codes. It simply asks the client to update their payment details via a direct Paperbell link.
What if Stripe retries the payment and it succeeds before I send the email?
WebRun reads the live payment status each morning. If a retry has already succeeded, the client is removed from that day's recovery list and no draft is created for them.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.