Automated Two Person Crew Routing
Each night, WebRun reads tomorrow's manifest in Deliveright Grasshopper, picks out the oversized items that need a two person crew, sequences them into a sensible route by area and access, drops a proposed crew calendar on Google Calendar, and posts the plan to Slack for a planner to confirm.
How do I automatically route oversized deliveries to a two person crew?
Each night WebRun reads tomorrow's manifest in Deliveright Grasshopper, picks the oversized items needing a two person crew, and sequences them into an efficient route by area, window, and access. It drops a proposed schedule on Google Calendar and posts it to Slack, so a planner starts the day with a ready two person run to confirm.
- Oversized stops arrive pre-grouped into a sensible two person run each morning
- Access hazards are flagged before the crew leaves the yard
- Planners confirm a route instead of building one from scratch
Built for furniture delivery teams · white glove carriers · route planners · final mile dispatch
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 - find oversized two person stops
deliveright.com
WebRun opens Deliveright to find oversized two person stops. - Open tomorrow's manifest in Deliveright Grasshopper
- Filter to items flagged oversized or requiring a two person handle
- Capture each stop's address, access notes, and time window
Done when Every oversized two person stop for tomorrow is listed with its constraints.
-
2
Google Calendar - propose the crew route
calendar.google.com
WebRun opens Google Calendar to propose the crew route. - Sequence the stops into an efficient run by area, window, and access difficulty
- Create tentative calendar blocks on the two person crew's Google Calendar
- Mark the route as a proposal for a planner to confirm, not a locked schedule
Done when A proposed, ordered crew route sits on the calendar awaiting sign-off.
-
3
Slack - post the plan to confirm
slack.com
WebRun opens Slack to post the plan to confirm. - Post the proposed stop order with drive time and any tight windows called out
- Flag stops with stairs, elevators, or narrow access for a planner's attention
Done when The planner has tomorrow's proposed two person route in Slack to confirm or adjust.
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 it lock the schedule without a planner?
No. It builds the route as a tentative proposal on Google Calendar and posts it to Slack for a planner to confirm or adjust. The crew's real schedule only changes once a human signs off.
How does it decide which stops need two people?
It reads the oversized and two person handle flags on each item in Deliveright Grasshopper, so only orders your team already marked as heavy get grouped into the crew's run.
Can it account for stairs and tight access?
Yes. It carries the access notes from each order into the plan and flags stairs, elevators, or narrow entries in Slack so the planner can sequence and staff them sensibly.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.