Automated MCA Application Pipeline Digest
Every afternoon, WebRun opens Centrex, tallies the count of applications in each origination stage (submitted, under review, approved, declined, funded, pending documents), flags any file stalled in one stage for more than 2 business days, and posts a pipeline digest to your origination Slack channel so your team finishes the day with a clear queue picture.
How do I get an automatic daily status digest of my MCA application pipeline?
WebRun opens Centrex every afternoon and counts applications at each stage of your origination pipeline, from submitted through to funded. It flags any file stalled for more than 2 days and posts the full pipeline digest to Slack, giving your team a clear queue picture before the day closes.
- Origination team ends each day knowing exactly how many files are in each stage
- Stalled applications are surfaced before they turn into missed opportunities
- No manual pipeline reporting required from the team
Built for MCA origination managers · MCA underwriters · advance processors · MCA operations 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.centrexsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
Centrex - count applications by origination stage
centrexsoftware.com
WebRun opens Centrex to count applications by origination stage. - Open Centrex and navigate to the origination pipeline view
- Count applications in each stage: submitted, under review, approved, pending documents, declined, and funded
- Identify any application that has not moved stage in more than 2 business days and capture the file owner and stage name
Done when Stage counts and stalled file list are captured from Centrex.
-
2
Slack - post daily pipeline digest with stall flags
slack.com
WebRun opens Slack to post daily pipeline digest with stall flags. - Post the daily pipeline digest to your origination Slack channel
- Include a stage-by-stage count and a comparison to yesterday's counts where available
- List each stalled file with the merchant name, stage, days stalled, and assigned owner
Done when Your origination team has the afternoon pipeline digest in Slack with all stalled files surfaced.
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 move or update any applications in Centrex?
No. WebRun reads the Centrex pipeline and reports what it finds. All stage movements and decisions remain with your origination team.
What counts as a stalled application?
Any application that has not changed stage in more than 2 consecutive business days is flagged. You can adjust this threshold when setting up the workflow.
Can we receive the digest in a channel other than Slack?
Yes. The digest can be directed to a Telegram channel or an email address instead of or in addition to Slack during workflow setup.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.