Flag client portal inactivity in Suralink before your engagement falls behind
Every morning, WebRun opens Suralink and reviews the last activity date for each client portal across active engagements. Any client with no login or upload activity in the past 5 days is flagged, logged in an Airtable inactivity tracker, and surfaced in a Slack alert so your team can follow up before the engagement falls behind.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically flag inactive clients in my Suralink engagement portals?
Every morning WebRun opens Suralink and checks when each client last logged in or uploaded a document. Any client inactive for 5 or more days is logged in an Airtable tracker and surfaced in a Slack alert ranked by days inactive, so your team can prioritize follow-up before portal inactivity puts the engagement schedule at risk.
- Inactive clients surfaced in Slack every morning ranked by days without activity
- Running inactivity log in Airtable across all active engagements
- Clients who return to activity cleared from the tracker automatically
Built for audit managers · CPA firms · engagement partners · assurance 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
app.suralink.comin a real browser with your saved login - no setup, no API keys. -
1
Suralink - check client portal activity dates
WebRun opens Suralink to check client portal activity dates. - Open Suralink and list all active engagements with client portals
- For each client portal, find the date of the most recent login or document upload
- Flag any client with no activity in the past 5 days
- Also flag any client with open requests and no activity in the past 3 days during the final week before a deadline
Done when Every inactive client is identified with the number of days since their last activity and the count of open requests remaining.
-
2
Airtable - log inactive clients
WebRun opens Airtable to log inactive clients. - Open the client inactivity tracking Airtable base
- Add or update a record for each inactive client with last activity date, days inactive, and open request count
- Mark clients who have returned to activity since the previous run as resolved
Done when The Airtable tracker reflects current inactivity status for all flagged clients.
-
3
Slack - post inactivity alert
WebRun opens Slack to post inactivity alert. - Post a concise inactivity alert to the audit team Slack channel
- Sort by days inactive descending so the most disengaged clients appear first
- Include the engagement name, days inactive, and count of outstanding requests for each client
Done when The team has today's client inactivity alert in Slack.
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 send a message to inactive clients automatically?
No. WebRun only flags inactivity for your team internally via Slack and Airtable. Any outreach to the client is a decision your team makes after reviewing the report.
Can the inactivity threshold be changed from 5 days?
Yes. During setup you specify the number of days of inactivity that triggers a flag, so you can set a tighter threshold during busy season or a looser one for early-stage engagements.
What if a client logs in after the morning run?
The flag will clear on the next morning's run when WebRun reads the updated activity date from Suralink. The Airtable record is marked resolved automatically.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.