Emergency Call Triage for HVAC and Plumbing Dispatch

Not every caller who says emergency is an emergency. Not every calm caller is safe. Triage is the skill that protects homeowners and your on-call rotation at the same time.

This is a practical tree you can hand to CSRs and encode into an AI receptionist.

Hard emergencies

• Suspected gas leak or CO alarm
• Active flooding / sewage backup into living space
• No heat in dangerous cold with vulnerable occupants
• No cool in extreme heat with vulnerable occupants
• Sparking electrical / burning smell

Urgent but schedulable soon

• System down but safe temps
• Minor leak contained
• No hot water
• Strange noises without safety signs

Questions that unlock triage

1. Is anyone in immediate danger?
2. What is the indoor temperature / is water still flowing?
3. Any gas smell, CO alarm, or sparking?
4. Membership status?
5. Can you shut off water/gas if directed?

Copy-paste scripts

Copy these, then edit bracketed fields so they sound like your shop.

Safety first

If you smell gas, leave the home and call your gas emergency line. I can also notify our on-call once you are safe.

No cool extreme heat

Understood. Who is in the home, and what is the current thermostat reading? I am prioritizing this.

Contained leak

Thanks. If you can stop the water at the valve, do that now. I can offer {Window} for a tech.

Metrics worth tracking every week

Fifteen minutes every Monday. Same numbers. Same owners.

Metric	How to count it	Target
Triage accuracy	QA sample of emergency tags	High
False emergency pages	Non-emergencies paged	Trend down
Safety script compliance	Gas/CO script used when needed	100%
Time to page	Emergency to on-call page	Under 5 min

Honest limitations: when a human must take over

CSRs and AI are not first responders. When in doubt on safety, escalate and tell the caller to use emergency services.

• Gas/CO
• Medical distress
• Structural collapse risk
• Threats of violence

Implementation checklist

1. Publish emergency definitions
2. Post tree at phones
3. Train monthly
4. Encode into AI
5. QA ten calls/week in season
6. Update after incidents

Operator FAQ

Caller refuses safety steps?

Document, escalate to owner, still urge emergency services when needed.

Member always first?

Only if policy says so and safety is equal.

AI allowed to page?

Yes with strict tag rules and logging.

Petunia can run first-line triage with hard handoff rules for true emergencies. Features · Pricing.

Related pages: After-hours, AI trust, Seasonal surge.

Writing the tree

Ambiguity creates false pages and missed danger.

1. One-page tree

One-page tree. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

2. Examples per branch

Examples per branch. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

3. Member rules

Member rules. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

4. Commercial exceptions

Commercial exceptions. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

5. Version date on the sheet

Version date on the sheet. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

QA without blame

Triage improves with calm review.

1. Weekly samples

Weekly samples. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

2. Focus on safety misses first

Focus on safety misses first. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

3. Coach language

Coach language. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

4. Update tree from real calls

Update tree from real calls. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

5. Share near-misses

Share near-misses. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

Seasonal re-training

Heat and freeze change volumes and nerves.

1. Pre-season drills

Pre-season drills. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

2. Temp thresholds posted

Temp thresholds posted. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

3. On-call capacity plans

On-call capacity plans. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

4. CSR backup lists

CSR backup lists. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

5. Owner availability rules

Owner availability rules. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.