Back to pricing
Phoenix — Pixar-style AI operations lead pilot portrait
Live now Wingman Flight Director

Phoenix

Operations Lead

Routes inbound jobs to the right tech by skill, zone, and current load. Health-checks every Wingman + workflow and gives you a daily ops briefing on what's broken.

What Phoenix does

Phoenix is the operations layer most growing service shops are missing. When a qualified lead lands, Phoenix picks the best-fit tech using skills, zones, and current load, then assigns the job and SMS's the tech with the details. He runs a daily health check on every Wingman + workflow in your account, so if Mia's not picking up or Charlotte's campaign threw an error, you know about it before customers do. Each morning your inbox gets an ops briefing with jobs booked, jobs completed, missed calls, stuck deals, and any anomalies worth a look.

Capabilities

Built to do this every day.

01

Skill + zone + load routing

Phoenix knows which tech is qualified for which job type (gas vs electric, drain vs install), which zones each tech covers, and how loaded each tech is today. When a Qualified lead lands, he picks the right tech in under 5 seconds and SMS's them.

02

Daily workflow health checks

Every night at 11 PM, Phoenix scans every installed Wingman workflow. He looks for contacts stuck mid-workflow, workflows that fired errors, drops in expected fire rates, and any anomaly. If something's broken, you get an SMS before the customer notices.

03

Daily 7 AM owner briefing

Jobs booked yesterday, jobs completed, missed calls, stuck deals (3+ days no touch), anomalies (sudden drops or spikes). All in 6 to 8 bullets. Read time under 2 minutes. Coffee in hand.

04

Weekly team performance report

Sunday 6 PM email with jobs-per-tech, average job duration, customer satisfaction by tech (from Stella's review tagging), and the one bottleneck Phoenix recommends fixing this week.

05

Anomaly detection and escalation

Phoenix tracks the baseline (missed calls per day, booking rate per lead, average reply time on chat) and alerts you when something deviates more than 30 percent. 'Booking rate dropped from 38 percent to 19 percent yesterday — Sophia might be misclassifying.' Action item, not just a chart.

06

Cross-Wingman coordination

If Harper hands off to Mia, or Mia hands off to Henry, or Henry hands off to Harper, Phoenix watches the handoffs and flags any breaks. The whole crew works as a unit, not 10 separate Wingmen.

In the field

Real scenarios.

Qualified lead routed in 4 seconds

Mia just booked a sump pump install for Friday. The opportunity moves to Qualified.

Phoenix reads the job (sump pump = drain skill + Northgate zone), checks the tech roster (Mike covers Northgate + has drain skill + has 2 open slots Friday), assigns to Mike, and SMS's him with the job address, time, customer name, and notes. Total time: 4 seconds. Mike acknowledges within 90 seconds. You didn't lift a finger.

"New job Friday 10 AM: Sump pump install, 1247 Northgate Ave, customer Tom Hendricks. Mia's notes: existing pump 14 years old, basement bone dry currently. Reply YES if you can take it, otherwise I'll reassign."

Wingman health alert

It's 11 PM Thursday. Phoenix runs his nightly health check.

Phoenix spots that Charlotte's Q1 campaign workflow has 12 contacts stuck mid-flow (expected 0). Drills in: a third-party SMS provider issue caused message-send failures since 3 PM. He SMS's you with the issue, the impact (12 contacts, 7 of whom would have booked based on historic conversion rate), and the suggested action (retry the failed sends in the morning, or escalate to the provider).

"Heads up — Charlotte's Q1 SMS sends started failing at 3:15 PM today. 12 contacts stuck. the upstream phone provider is reporting issues. Suggest: retry failed sends at 7 AM when their status page clears. Want me to schedule it?"

Monday morning briefing

Monday 7 AM. You're heading to the truck.

Phoenix's briefing hits your inbox: '4 jobs Sunday completed, 6 booked. 2 missed calls Saturday after-hours that Mia rebooked. 1 stuck deal: Sarah Henderson, 4 days no touch. 1 anomaly: Saturday booking rate was 19 percent (baseline 35 percent), Sophia might have misclassified some inbound chats. Priority today: review Sophia's Saturday classifications.' 90 seconds to read, 2 actions to take.

What you'll connect

Integrations

Required connections need to be wired before Phoenix can fly. We'll guide you through every one during onboarding.

  • Tech roster with skills + zones

    Phoenix's routing input

  • Tech availability schedule per day

    So routing doesn't double-book

  • Owner phone for alerts

    For anomaly + health-check SMS

  • Email for daily briefings + weekly reports

    Where the 7 AM briefing lands

  • +

    Other installed Wingmen Optional

    Phoenix coordinates the whole crew if multiple are live

  • +

    Customer satisfaction signal Optional

    Pulled from Stella's review tagging if installed

What gets deployed

Inside the build

When your estimate is accepted, our system automatically deploys these artifacts to your Wingman dashboard. No copy-paste, no manual setup.

  • Qualified-lead routing workflow with skill + zone + load matching
  • Four automation handlers (route_inbound, workflow_health_check, daily_briefing, team_performance)
  • Nightly workflow health-check cron (11 PM)
  • Daily ops briefing cron (7 AM local)
  • Weekly team performance cron (Sunday 6 PM)
  • Anomaly detection workflow with configurable thresholds
  • Cross-Wingman handoff monitor workflow
  • Tech assignment + tech-confirmation SMS workflow
  • Custom fields on user records: tech_skills, tech_zones, tech_status, tech_capacity
  • Custom fields on opportunities: phoenix_assigned_tech, phoenix_assigned_at, phoenix_routing_reason

Ideal for

Growing service shops with 2 to 20 techs where dispatch and ops oversight have outgrown the owner's head. Especially trades with skill differentiation (gas vs electric, drain vs install) and multi-zone coverage.

FAQ

Common questions.

What if I'm a solo operator without a team? +

Phoenix's routing function becomes a no-op (all jobs go to you), but the rest of his value (workflow health checks, daily briefings, anomaly detection, weekly reports) still applies. Solo operators usually skip Phoenix and pick him up when they hire their first tech.

How is the daily briefing different from a CRM dashboard? +

A dashboard makes you go look. The briefing comes to you in 6 to 8 bullets with priorities. Phoenix triages your day so you start with the right 2 actions instead of staring at a wall of numbers.

Will Phoenix mis-route a job? +

Routing is rule-based plus a AI check on edge cases. If skills + zones + load all point the same direction, he assigns. If there's ambiguity (two equally-qualified techs, or no perfect match), he kicks the routing to you with the candidates and his suggestion. Default is conservative: ambiguous goes to owner.

What's the difference between Phoenix and Henry? +

Henry runs the customer-facing coordination (confirmations, reschedules, prep). Phoenix runs the internal operations (tech routing, workflow health, ops briefings). Henry talks to your customers. Phoenix watches your business.

Can Phoenix tell me which Wingman is underperforming? +

Yes, in the weekly report. He shows per-Wingman fire rates, conversion rates, and trendlines vs the prior 4 weeks. If Harper's chase conversion drops 15 percent, Phoenix flags it with a suggested cause (often a brand voice drift or a specific message step that's underperforming).

Ready to hire Phoenix?

Tell us about your business and we'll send a tailored proposal with Phoenix configured for your industry — within one business day.