Automated iClassPro Tuition Autopay Alerts
Every morning, WebRun opens iClassPro, finds every tuition autopay charge that failed overnight, logs the family, amount, and failure reason to a Google Sheet, and drafts a short payment update text for each family in Twilio so staff can review and send it before the balance grows further.
How do I catch and follow up on failed ninja gym tuition autopay charges?
WebRun checks iClassPro every morning for tuition autopay charges that failed overnight, logs the family, amount, and failure reason to a Google Sheet, and drafts a short payment update text for each family in Twilio. Staff approve and send the texts, so declined cards get caught and followed up before balances pile up.
- Failed charges are caught the same morning they happen
- Every failure is logged and tracked through to resolution
- No payment text goes out without staff reviewing it first
Built for ninja warrior gyms · obstacle training gyms · gym billing staff · front desk managers
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.iclasspro.comin a real browser with your saved login - no setup, no API keys. -
1
iClassPro - find failed autopay charges
iclasspro.com
WebRun opens iClassPro to find failed autopay charges. - Open iClassPro and check the billing section for autopay charges that failed overnight
- Capture the family, student, amount due, and the failure reason for each
- Skip any account already contacted in the past 3 days
Done when Every failed autopay charge is listed with amount, reason, and family contact.
-
2
Twilio - draft a payment update text for each family
twilio.com
WebRun opens Twilio to draft a payment update text for each family. - Draft a short, polite payment update text for each family naming the amount and asking them to update their card
- Include a direct link to update payment on file
- Save each text as a draft. Do not send until staff approves it
Done when A draft payment update text is queued in Twilio for every failed charge.
-
3
Google Sheets - log the failure for tracking
google.com
WebRun opens Google Sheets to log the failure for tracking. - Append a row to the failed payment log with the date, family, amount, and failure reason
- Mark the follow up status as pending until staff confirms the text was sent
- Update the status to resolved once the payment succeeds on a later run
Done when Every failed charge is recorded in the tracking sheet with a follow up status.
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 families about a declined card without staff checking first?
No. WebRun drafts the payment update text in Twilio and leaves it unsent. Staff review and send it, so the message and timing always get a human check.
How does it avoid contacting the same family twice?
It skips any account already contacted in the past 3 days, so a family does not get repeated texts while staff are still following up.
What happens once the family updates their card?
WebRun reads the live billing status in iClassPro each morning, so once the payment succeeds the account is marked resolved in the tracking sheet and no further text is drafted.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.