IRIS CRM Automated Application Approval Routing
When a merchant application moves to Pending Approval in IRIS CRM, WebRun reads the risk tier, processing volume estimate, and business type, looks up the correct approver based on your routing rules, and sends them a Slack message with a complete application summary and a link to the IRIS CRM record. For high-volume accounts, it also checks the applicant's Stripe payment history as additional context.
How do I automatically route merchant application approvals to the right reviewer?
WebRun monitors IRIS CRM for applications moving to Pending Approval, reads the risk tier and volume estimate, applies your routing rules to identify the correct reviewer, and sends them a complete Slack summary with a direct link to the record. For high-volume accounts it also pulls Stripe payment history for added context.
- Every pending application reaches the right reviewer within minutes, not hours
- Approvers get full context including risk tier and Stripe history in one Slack message
- No application waits in a queue because the wrong person was notified
Built for payment ISOs · underwriting teams · ISO managers · merchant services operations
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 - read application details and risk tier
iriscrm.com
WebRun opens IRIS CRM to read application details and risk tier. - Open IRIS CRM and read the newly pending application's merchant type, estimated monthly volume, risk tier, and assigned agent
- Apply your routing rules to identify the correct approver (e.g., deals over $50,000 go to the senior underwriter, standard deals go to the team lead)
- Collect all supporting details the approver needs: business name, SIC code, years in business, and any flagged notes
Done when The correct approver is identified and all application details are captured.
-
2
Stripe - check applicant payment history for high-volume accounts
stripe.com
WebRun opens Stripe to check applicant payment history for high-volume accounts. - For applications with an estimated monthly volume over your high-value threshold, open Stripe and look up the applicant's existing account if one exists
- Note their historical dispute rate, processing volume trend, and account standing
- Add these data points to the approval context summary
Done when Stripe payment history is added to the approval context for high-volume applicants.
-
3
Slack - send approval request to the right reviewer
slack.com
WebRun opens Slack to send approval request to the right reviewer. - Send the identified approver a Slack message with the full application summary
- Include merchant name, volume estimate, risk tier, SIC code, Stripe history if applicable, and a direct link to the IRIS CRM record
- Ask them to approve or decline in IRIS CRM and include your target turnaround time
Done when The approver has a complete application summary in Slack with a direct IRIS CRM link.
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 it approve or decline applications automatically?
No. WebRun only routes the approval request and provides context. All approvals and declines are made by a human in IRIS CRM.
How does it decide who the right approver is?
You define routing rules during setup (e.g., by volume tier, risk tier, or business type). WebRun applies those rules to each application to find the correct reviewer.
What happens if no approver matches the routing rules?
It sends the request to a fallback approver you designate during setup, so no application waits in limbo without a reviewer assigned.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.