Community Scheduling

Build a route-aware community delivery schedule for a given planning period. The agent queries Airtable for orders, community geography, drive-tier proximity, scheduling-tier config, and customer delivery preferences, then groups orders into community time-slots sequenced for route efficiency. All scheduling parameters (tier windows, travel times, drive distances) are read from Airtable at runtime — nothing is hardcoded. The process handles multi-day scheduling periods, checks for existing CDS records (idempotency), and exits early when no orders need scheduling. Founders review and iterate on the draft via WhatsApp until approved.