Automated Frontegg Inactive Tenant Chasing
Every Monday, WebRun opens Frontegg, checks every tenant's last login activity, posts the full list of tenants inactive for 30 days or more to Telegram, and texts your customer success lead a shortlist of the longest inactive tenants to follow up with directly.
How do I catch inactive Frontegg tenants before they churn?
WebRun checks every Frontegg tenant's last login activity each Monday, posts the full list of tenants inactive for 30 days or more to Telegram, and texts your customer success lead the longest inactive ones to follow up with. It never suspends a tenant itself, so every account decision stays with your team.
- Inactive tenants get flagged weekly instead of discovered at renewal
- The longest inactive tenants reach your CS lead directly
- Reactivated tenants drop off the list automatically
Built for customer success teams · B2B SaaS companies · product teams · growth teams
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
frontegg.comin a real browser with your saved login - no setup, no API keys. -
1
Frontegg - check tenant login activity
frontegg.com
WebRun opens Frontegg to check tenant login activity. - Open Frontegg and list every tenant
- Check the last login date for each tenant's users
- Flag any tenant with no login in 30 days or more
Done when Every tenant's last login activity has been checked.
-
2
Telegram - post the inactive tenant list
telegram.org
WebRun opens Telegram to post the inactive tenant list. - Post the full inactive tenant list to Telegram
- Sort by longest inactive first
- Note the plan tier for each tenant
Done when Telegram has this week's full inactive tenant list.
-
3
Twilio - text your customer success lead
twilio.com
WebRun opens Twilio to text your customer success lead. - Text your customer success lead the 3 longest inactive tenants
- Name the tenant and days since last login
- Skip the text entirely if no tenant is newly inactive
Done when Your customer success lead has been texted the top inactive tenants.
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
Does WebRun suspend or deactivate a tenant?
No. WebRun only reports who is inactive. Suspending an account or changing a tenant's status is left for your team to decide and do.
Does it contact the inactive tenant directly?
No. It only messages your own customer success lead internally. WebRun never emails or messages a customer without your team's involvement.
What happens once a tenant logs in again?
It checks Frontegg's live activity data each Monday, so a tenant that logs back in drops off the inactive list automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.