Book a delivery window from the consignee's reply
When consignees reply to a scheduling text, WebRun reads their chosen window, checks it against open capacity in Deliveright Grasshopper, drafts a confirmation text in Twilio, and pencils the slot on Google Calendar, all queued for a scheduler to approve before anything is locked.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically book a delivery window from a customer's text reply?
When consignees reply to a scheduling text, WebRun reads their chosen window in Twilio, checks it against route capacity in Deliveright Grasshopper, drafts a confirmation text, and pencils a tentative slot on Google Calendar. Everything is queued for a scheduler to approve, so a customer reply becomes a ready-to-confirm appointment without any window being locked automatically.
- Customer replies turn into ready-to-confirm windows within minutes
- Requested slots are checked against real route capacity first
- No appointment locks or confirms without a scheduler's approval
Built for white glove carriers · delivery schedulers · furniture logistics · 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
Twilio - read the consignee reply
WebRun opens Twilio to read the consignee reply. - Read incoming consignee replies to the scheduling text in Twilio
- Parse the day and window each consignee prefers
- Draft a confirmation text back, queued and left unsent for a scheduler to approve
Done when Each reply has a parsed window and a drafted confirmation awaiting approval.
-
2
Deliveright - check window capacity
WebRun opens Deliveright to check window capacity. - Open Deliveright Grasshopper and check the requested window against route capacity and zone
- Confirm the stop fits, or note the nearest open alternative
- Attach the order and address to the proposed booking
Done when Each requested window is checked against real capacity in Grasshopper.
-
3
Google Calendar - pencil the proposed slot
WebRun opens Google Calendar to pencil the proposed slot. - Pencil a tentative appointment block on the delivery calendar for the requested window
- Mark it proposed, pending a scheduler's confirmation
- Note any conflict or capacity issue on the event for a human to resolve
Done when A proposed slot sits on the calendar for the scheduler to confirm.
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 confirm the appointment to the customer on its own?
No. It drafts the confirmation text in Twilio and pencils a tentative slot on the calendar, both left for a scheduler to approve. The consignee only gets a confirmed window once a person signs off.
What if the requested window is full?
It checks capacity in Deliveright Grasshopper first and, if the slot is full, notes the nearest open alternative on the proposed booking so the scheduler can offer it rather than overbooking a route.
How does it understand a free-text reply?
It reads the consignee's message in Twilio and parses the day and window they name. Anything ambiguous is flagged for the scheduler instead of being guessed at.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.