Appointment Scheduler Agent
Books dock windows and reschedules when the plan moves.
- Portal, email, or phone
- Facility rules applied
- Slips rebooked the same hour
- needL-48291 needs a delivery window at Dallas DC 7
- bookFri 14:00–16:00 taken on the facility portal
- slipPickup runs 3 hours late — that window is no longer reachable
- rebookFri 18:00–20:00 confirmed; carrier and customer told
How appointments get booked
Web App Browser is the hands on a portal with no API. This agent is the scheduler — it picks the channel that dock actually accepts, then rebooks when the plan moves.
Whichever way that dock books
Facility portal, email to a coordinator, or a phone call when that is the only option.
That site’s rules
Receiving hours, lead times, PO requirements, and dock preferences come from the Knowledge Hub.
The next window that actually fits
Checked against the driver clock and the delivery commitment before it is taken.
A slip moves the rest
A late pickup does not just move one stop. Downstream appointments are recalculated and everyone affected is told.
What changes at the dock
Scheduling stops being a morning on hold.
Windows booked without the phone tree
Portal and inbox work runs in the background instead of consuming a morning of hold music.
Slips handled the same hour
Rebooking starts when the pickup runs late — not after detention has already been earned.
Fewer missed windows
Appointments are checked against the live ETA, so a window that will not be met gets moved first.
See it run on your freight
Bring one process that costs your team too much time. We will show you the same workflow running on Emulon, with the execution trace open.