Automated Inbound Grain Truck Scheduling
Every afternoon, WebRun opens Ceres, reads the loads expected inbound tomorrow against open contracts and delivery windows, builds a truck schedule by time slot and pit in Google Calendar to spread arrivals, and drafts a confirmation text per driver in Twilio that waits for your approval before it is sent.
How do I schedule inbound grain trucks so the pit does not back up?
Every afternoon, WebRun opens Ceres and reads the loads expected inbound tomorrow against open contracts and delivery windows. It builds a truck schedule by time slot and pit in Google Calendar to spread arrivals, then drafts a confirmation text per driver in Twilio, queued unsent, so nothing is sent to a driver without your approval.
- Tomorrow's trucks are spread across slots so the pit keeps moving
- Drivers get a clear arrival window and pit to report to
- Confirmation texts wait for your approval before any driver is messaged
Built for grain elevators · elevator managers · grain logistics coordinators · country elevators
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
www.verticalsoftware.netin a real browser with your saved login - no setup, no API keys. -
1
Vertical Software Ceres - read expected inbound loads
verticalsoftware.net
WebRun opens Ceres to read tomorrow's expected inbound loads. - Open Ceres and read loads expected inbound tomorrow against open contracts
- Capture producer, grain, estimated bushels, and any delivery window
- Estimate how many trucks and how much pit time each delivery needs
Done when Tomorrow's expected inbound loads are listed with sizes and windows.
-
2
Google Calendar - build the truck schedule
calendar.google.com
WebRun builds tomorrow's inbound truck schedule in Google Calendar. - Open the receiving calendar and lay out arrival slots across the day
- Spread loads so no single hour or pit is overbooked
- Add each slot with producer, grain, and estimated bushels in the title
Done when Tomorrow's inbound trucks are scheduled into calendar slots.
-
3
Twilio - draft driver confirmations
twilio.com
WebRun drafts each driver's confirmation text and leaves it unsent. - Draft a confirmation text per driver with their assigned arrival window
- Include the pit or scale to report to and any grain-specific instructions
- Leave every text queued and unsent for you to review and release
Done when A driver confirmation text is drafted and queued for your approval.
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 text drivers without my approval?
No. WebRun drafts every driver confirmation in Twilio and leaves it queued and unsent. You review the slots and release the texts yourself, so no driver is messaged until you approve the schedule.
How does it decide the arrival slots?
It reads the loads expected against contracts and delivery windows in Ceres, estimates the pit time each needs, and spreads arrivals across the day so no single hour or pit is overbooked.
What if a producer's plans change after the schedule is built?
Because the texts wait for your approval, you can adjust or drop any slot before releasing them, and the next afternoon's run re-reads the live expected loads in Ceres.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.