Tiered Vendor Dispatch: Standard Ticket → Preferred, Fallback & Global Routing with Blackout Guard

Problem: Dispatching a standard-tier service ticket required someone to check property blackouts, look up the client's preferred vendor, fall back manually when that vendor couldn't take the job, then notify the vendor, the client, and ops across SMS and email in separate tools.

Solution: Built a Make.com scenario (10. Standard-Tier Dispatch) that runs every minute, watching Standard Tickets in Airtable. On trigger it gets the Property, searches Blackouts, and routes through a Blackout Check: active blackouts fire a staff alert path (parse phone number, send Alert Blackout Staff SMS via Quo, log communication). Clear blackouts flow into Search Preferences and a Vendor Preference Check router that opens three parallel dispatch tracks (Preferred Vendor via Get + Verify, Fallback Global Vendors, Search Global Vendors), each following the same cadence of Get Service Rate → Create Opportunity Ticket → Set Arrival URL → Mark Ticket Dispatched → parse Phone number → Send Vendor SMS + Email → Log Communication → Get Client → parse Phone number → Notify Client SMS → Log Communication, with the fallback and global paths carrying their own tier labels so the audit trail records which tier won the job.

Result: Standard-tier tickets now dispatch to the correct vendor tier automatically every minute, with blackouts caught before dispatch and both vendor and client notifications fired across SMS and email in a single run.