Twilio Expert Needed: Build Dispatch Broadcast & Lockout System via Functions & Studio

Here is what we have so far , a zapier website form that once submitted for a ride request triggers my sms approved twilio number to send me a text with the requested ride info ( lighting fast ) what wouldbe better is Twilio Expert to Build Dispatch Broadcast & Lockout System via Functions & Studio Project Description: We run a local Free community micro courtesy shuttle business utilizing a fleet of 6 gas-powered passenger vans. We need a backend developer to build a text-message-based dispatching system using Twilio Studio, Twilio Functions, and Twilio Sync for data tracking. Core Workflow Required: Web Request Ingestion: Webhook takes ride data (Name, Pickup, Dropoff, Resident Status, Pax count). Active Schedule Check: System checks an internal list of active, on-duty drivers (needs an easy way for me to update weekly schedules or toggles). Simultaneous SMS Broadcast: Send a ride text to only the active drivers on-duty right now. First Responder Wins (Lockout Logic): When a driver replies with a number (e.g., "15"), a Twilio Function checks Twilio Sync. If the ride is still unclaimed, lock it to that driver, store their name and their inputted ETA, and mark the ride as "Claimed". Late drivers must get an automated "Already claimed" text back. Customer Interactive Flow: Trigger a Twilio Studio flow to text the customer: "Your ride is confirmed! [Driver Name] will arrive in [ETA] minutes. Reply CANCEL within 3 minutes if you don't want to wait." Handle customer cancellation loops cleanly. Archival: Push all completed or canceled ride data to a permanent history log. Requirements: Deep experience with Twilio Node.js runtime environments. Proven experience managing race conditions via Twilio Sync Maps/Documents. Ability to build clean, well-commented code so non-technical owners can easily swap out driver lists/phone numbers. Step 2: Prepare Your System Specs (Before the First Call) To keep this fast and budget-friendly, hand developer clean blueprint of your data structure on day one. Have an Excel or Google Sheet ready that maps out exactly what you want tracked: Driver Name Driver Phone Shift Day Start Hour End Hour Status (On/Off Duty) Driver 1 +1727xxxxxxxx Monday 08:00 16:00 Active Driver 2 +1727xxxxxxxx Monday 16:00 23:00 Off-Duty “Can we use Twilio Sync to manage this schedule list, or would it be easier to have the Twilio Function pull this table dynamically from a Google Sheet using the Google Sheets API?” Step 3: Execution and Safeguards the milestone payments based on clear deliverables: Milestone 1 (Setup & Simulation): The developer creates the Twilio Sync environment and proves that if they send two simulate driver texts at the exact same second, one gets the ride and the other gets locked out. Milestone 2 (Studio Integration): The customer text sends successfully with the winning driver's name and ETA, and replying "CANCEL" triggers the cancellation text back to the driver. Milestone 3 (Live Beta Test): I stand on the beach with 2 or 3 of my drivers on a Tuesday afternoon. i hit submit on your webpage, watch the phones drop the texts, claim the ride, and verify the customer workflow. let me know what I missed ?