Automated Thunes Failed Payout Handoffs
Every hour, WebRun opens the Thunes payout dashboard, checks for cross border payouts marked failed or delayed, adds a follow-up block to Google Calendar for the same day, and messages your ops team on WhatsApp with the payout reference and reason so it gets investigated quickly.
How do I get alerted when a Thunes payout fails?
WebRun checks your Thunes payout dashboard every hour for cross border payouts marked failed or delayed, schedules a same-day follow-up on Google Calendar, and messages your ops team on WhatsApp with the payout reference and reason. It never retries a payout or moves funds itself, so failed payouts get investigated within the hour.
- Failed payouts reach ops within the hour instead of at week's end
- Every exception has a scheduled follow-up instead of sitting unclaimed
- Payout reasons are captured immediately, before the trail goes cold
Built for payments operations · fintech ops teams · businesses using Thunes · treasury 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
www.thunes.comin a real browser with your saved login - no setup, no API keys. -
1
Thunes - check payout status
thunes.com
WebRun opens Thunes to check payout status. - Open the Thunes payout dashboard and check recent payout status
- Filter to payouts marked failed or delayed beyond the normal window
- Capture the payout reference, amount, and reason given
Done when Every failed or delayed payout is captured with its reason.
-
2
Google Calendar - schedule the follow-up
calendar.google.com
WebRun opens Google Calendar to schedule the follow-up. - Add a same-day follow-up block for each failed payout
- Include the payout reference and reason in the event notes
- Skip adding a duplicate if a follow-up already exists
Done when Every failed payout has a follow-up block on the calendar.
-
3
WhatsApp - message ops to investigate
whatsapp.com
WebRun uses WhatsApp to message ops to investigate. - Message your ops team with the payout reference, amount, and reason
- Ask them to investigate with Thunes support
- Leave the payout itself untouched either way
Done when Ops has been messaged about every failed payout this hour.
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 WebRun retry the payout or move funds itself?
No. WebRun never sends a payment, issues a refund, or transfers funds on its own. It only flags the failed payout and hands it to your ops team to investigate and resolve.
Who receives the WhatsApp message?
Your ops team, the internal group you've set up to handle payout exceptions. WebRun never messages the payout recipient or any outside party.
What counts as a delayed payout?
Any payout the Thunes dashboard shows as failed, or one still pending past the normal processing window you'd expect for that route.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.