What the first ninety seconds of a water loss call should capture.

A well-run restoration intake captures fourteen pieces of information in the first ninety seconds of a water loss call, and the difference between fourteen and eight is the gap between a profitable job and one that runs over scope.

The shape of the first call decides most of the economics of a restoration job. The dispatcher reading the intake record needs to know enough to send the right tech with the right equipment, give an accurate ETA, set the homeowner's expectations and start the insurance process. When the intake is thin, the dispatcher guesses. When the dispatcher guesses, the tech shows up with the wrong gear, the scope is off and the job either runs over budget or never closes.

This piece walks through what a well-run water loss intake captures, why each piece matters and where most restoration companies drop information.

The cost of a bad first ninety seconds

The math on bad intake is direct. A water loss called in at 2am with poor qualification typically results in a 25% to 40% chance the wrong tech gets dispatched (requiring a follow-up visit), a 15% to 20% chance the scope is mis-estimated by more than 30% (which kills margin), a 10% to 15% chance the insurance claim gets supplemented or rejected later because the FNOL was incomplete, and an average cycle time eight to twelve days longer than a properly intaken job.

Add those up across a year and the dollar cost of bad intake quality runs $50K to $200K at a $10M company. The dollars do not show up as missed calls. They show up as margin erosion on jobs that did book, which is harder to spot in the P&L.

What the well-run intake captures in ninety seconds

A properly trained intake conversation, AI or human, captures these fourteen items before the call ends:

1. Homeowner name and callback number.
2. Property address with cross-street if rural.
3. Loss cause (burst pipe, appliance failure, roof leak, storm).
4. Loss source (which fixture, which pipe, which floor).
5. Stoppage status: water still flowing, controlled by main shutoff, or unknown.
6. Category: Cat 1 clean, Cat 2 gray, or Cat 3 black. Determines crew and PPE.
7. Class: Class 1 through 4. Determines drying equipment.
8. Affected area: rough square footage and which rooms.
9. Affected materials: drywall, hardwood, carpet, tile, insulation.
10. Ceiling involvement: sagging, fallen or dry.
11. Insurance carrier and policy number if available.
12. Occupancy status: owner-occupied, rental or vacant. Determines who signs the authorization.
13. Urgency markers: children at home, medical equipment, pet on oxygen.
14. Access constraints: gated community, off-hours building, pet at home.

That looks like a lot to capture in ninety seconds. With a script designed around natural conversation flow, it is not. Most of the items emerge from how a homeowner naturally describes the loss when asked the right open question.

The opening question that gets most of it is "Can you walk me through what's happening?" The homeowner describes the situation, the intake person listens for the markers and follows up only on the gaps.

Why your dispatcher needs this before the tech moves

The dispatcher reading a complete intake record can do four things a dispatcher reading a thin record cannot.

A Cat 3 sewage backup needs different PPE and different equipment than a Cat 1 clean water loss. With the loss category captured, the dispatcher sends the right tech. Sending the wrong crew costs an hour of repositioning, sometimes more.

Knowing the Class number (Class 2 vs Class 4 dry-down) determines air mover and dehumidifier counts. A truck that shows up under-equipped either burns time on a parts run or under-scopes the job. With the Class captured, the dispatcher loads the right gear from the start.

The third gain is in setting the homeowner's expectations correctly. A homeowner told "someone will be there in forty-five minutes" who waits two hours has a worse experience than one told "this is a complex loss and your tech will arrive between 9 and 11am, with a phone call when he is fifteen minutes out."

The fourth is in the insurance process. A dispatcher with the carrier name and policy number in hand can file the FNOL the same night, which puts the claim ahead of the next-morning queue and shortens cycle time by 24 to 72 hours.

Where most intake scripts fail

The intake scripts in use at most mid-market restoration companies were written between 2010 and 2018 and have not been touched since. They fail in three predictable ways.

Over-asking is the first. Scripts that try to capture twenty-two items end up rushing the conversation and missing the markers that matter most. A homeowner who feels interrogated stops volunteering information.

The second failure is wrong sequencing. Scripts that ask for insurance details before establishing what happened make the homeowner feel like a billing record. The carrier and policy number should come after the loss has been qualified, not before.

The third is around the soft markers. Children in the home, a homeowner medical condition or an anxious pet are not on most intake scripts. Those markers are what makes a homeowner remember your company and refer their neighbor when the question comes up at the next block party.

How to test your own intake quality

The simplest test takes thirty minutes. Pull a random sample of ten water loss intake records from the last quarter. Check each against the fourteen-item list. Count how many items are captured cleanly in each record.

The benchmark we see for companies we audit before deployment is twelve of fourteen on the median call. Most companies land between seven and ten in the audit. The gap shows up later in scope-creep on the jobs that booked and in the rate of supplements that get rejected by the carrier.

If your company's average is below ten, the next conversation is whether the gap sits in the script, the training or the structure of the intake conversation itself.

The pattern at the companies doing it well

The companies with consistently high intake quality have three things in common.

They use a structured intake form rather than a free-text message field. The intake person or AI agent fills the same fourteen fields on every call, with required-field validation that prevents the form from being submitted incomplete.

Weekly intake reviews are the second pattern. Ten random calls get scored against the checklist, patterns flagged, and the dispatcher and intake person sit down to look at what got missed and why.

The third is integration. Intake data flows into the dispatch tool and carrier portal automatically, so the dispatcher does not retype, the estimator does not retype and the carrier portal gets a clean FNOL the same night.

Stoa runs all three of these by design. The intake script is structured around the fourteen-item capture, validates required fields before completing the call and pushes the structured data into your CRM and carrier portal automatically. The dispatcher coming in the next morning sees the full record with no manual data entry.

If your intake quality has not been measured this quarter, that is the cheapest piece of operational work you can do. Pull ten calls, run the checklist and see where the gap sits.

For the broader economics of intake, see the missed call cost piece. For why speed at intake wins more jobs, see fast first contact wins more restoration jobs than ad spend.