Automated talech Refund Exception Flags
Every morning, WebRun opens talech, reads all refunds processed in the prior day, flags any that exceed your configured dollar threshold or are missing a reason code, and posts a clear exception summary to your manager Slack channel with employee names and transaction details.
How do I automatically flag refund exceptions in my talech POS?
WebRun reads all refunds from talech every morning, flags any above your dollar threshold, missing a reason code, or from an employee with unusually high volume, and posts a grouped exception summary to Slack. Clean days get an all-clear so managers always know the check ran.
- Refund exceptions surface the next morning before they become a pattern
- Managers can investigate by employee or transaction type immediately
- All-clear messages confirm the check ran even on clean days
Built for retail store owners · restaurant managers · talech merchants · loss prevention 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.talech.comin a real browser with your saved login - no setup, no API keys. -
1
talech - read prior-day refunds
WebRun opens talech to read prior-day refunds. - Open talech and navigate to the refund report for yesterday
- Capture every refund with its amount, employee, time, item, and reason code
- Flag any refund above your configured dollar threshold
- Flag any refund with no reason code entered
- Count total refunds per employee and flag anyone with more than three in a single day
Done when All refund exceptions are identified with employee and transaction details.
-
2
Slack - post exception summary to manager
WebRun opens Slack to post exception summary to manager. - Post a formatted exception summary to your manager Slack channel
- Group exceptions by type: over-threshold, missing reason, and high-volume employee
- Send an all-clear message if no exceptions were found so the team knows the check ran
Done when Manager has a full refund exception summary in Slack or an all-clear confirmation.
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
What counts as a refund exception?
By default WebRun flags refunds above your set dollar threshold, refunds with no reason code, and any employee who processed more than three refunds in a day. You can adjust all three thresholds at setup.
Does it reverse or modify any refund in talech?
No. WebRun only reads and reports. It never modifies, reverses, or cancels a transaction in talech. All actions on flagged refunds are taken by your team.
What happens on a clean day with no exceptions?
WebRun posts a brief all-clear message so you know the check ran and nothing was flagged. Silence is not the signal; a confirmed all-clear is.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.