Automated Refused Delivery Escalation
When a delivery is refused, WebRun reads the order and refusal reason in Deliveright Grasshopper, drafts a return authorization request to the retailer in Gmail, leaves it for a coordinator to review, and posts the growing returns queue to Slack so nothing sits in limbo on the truck.
How do I automatically escalate a refused delivery for a return authorization?
When a delivery is refused, WebRun reads the order and refusal reason in Deliveright Grasshopper, drafts a return authorization request to the retailer in Gmail, and leaves it for a coordinator to review. It posts the returns queue to Slack with each order's status, so refusals become RA requests fast and nothing is stranded.
- Refusals become drafted RA requests within minutes of the stop
- The returns queue is visible in Slack instead of lost in inboxes
- No retailer RA email sends without a coordinator's review
Built for white glove carriers · returns coordinators · furniture retailers · final mile ops
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
deliveright.comin a real browser with your saved login - no setup, no API keys. -
1
Deliveright - catch refused deliveries
deliveright.com
WebRun opens Deliveright to catch refused deliveries. - Open Deliveright Grasshopper and find stops closed as refused or rejected
- Read the refusal reason, the order, item, and retailer
- Skip orders already escalated this run
Done when Every refused delivery is captured with its reason and retailer.
-
2
Gmail - draft the RA request
gmail.com
WebRun opens Gmail to draft the RA request. - Draft a return authorization request to the retailer with the order, item, and refusal reason
- Ask for the RA number and return instructions
- Leave every email as a draft in Gmail for a coordinator to review and send
Done when An RA request is drafted for each refusal, none sent without review.
-
3
Slack - post the returns queue
slack.com
WebRun opens Slack to post the returns queue. - Post the returns queue: each refused order, reason, and whether an RA request is drafted
- Flag items sitting on a truck or in a hub awaiting a decision
Done when The returns team sees every refusal and its RA status in Slack.
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 email the retailer without me?
No. Each return authorization request is drafted and left in Gmail for a coordinator to review and send. Nothing goes to the retailer until a person confirms the refusal details and wording.
What does the RA request include?
The order and item, the refusal reason from Deliveright, and a request for the RA number and return instructions. It gives the retailer everything needed to authorize the return in one message.
How does it stop refusals getting stranded?
It posts the full returns queue to Slack each run and flags items still on a truck or in a hub awaiting a decision, so the returns team can act before goods sit idle.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.