Automated Mangomint Package Balance Report
Every Monday, WebRun opens Mangomint, pulls every client with an active package or treatment series, works out sessions completed versus sessions remaining and the days left before any expiry date, logs the full breakdown to Google Sheets, and posts your front desk a Slack summary of who is running low.
How do I track how many laser hair removal sessions each client has left?
WebRun opens Mangomint every Monday and pulls every client with an active laser hair removal package or treatment series. It calculates sessions completed against sessions remaining for each one, logs the full breakdown to Google Sheets, and posts your front desk a Slack summary of who is running low, so no client's package quietly runs out unnoticed.
- Front desk always knows exactly how many sessions each client has left
- Clients running low on their package surface automatically every week
- A dated Google Sheets history shows balance trends without manual entry
Built for laser hair removal studios · multi location aesthetics clinics · front desk and studio managers · medical spas selling laser packages
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.mangomint.comin a real browser with your saved login - no setup, no API keys. -
1
Mangomint - pull active packages and series
mangomint.com
WebRun opens Mangomint to pull active packages and series. - Open Mangomint and list every client with an active package or treatment series
- For each one, work out sessions completed, sessions remaining, and any expiry date on file
- Note the treatment area and plan type for context
Done when Every active package and series has a sessions completed and sessions remaining count.
-
2
Google Sheets - log sessions completed and remaining
google.com
WebRun opens Google Sheets to log sessions completed and remaining. - Open the package tracking sheet and update each client's row with sessions completed and sessions remaining
- Add a running low flag for anyone with two or fewer sessions left
- Keep a dated history so front desk can see how balances changed week over week
Done when Every client's package balance is logged in Google Sheets with a running low flag where it applies.
-
3
Slack - flag clients running low
slack.com
WebRun opens Slack to flag clients running low. - Post a summary of how many clients are running low on sessions
- List the running low clients with their treatment area and sessions remaining
- Link to the full Google Sheets ledger for anyone who wants the complete list
Done when Front desk has this week's running low list in Slack with a link to the full ledger.
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 this report ever contact clients directly?
No. This workflow only builds an internal ledger and a Slack summary for your team. It does not message any client. Pair it with a reminder workflow if you want low balance clients nudged automatically.
How does it decide who is running low?
It flags anyone with two or fewer sessions remaining in an active package or treatment series, based on the sessions completed count in Mangomint, so front desk can prioritize outreach.
Can it track packages that cover more than one treatment area?
Yes. It logs each package or series separately by treatment area, so a client with both underarm and leg packages shows a distinct balance for each.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.