Catch at-risk merchants before they close their accounts
Every Monday, WebRun opens IRIS CRM, checks each active merchant's processing volume trend, dormancy flag, and recent support ticket history, identifies accounts showing attrition signals, posts a save-the-merchant worklist to Slack, and adds flagged merchants to a re-engagement Mailchimp segment for your team to activate.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically detect and act on merchant attrition signals?
WebRun scans IRIS CRM every Monday for merchants with declining volume, dormant accounts, or unresolved support escalations, and posts a prioritized at-risk worklist to Slack. Flagged merchants are also added to a Mailchimp re-engagement segment, held as a draft until your team activates it.
- At-risk merchants are spotted weeks before they close their account
- Relationship managers get a weekly prioritized save list in Slack
- Re-engagement campaigns are pre-built and ready to activate in Mailchimp
Built for payment ISOs · merchant relationship managers · portfolio managers · ISO retention 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
iriscrm.comin a real browser with your saved login - no setup, no API keys. -
1
IRIS CRM - detect attrition signals across merchant portfolio
WebRun opens IRIS CRM to detect attrition signals across merchant portfolio. - Open IRIS CRM and review each active merchant's volume trend over the last three months
- Flag merchants whose processing volume dropped more than 20% month over month
- Also flag accounts with no transactions in 30 or more days, or with two or more unresolved support tickets
Done when All merchants showing attrition signals are identified with their risk reason.
-
2
Slack - post save-the-merchant worklist
WebRun opens Slack to post save-the-merchant worklist. - Post the at-risk worklist to the retention Slack channel, sorted by risk level
- Include merchant name, assigned agent, risk reason, volume change, and last transaction date
- Tag the assigned agent for each merchant so they are alerted directly
Done when The relationship team has this week's at-risk merchant list in Slack.
-
3
Mailchimp - add flagged merchants to re-engagement segment
WebRun opens Mailchimp to add flagged merchants to re-engagement segment. - Add each flagged merchant's contact email to the re-engagement Mailchimp segment
- Tag each contact with the attrition reason (volume drop, dormancy, or support issues)
- Leave the segment in draft so your team can review and activate the campaign
Done when Flagged merchant contacts are added to the Mailchimp re-engagement segment, ready for review.
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 re-engagement emails to merchants automatically?
No. Flagged merchants are added to a Mailchimp segment that stays in draft until your team reviews it and activates the campaign. No email goes out on its own.
What counts as an attrition signal?
A volume drop of more than 20% month over month, 30 or more days of dormancy, or two or more unresolved support tickets. You can adjust any of these thresholds during setup.
How far back does it look for volume trends?
It compares the last three months of processing volume in IRIS CRM to identify meaningful decline trends rather than one-off slow periods.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.