Lesson 4 of 15 · 6 min

Emergency-first call flow: first to answer wins

Answer plumbing emergencies first, because the first company to answer wins.

Read the lesson

Goal: Build a plumbing call flow that spots emergencies first and gets them to a person fast.

You need: A live voice agent, Transfer to your team on, and the client's own emergency wording in writing.

Why this matters

A burst pipe does not wait. Water runs across the floor while the homeowner dials. They call the first plumber on the map. If nobody answers, they call the second one before the voicemail beep ends.

That is why plumbing is "first to answer wins." The job goes to the company that picks up and acts. Price comes later. Reviews come later.

Most plumbing shops already know this. Their problem is coverage. The owner is under a sink. The office is on the other line. At night, the on-call tech is asleep with the phone on the dresser.

The AI answers every call on the first ring, day and night. It asks one question first: is this an emergency? Then it sends the emergency to the on-call person, and books the rest.

Size changes the flow:

  • Owner-operator. The owner is the only on-call person. Transfers go to their cell. Routine calls book straight onto their calendar.
  • Fleet (Northside Plumbing, 8 techs). An on-call tech changes each week. The office decides how the transfer number changes.
  • Multi-location. Each location may have its own on-call person and its own emergency rules.

Emergency first, everything else second

The flow has three branches. The agent decides the branch from the caller's first answer.

Emergency signs might be water running now, no water at all or a sewage backup. The agent reads the client's safety line and transfers. Urgent signs might be a contained leak or one fixture out. The agent books the earliest slot today or tomorrow. Routine calls are a dripping faucet, a quote or maintenance. The agent books a normal slot.

Fig 1

Emergency-first call flow

  1. AI answers on the first ring
  2. Does the caller name one of the client's emergency signs?YesRead the client's safety line word for word, then transferEnds hereNoAsk the next question
  3. Is it urgent, such as a contained leak?YesBook the earliest slot today or tomorrowNoRoutine: book a normal slot
  4. Did the call end with no booking and no transfer?YesCall ended: Create CRM Task for a callbackNoDone
  5. Every caller has a next step
The emergency question comes first. Every branch ends with an action. The client lists the signs.

The client decides what counts as an emergency. You write their list into the agent. You never decide it yourself.

The client also writes the safety words. That includes any line about shutting off water or calling 911. Each client writes its own wording with its own advisors. SAU gives no standard safety script. Your job is to get the exact words in writing and put them in the agent word for word.

Use this template. The client fills in every bracket.

The transfer has limits you must know. Transfer to your team holds one phone number. There is no on-call rotation. A briefed warm transfer is coming soon. Today the call goes straight to that number.

Fig 2

Where the emergency transfer is set

Transfer to your team

Transfer to your teamOn
Transfer phone numberThe on-call phone: one number only
Transfer when…Emergency: on
Warm transferComing soon
The transfer holds one number. There is no rotation. A briefed warm transfer is coming soon.

So decide with the owner how the on-call number works. Two common choices:

  • One shared on-call cell phone that passes to the on-call tech each week.
  • The office updates the number in Actions every Monday.
Fig 3

Two ways to run the on-call number

Shared on-call cell
  • The number in Actions never changes
  • The phone passes to the on-call tech each week
  • Risk: a missed handoff
Office updates the number
  • Each tech uses their own phone
  • Someone edits Actions every Monday
  • Risk: a forgotten Monday
Agree on one with the owner, then test that the phone rings a real person.

Build it in ServiceAgent

  1. Get the client's emergency signs and safety line in writing. Keep a copy in the client's folder.
  2. Open Voice Agents, then the agent, then Basics. Put the AI disclosure in the Initial greeting, in the client's words.
  3. In the voice instructions, make the first question about the emergency. Paste the template with the client's words.
  4. Open Actions. Turn on Transfer to your team and enter the on-call number.
  5. Under Transfer when…, turn on Emergency.
  6. Set Human handoff behavior → Always transfer urgent calls.
  7. Set After-hours behavior → Triage urgent vs routine.
  8. Turn on Schedule in Allowed actions so urgent and routine calls book live.
  9. Open Follow-up. Add "When Call ended then Create CRM Task" for any call that did not book or transfer.
  10. Open Test & publish. Test with Talk in browser using five scripted callers.
  11. Click Publish.

Check it works: Run one Call my phone test as a burst-pipe caller. Confirm the safety line is word for word. Confirm the transfer rings the on-call phone.

Fig 4

Before the emergency flow goes live

  • Emergency signs from the client, in writing
  • Safety line from the client, word for word
  • On-call phone plan agreed
  • Transfer when… Emergency on
  • Five browser tests and one real call
Nothing goes live without the client's own words.

Worked example: Northside Plumbing

Northside has 8 techs and runs Core. The owner is Carol. The audit found 25 calls a day, with 14% missed, and a $380 average job.

Missed calls per business day: 25 × 14% = 3.5.

Missed calls per month, at 22 business days: 3.5 × 22 = 77.

At the approved 42% booking rate on answered calls: 77 × 42% = 32.34 jobs.

At $380 a job: 32.34 × $380 = $12,289 a month at risk.

Some callers call back on their own. So show Carol half as the safe number: about $6,145 a month.

Fig 5Example numbers

Northside's monthly leak

Missed a day: 25 × 14%3.5
Missed a month: 3.5 × 2277
Jobs lost: 77 × 42%32.34
Revenue at risk: 32.34 × $380$12,289
÷Safe figure: half2
Safe figure for Carolabout $6,145 a month
Show the owner the half figure, because some callers call back.

Now the credits. If all 77 calls go to the AI at 3 billed minutes each:

  • 77 × 3 = 231 minutes.
  • 231 × 15 = 3,465 credits.

Core includes 2,000 plan credits a month. Northside needs about 1,465 more. One 2,500-credit pack costs $80. Three Safe Packs cost $60 for 1,500 credits. Carol picks the 2,500 pack. It costs 3.2 cents a credit, against 4 cents for Safe Packs. The spare 1,035 credits roll over.

Night calls add to this. Pull the after-hours count from Analytics → Calls and repeat the math.

Reading the first week of transcripts

Go-live is the start, not the end. In the first week, read every call the agent marked as an emergency. Then read a sample of the routine calls.

Look for two errors. A false emergency is a dripping faucet sent to the on-call phone at midnight. A missed emergency is a burst pipe booked for Thursday. The second error is far worse.

Fig 6

Two errors to look for in transcripts

It was a real emergency
Missed emergencyBurst pipe booked for Thursday. Fix now
CorrectSafety line, then transfer
CorrectDripping faucet booked normally
False emergencyA drip sent to the on-call phone at midnight
Agent treated it as an emergency
A missed emergency is far worse than a false one. Fix the signs list, never the safety line.

Fix errors by changing the client's list of emergency signs, never the safety line. If the safety line needs a change, the client rewrites it. Then test again in the browser and publish.

Common mistakes

  • Writing your own safety line. Fix: the client writes it with its advisors. You paste it word for word.
  • Emergency question asked last. Fix: ask it first. A caller with water on the floor will not wait through a menu.
  • A transfer number nobody answers. Fix: agree on who holds the on-call phone each week, and test it.
  • No task when a transfer fails. Fix: the Call ended task catches it. Someone calls back in minutes.
  • Testing only in the browser. Fix: one real Call my phone test before go-live, to hear the transfer ring.

Do this now

Send your client the emergency template with blank brackets. Ask for the emergency signs, the safety line and the on-call plan in writing. When it comes back, build the flow in a draft and run five browser tests.

Practice the conversation

  1. Owner What does the AI say if a pipe bursts at 2 am?
  2. Operator Whatever you tell it to. You write the safety line, and I paste it word for word.
  3. Owner I do not want it giving repair advice.
  4. Operator It will not. It reads your line, then connects the caller to your on-call plumber.
  5. Owner We rotate on-call every week.
  6. Operator The transfer holds one number. A shared on-call phone that passes each week works best.
  7. Owner And if nobody picks up?
  8. Operator The call ends with a task for your team. You see it first thing.
  9. Owner What is all this worth?
  10. Operator On your numbers, about $6,100 a month, even if half those callers would call back.

Quick check

  1. Who writes the safety line the agent reads to a caller with a burst pipe?
    • The Operator, from SAU's standard script
    • The AI, based on the caller's words
    • The client, with its own advisors
    • ServiceAgent support
  2. A plumber gets 30 calls a business day and misses 10%. Use 22 business days, a 42% booking rate and a $400 job. What is the revenue at risk each month?
    • $11,088
    • $5,544
    • $26,400
    • $9,240
  3. A fleet rotates on-call each week. How do you set up the transfer?
    • Add all on-call numbers to `Transfer to your team`
    • Turn on the rotation setting in `Actions`
    • Use one shared on-call phone, or update the number each week
    • Send emergencies to voicemail and call back

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community