Automated JD.com Return Request Queue
Every morning, WebRun opens your JD.com seller account, reads the return and refund requests still waiting on a decision, logs each one in Airtable with the order, the buyer's reason, and how long it has waited, and posts the queue to Microsoft Teams with the oldest first.
How do I keep on top of return and refund requests on my store?
WebRun opens your JD.com seller account every morning, reads the return and refund requests still waiting on a decision, and logs each one in Airtable with the order, the buyer's reason, and how long it has waited. It then posts the queue to Microsoft Teams oldest first, so refunds get handled before they become complaints.
- The longest waiting request is worked first, every morning
- The value still under dispute is visible daily
- Resolved requests drop off the queue on their own
Built for marketplace sellers · ecommerce operations · customer service teams · store managers
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
jd.comin a real browser with your saved login - no setup, no API keys. -
1
JD.com - read pending return requests
jd.com
WebRun opens JD.com to read pending return requests. - Open your JD.com seller account and go to the after-sales requests list
- Filter to requests still awaiting a decision from you
- Capture the order number, the request type, the buyer's stated reason, the amount, and the date it was opened
Done when Every pending return and refund request has been captured with its details.
-
2
Airtable - log each request with its age
airtable.com
WebRun opens Airtable to log each request with its age. - Add or update a row per request with the order, type, reason, amount, and days waiting
- Mark rows as resolved once the request no longer appears as pending
- Sort the view so the longest waiting requests sit at the top
Done when The Airtable queue matches the live pending list on JD.com.
-
3
Microsoft Teams - post the queue oldest first
microsoft.com
WebRun opens Microsoft Teams to post the queue oldest first. - Post today's queue to your store operations channel, oldest request first
- Flag anything waiting longer than the threshold you set
- Give the count and the total value still under dispute
Done when The team has today's after-sales queue in Teams.
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 or refuse a refund on its own?
No. WebRun reads the pending requests and queues them for you. Approving a return, issuing a refund, or replying to a buyer stays a human decision, because each one moves money and cannot be undone.
Does it message the buyer?
No. The queue is internal only, going to Airtable and your Teams channel. WebRun never sends a message to a JD.com buyer or posts anything on your store.
What happens when a request is resolved?
It drops out of the next morning's queue automatically, because WebRun reads the live pending list each run and marks the matching Airtable row resolved.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.