Recurring Service Dispatcher: Due-Plan Scanner → Ticket Creation with Blackout-Window Escalation

Problem:

Recurring service plans depended on someone remembering to check which plans were due, price the visit, raise the ticket, and confirm the property wasn't in a blackout window so visits slipped and blackout conflicts were caught too late.

Solution:

Built a scheduled Make.com scenario that searches Airtable for due plans behind an 'If Plan Exists' filter, pulls the matching Service Pricing and Property records through a dispatch-condition filter, and creates the Service Ticket. It then checks blackout records for the property and feeds a Blackout Decision Router: with no blackout in the window, it creates the sales Opportunity and advances the plan to its next cycle date; with an active blackout, it escalates the ticket and advances the plan on the escalated track instead.

Result:

Due service plans now convert into priced tickets and opportunities automatically on schedule, with blackout conflicts escalated the moment they're detected instead of discovered on dispatch day.