Track every refund request so none get missed
Every few minutes during trading hours, WebRun checks iKhokha for new refund requests, logs each one in Google Sheets with the customer, amount, and reason, and marks any that have missed iKhokha's same-day refund window so you know it needs manual follow up.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I keep track of every iKhokha refund request?
WebRun checks iKhokha every few minutes for new refund requests and logs each one in Google Sheets with the customer, amount, and reason. Because iKhokha only allows a same-day refund with the original card, it flags any request that has missed that window, so you know it needs manual follow up before it's forgotten.
- Every refund request is logged the moment it happens, not weeks later
- A missed same-day window gets flagged before the customer has to ask twice
- Your refund history builds into one searchable Google Sheet
Built for retail shop owners · restaurant and service businesses · 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
dashboard.ikhokha.comin a real browser with your saved login - no setup, no API keys. -
1
iKhokha - find new refund requests
ikhokha.com How to Automate iKhokha
WebRun opens iKhokha to find new refund requests. - Check iKhokha for any refund requested or processed since the last run
- Capture the customer, amount, reason, and original transaction date
- Note whether it still falls within the same-day refund window
Done when Every refund request since the last check is captured.
-
2
Google Sheets - log each request and its status
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log each request and its status. - Add a row for each refund with its status: processed, pending, or missed window
- Highlight any request that has missed the same-day window
Done when The refund log matches every request iKhokha shows, with nothing left unmarked.
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 WebRun ever issue the refund itself?
No, it never processes or authorizes a refund. It only logs requests that already happened in iKhokha, so the actual refund action always stays with you or your staff.
Why does the same-day window matter?
iKhokha only allows a refund the same day, for the full amount, with the original card present. Anything past that window needs your support team's help, so WebRun flags it early instead of letting it slip.
Will old refunds get logged twice?
No, each check only looks at what's new since the last run, so a refund already logged won't be added again.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.