Manage freight pickup and delivery appointments, send automated reminders to carriers and shippers, detect scheduling conflicts, and track load timelines. Use when a broker needs to schedule a pickup or delivery, wants to send reminders, has a scheduling conflict, or wants to see upcoming appointments. Triggered by phrases like "schedule pickup", "schedule delivery", "upcoming appointments", "remind carrier", or "reschedule load".
Manages pickup/delivery appointments with reminders and conflict detection.
cd skills/freight-scheduler/scripts
python3 appointment_manager.py --create --load LOAD-001 --type pickup --datetime "2025-12-18 09:00" --carrier-phone "555-1234"
python3 appointment_manager.py --load LOAD-001 --list
python3 reminder_sender.py --apt APT-20251218000001 --hours 24
| Command | Action |
|---|---|
schedule pickup [load ID] [time] | Set pickup appointment |
schedule delivery [load ID] [time] | Set delivery appointment |
upcoming appointments | List next 48 hours |
remind carrier [load ID] | Send reminder now |
reschedule [load ID] to [time] | Change appointment |
📅 APPOINTMENT SET - Load #12345
Pickup: Dec 18, 9am | LA Warehouse
Delivery: Dec 22, 2pm | NYC Receiver
Reminders: Carrier & shipper notified ✅
Reply 'reschedule [new time]' if needed
📅 NEXT 24 HOURS
Load #12345 - Pickup 9am ✅ Confirmed
Load #12346 - Pickup 2pm ⚠️ Unconfirmed
Load #12347 - Delivery 5pm ✅ Confirmed
Reply 'remind [load ID]' to resend
Default reminders sent at:
This skill uses the following external services. See INTEGRATIONS.md for detailed setup instructions, API documentation links, and implementation guidance.
| Service | Purpose | Section in INTEGRATIONS.md |
|---|---|---|
| Google Calendar API | Sync appointments to calendar | Skill 7: Google Calendar API |
| Microsoft Graph Calendar | Outlook calendar sync | Skill 7: Microsoft Graph Calendar |
| Twilio | SMS reminders | Shared Infrastructure: Twilio |
# Send daily upcoming summary at 6am
0 6 * * * cd /path/to/freight-scheduler/scripts && python3 reminder_sender.py --daily >> /tmp/scheduler.log 2>&1
See INTEGRATIONS.md for complete integration architecture