Automated Tmall After-Sales Queue Tracking
Every hour, WebRun signs in to your Tmall seller account, reads the open refund and after-sales requests, pulls the order and buyer behind each one, works out how long is left before the response deadline, records them in Notion, and posts the requests closest to timing out into Microsoft Teams.
How do I keep on top of Tmall refund and after-sales requests?
WebRun reads your Tmall after-sales queue every hour, capturing each refund request with its order, amount, reason, and the time left to respond. It logs every request in Notion and posts the ones closest to timing out into Microsoft Teams, so none of them expire against the shop.
- Requests are ranked by hours left, so nothing times out unnoticed
- A suggested reply is drafted before anyone opens the queue
- Teams stays quiet unless something is inside the warning window
Built for Tmall sellers · marketplace operators · ecommerce operations teams · cross-border brands
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
tmall.comin a real browser with your saved login - no setup, no API keys. -
1
Tmall - read the after-sales queue
tmall.com
WebRun opens Tmall to read the after-sales queue. - Sign in to your Tmall seller account and list every open refund and after-sales request
- Capture the order number, the buyer, the amount, and the reason given for each
- Read the response deadline on each request and work out the hours remaining
- Draft a suggested reply for each request and leave it unsent. WebRun never approves a refund, declines one, or messages a buyer
Done when Every open request is captured with its order, amount, reason, and hours left to respond.
-
2
Notion - log every open request
notion.so
WebRun opens Notion to log every open request. - Keep one row per open request in your after-sales database with order, buyer, amount, and reason
- Update the hours remaining on each run and mark requests that have since been resolved as closed
- Record which requests had a reply drafted and which are still untouched
Done when The Notion database matches the live queue with hours remaining on every open row.
-
3
Microsoft Teams - post what is running out of time
microsoft.com
WebRun opens Microsoft Teams to post what is running out of time. - Post the requests with the least time left to your store operations channel
- Show the order, the amount, the reason, and the hours remaining for each
- Say which ones already have a drafted reply waiting for approval
- Stay quiet when nothing is inside the warning window
Done when The operations channel has the requests closest to timing out.
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 approve refunds or reply to buyers?
No. WebRun never approves or declines a refund, issues money, or sends a message to a buyer. It drafts a suggested reply and leaves it for a person to review, approve, and send.
How does it rank the queue?
By hours left before each request's response deadline, soonest first, so the request most likely to time out against the shop is the one at the top of the list.
Does it post every hour even when the queue is quiet?
No. It updates Notion each run but only posts to Teams when a request is inside the warning window you set, so the channel stays worth reading.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.