Route the right HVAC tech to every job — based on certification, skill set, and zone. Automatically.

We build a tech profile database that stores each technician's EPA 608 certification type — Type I (small appliances under 5 lbs), Type II (high-pressure systems like R-410A and R-22), Type III (low-pressure chillers), or Universal. When a job comes in, the routing engine reads the job's refrigerant classification and system type, then filters the eligible tech pool to only those who hold the correct certification. A commercial low-pressure chiller job is never routed to a Type II-only tech, regardless of proximity. This check happens automatically before any dispatch option is presented — not as a post-dispatch review.

Residential and commercial are configured as entirely separate dispatch tracks. Residential jobs route against the service tech pool using zone proximity and same-day availability as primary weights. Commercial jobs route against a filtered tech pool that includes commercial certification, equipment familiarity flags (rooftop units, chillers, VAV, building automation), and sometimes customer-specific access requirements like a site orientation record. We also build account-level routing rules for large commercial clients — so a tech who's been banned from a property by the facilities manager is never accidentally dispatched there.

Yes — and this is one of the most common HVAC dispatch failures we fix. Service techs have a single-person, same-day capacity model. Install crews have multi-person, multi-day capacity with crew lead assignments and staged scheduling. We build these as completely separate routing pools with different capacity logic, different scheduling windows, and different tech profile fields. Service calls never touch install crew capacity. Install leads never appear in the service queue. If you have techs who float between both (common in smaller HVAC companies), we build a dual-pool assignment logic that respects their current assignment status before routing them to either pool.

This is where manual dispatch completely breaks down — and where automation delivers the fastest ROI. When a tech goes unavailable mid-day, the re-dispatch flow activates automatically. It pulls all jobs assigned to that tech, re-scores each job against the remaining eligible tech pool using current schedule data and certification matching, and surfaces a re-dispatch recommendation for your dispatcher to review in one screen. For each affected customer, a proactive delay notification goes out via SMS automatically — before they call your office wondering where their tech is. The whole process takes under 5 minutes instead of the 45+ it takes manually.

The sprint runs in exactly 21 days. Week 1 is discovery and design: we audit your dispatch process, map your full tech profile roster (certifications, equipment skills, zones, service vs. install designation), design the routing logic for every job type you handle, and get your sign-off before writing a single integration. Week 2 is the build: CRM integration, routing engine, tech briefing automation, customer notification system, and re-dispatch flow. Week 3 is scenario testing, edge case validation, dispatcher training with written documentation and recorded walkthroughs, and go-live. Fixed $10k. No retainer, no monthly fee. 30-day post-launch support included.