Automated MCA Application Routing to Underwriters
When a new MCA application is submitted in Centrex, WebRun reads the deal profile including requested amount, industry, and time in business, applies your underwriter routing rules, posts a structured intake card to the assigned underwriter in Slack, and logs the assignment to the underwriting queue in Google Sheets.
How do I automatically route new MCA applications to the right underwriter?
WebRun reads every new MCA application in Centrex as it arrives, applies your routing rules to match it to the right underwriter based on deal size and industry, logs the assignment in Google Sheets, and posts a structured intake card to the underwriter in Slack so they can start reviewing within minutes of submission.
- Every new application reaches the right underwriter within minutes of submission
- Underwriting workload is visible in real time in Google Sheets
- High-value and expedite applications are flagged automatically for priority handling
Built for MCA underwriting managers · MCA funders · advance origination teams · lending 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
app.centrexsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
Centrex - read new application profile
centrexsoftware.com
WebRun opens Centrex to read new application profile. - Detect a new application submission in Centrex
- Capture requested advance amount, industry, monthly revenue, time in business, and ISO broker name
- Apply your routing rules to select the assigned underwriter based on deal size and industry
Done when The application is matched to an underwriter using the routing rules from the deal profile.
-
2
Google Sheets - log assignment to underwriting queue
google.com
WebRun opens Google Sheets to log assignment to underwriting queue. - Append the application to the underwriting queue sheet with the assigned underwriter, submission time, and deal profile summary
- Update the underwriter's current queue count so workload is visible
- Flag any application above your high-value threshold for senior underwriter review
Done when The application is logged in the underwriting queue sheet with the correct assignment and workload count updated.
-
3
Slack - post intake card to assigned underwriter
slack.com
WebRun opens Slack to post intake card to assigned underwriter. - Post an intake card to the assigned underwriter's Slack DM or the underwriting channel
- Include merchant name, requested amount, industry, ISO broker, and a link to the Centrex application
- Flag high-value or expedite-requested applications with a priority tag
Done when The assigned underwriter has received the intake card in Slack with all details and a direct link to Centrex.
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 on its own?
No. WebRun only routes and surfaces the application to the assigned underwriter. All approval and decline decisions are made by the underwriter after their own review.
How are the routing rules set?
You define the routing rules during setup, for example, deals above a certain amount go to a senior underwriter, and specific industries route to a specialist. WebRun applies those rules on every new submission.
What if no underwriter is available or matches the routing rule?
If no matching rule is found, the application is flagged as unassigned in the Google Sheet and posted to a general underwriting Slack channel so a manager can assign it manually.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.