Clear the refunds that are still sitting pending
Every morning, WebRun opens PhonePe, reads the refunds still marked pending, works out how far each one is past your normal turnaround, posts the operations team an oldest-first chase list in Microsoft Teams, and prepares a customer update on WhatsApp for each one, left unsent for you to approve.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track refunds that are still pending and chase them?
WebRun opens PhonePe each morning, finds the refunds still marked pending, and measures each against your normal turnaround. It posts an oldest-first chase list to Microsoft Teams and prepares a customer update on WhatsApp for every overdue one, left unsent for your approval, so nobody waits silently on their money.
- Every customer still waiting on money back is visible by 9:00 AM
- Refunds past your turnaround sit at the top of the queue, oldest first
- Customer updates are written and waiting instead of triggered by a complaint
Built for payment operations teams · ecommerce merchants · finance teams · customer support leads
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
www.phonepe.comin a real browser with your saved login - no setup, no API keys. -
1
PhonePe - find refunds still pending
WebRun opens PhonePe to find refunds still pending. - Open PhonePe and filter transactions to refunds
- Capture every refund whose status is still pending, with its amount, customer and initiation date
- Work out the age of each one against your normal turnaround window
- Note the matching original transaction and settlement so the finance team can trace it
- Skip refunds that completed since the last run
Done when Every pending refund is listed with its age, amount and customer.
-
2
Microsoft Teams - post the chase list
WebRun opens Microsoft Teams to post the chase list. - Post the operations channel an oldest-first list of refunds still pending
- Show the customer, amount, days pending and the original transaction reference
- Separate the ones past your turnaround from the ones still inside it
- Add the count and total value so the size of the queue is obvious
Done when The operations channel has today's pending refund queue in Microsoft Teams.
-
3
WhatsApp - prepare customer updates
WebRun opens WhatsApp to prepare customer updates. - Write a short, plain update for each customer still waiting, naming the amount and the date it was initiated
- Group them so you can work down the list in one sitting
- Leave every customer message unsent for you to read and approve. WebRun never messages a customer on its own
Done when A customer update is prepared for each overdue refund and waiting on your 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
Will it message customers about their refund without me?
No. Every customer update is prepared and left unsent for you to approve. Only the internal chase list posts on its own, and it goes to your own Microsoft Teams channel.
Can it issue or re-trigger a refund?
No. WebRun never moves money. It reads refund status in PhonePe and reports it. Issuing, cancelling or re-initiating a refund stays a human action inside your payments console.
How does it decide a refund is overdue?
You set your normal turnaround window once. WebRun measures each pending refund against it every morning and splits the list into overdue and still in window.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.