Automated bol.com Returns Handling Queue
Every morning, WebRun signs into your bol.com seller account, lists the returns that are still open, reads the reason the customer gave and whether the refund has settled, works out how many days each has been waiting, sends the whole queue to Telegram, and texts your ops number through Twilio when one is about to age out.
How do I handle bol.com returns before customers start chasing?
Every morning, WebRun signs into your bol.com seller account and lists the returns still open, with the reason the customer gave, whether the refund has settled, and how long each has waited. It sends the queue to Telegram and texts your ops number through Twilio when a return is aging out.
- Returns are handled before a customer raises a case
- Repeat return reasons on one product become visible
- Every refund decision stays with a person, not the automation
Built for bol.com sellers · ecommerce operations · marketplace sellers · 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
bol.comin a real browser with your saved login - no setup, no API keys. -
1
Bol.com - list open returns and refunds
bol.com
WebRun opens Bol.com to list open returns and refunds. - Sign into your bol.com seller account and open the returns overview
- List every return that is still open or awaiting a decision
- Read the return reason the customer gave and the original order it belongs to
- Check whether the refund has been issued, is pending, or has not been started
- Count the days since the return was registered so aging is visible
- Do not accept, reject, or refund anything. WebRun reports the queue and a person decides in bol.com
Done when Every open return is listed with its reason, refund status, and age in days.
-
2
Telegram - send the returns queue
telegram.org
WebRun opens Telegram to send the returns queue. - Send today's returns queue to your operations chat on Telegram
- Order it oldest first so the ones closest to a complaint sit at the top
- Show the order number, the item, the reason given, the refund status, and the days waiting
- Group the reasons so a product with repeated damage or wrong-size returns stands out
Done when The operations chat has today's queue ordered by how long each return has waited.
-
3
Twilio - text ops about the aging ones
twilio.com
WebRun opens Twilio to text ops about the aging ones. - Send an SMS through Twilio to your own operations number when a return passes the age you set
- Keep the text short: how many returns are aging and the oldest order number
- Send only to the internal numbers saved at setup. WebRun never texts a bol.com customer
- Stay silent on mornings where nothing has aged past the threshold
Done when Ops has been texted about aging returns, or nothing needed a text.
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 issue refunds or accept returns for me?
No. Refunding money and accepting or rejecting a return are irreversible, so WebRun only builds the queue. A person makes each decision inside bol.com.
Will it message my customers?
No. The Telegram queue goes to your own operations chat and the Twilio SMS goes to internal numbers you save at setup. No bol.com customer is contacted by this run.
How does it stop a return from aging out?
It counts the days since each return was registered, orders the queue oldest first, and texts your ops number once a return crosses the age threshold you choose.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.