Turn borrower update requests into a ready-to-approve change
When a borrower requests an update to their contact or bank details, WebRun opens LoanPro to pull the current record on file, logs the requested change to a Google Sheet alongside the current values so staff can compare them, and pings your servicing team on Telegram to verify the borrower's identity and approve the change before anything in LoanPro is edited.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I safely process borrower requests to update contact or payment info?
When a borrower requests an update to their contact or payment info, WebRun opens LoanPro to pull the current record, logs the requested change in Google Sheets next to the current value, and pings staff on Telegram to verify and approve it. Payment method changes are flagged for identity verification, and WebRun never edits a LoanPro record itself.
- Every requested change is compared against the current value before approval
- Payment method changes get flagged for extra identity verification
- No record in LoanPro is edited without a staff member's approval
Built for loan servicers · consumer lenders · credit unions · customer service 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
loanpro.ioin a real browser with your saved login - no setup, no API keys. -
1
LoanPro - pull the current borrower record
loanpro.io How to Automate LoanPro
WebRun opens LoanPro to pull the current borrower record. - Open LoanPro and locate the borrower's loan from the request
- Pull the current contact info and, if requested, the current payment method on file
- Do not edit the record. Only read the current values for comparison
Done when The borrower's current record is pulled from LoanPro for comparison.
-
2
Google Sheets - log the requested change for comparison
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log the requested change for comparison. - Open the update request tracker Google Sheet
- Log the requested change next to the current value on file, along with the request date and channel
- Mark bank or payment method changes as High Verification since these carry the most fraud risk
Done when The requested change is logged next to the current value, with a verification level assigned.
-
3
Telegram - notify staff to verify and approve
telegram.org How to Automate Telegram
WebRun opens Telegram to notify staff to verify and approve. - Notify staff of the pending request with the current and requested values side by side
- For any payment method change, remind staff to verify the borrower's identity through a second channel before approving
- Leave applying the change in LoanPro to staff. WebRun never edits the record itself
Done when Staff has been notified and no change has been applied without their approval.
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 update the borrower's record automatically?
No. WebRun only reads the current record and logs the requested change. A staff member verifies the borrower and applies the update in LoanPro themselves.
Why does a payment method change get flagged differently?
Bank and card changes carry the highest fraud risk, so those requests are marked High Verification and staff are reminded to confirm the borrower's identity through a second channel before approving.
What information does staff see to make the decision?
The Google Sheet log shows the current value on file next to the requested change, so staff can spot anything that looks inconsistent with the borrower's history before approving it.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.