Contained-Loss Inspection Booking

Not every restoration call is an emergency. A dishwasher leak that was mopped up yesterday, a stain on a ceiling from last month's storm, mold behind a vanity: these are jobs, but they do not justify waking a technician. The booking path for contained losses is the second branch of a restoration intake flow. The agent still captures the full job, then offers an inspection slot from the real calendar instead of a callback promise.

How it works. After the safety and peril questions, the agent applies the contained-loss rules written by the shop: water is not actively flowing, occupants are safe, there is no sewage or fire involvement, and the damage can wait for a published estimator window. It captures address, peril type, affected rooms, insurance carrier and claim number if one exists, and requests photos by text link where available. It reads availability from the connected calendar, offers two or three windows, books the chosen one, sends a confirmation text and writes the job to the CRM. The call ends with a scheduled inspection rather than "someone will call you".

Why it matters for restoration shops. Overnight and weekend inquiries for non-urgent damage are a large share of estimate demand, and a voicemail converts poorly. Booking on the call captures the job while the caller is motivated and before they ring a second company. It also protects the on-call rotation: technicians are paged for active losses only, so they answer those pages faster. And the estimator's morning starts with a calendar of confirmed inspections carrying address and carrier details rather than a list of numbers to chase.

Example. A caller rings a restoration company on Sunday afternoon about a musty smell and a soft patch of drywall under a bathroom window. The agent asks whether water is currently coming in (no), whether anyone has symptoms (no), and whether there is standing water (no). It classifies the call as contained, captures the address and the homeowner's insurer, offers Tuesday 9-11 am or Wednesday 1-3 pm from the estimator's calendar, books Tuesday, and texts a confirmation with a link to upload photos. The job appears in the CRM before the office opens on Monday.

Contained-loss booking vs on-call escalation. Both branches start with the same intake. Escalation pages people until one acknowledges and is for active losses. Booking schedules a future visit and is for stable damage. The classification question between them is the single most important rule in the flow, and it should be written by the shop, not guessed by the model.

Common pitfalls.

• Booking from a calendar that is not the estimator's live one.
• Quoting mitigation prices on the call; the agent should book, not estimate.
• Treating "contained" as "unimportant" and skipping the insurance fields.
• No photo request, which the estimator needs before the visit.
• Offering slots too far out; a caller offered next week calls someone else.

Botcadence lists Google Calendar, Calendly and JobNimbus among its documented integrations and offers managed restoration coverage at $399 a month; see voice agents.