---
title: "Supreme Restoration Group Case Study: A calendar that refuses a double-booking | The Quiet Protocol"
description: "Supreme Restoration Group, disaster restoration (water, fire, and mold) in Texas. The calls were already being answered. The problem started after the…"
url: "https://www.thequietprotocol.com/proof/supreme-restoration-group"
---

![A flooded basement mid-restoration: air movers and a dehumidifier running while a gloved hand checks moisture in the wall.](https://www.thequietprotocol.com/images/proof/restoration-basement-drying-1600.webp)

[The casebook](https://www.thequietprotocol.com/proof#transformations) Case 02 of 06

# Supreme Restoration Group

The calls were already being answered. The problem started after the phone was put down.

- **Business**: Disaster restoration (water, fire, and mold)
- **Location**: Texas
- **Size**: 22 staff across 6 restoration crews and 3 estimators
- **Before**: A part-time dispatcher coordinating crews over a group chat and a whiteboard in the office

## As we found it

Supreme already answered almost every emergency call. The trouble started right after: deciding which crew and estimator to send, and whether the office had any real idea where its crews actually were.

During flood and hail season, crews doubled up on the same job while other jobs sat unassigned. Estimators drove out to sites a different crew had already covered. Customers already dealing with water damage waited an extra hour or two for a crew to show. Adjusters noticed the delays too, and paperwork slipped right along with it.

- **Structure**: Emergency water, fire, and mold restoration, working directly with insurance adjusters on claims
- **Seasonality**: Spring flood and summer hail season roughly doubles emergency job volume

They already had a dispatcher.

Supreme already had a part-time dispatcher. That didn't help, because the dispatcher was still running everything off a group chat and a whiteboard. No single source of truth means no real coordination, no matter how good the dispatcher is. The company needed the system to prevent conflicts, not a person to catch them after the fact.

## A calendar that refuses a double-booking.

The same operation, drawn twice. Switch sheets or slide the overlay to see what changed, and what stayed the same.

- **As found**: A whiteboard and a group chat
- **As built**: A calendar that refuses a double-booking

Overlay

**As found.** One crew lands on two jobs. Another sits idle. Three emergency jobs wait with nobody assigned.

**As built.** Every job has one crew and one time, and each arrival checks in so the office can see it.

## What we installed

Product families involved: Custom Business Systems, AI Receptionists and Intake Agents, Follow-Up and Automation.

| Item | System |
| --- | --- |
| 01 | Custom Business System modeling jobs, crews, estimators, and insurance status as connected records instead of a whiteboard |
| 02 | Automated crew-availability calendar that prevents a crew from being assigned to two jobs at once |
| 03 | AI Receptionist tagging emergency severity and property type at intake so the system suggests the right crew type |
| 04 | Workflow automation compiling photos and moisture readings into an adjuster-ready report on job close |
| 05 | Mobile check-in notifications giving the office real-time visibility into crew arrival and departure |

## How one change led to the next.

Read it left to right. Each step depends on the one before it, from the system itself to what the business felt. Take one out and the chain breaks.

### System change

1. Step 1 A structured job-crew-calendar model replaces the whiteboard

### Behavior change

1. Step 2 Crew assignment becomes conflict-free by construction, not by the dispatcher catching mistakes

### Operational effect

1. Step 3 Fewer on-site delays from double-booked or misrouted crews
2. Step 4 Faster, more complete insurance paperwork handoff at job close

### Business effect

1. Step 5 Shorter claim-to-payment cycles for customers already under financial stress
2. Step 6 Adjusters trust Supreme with more of their referred jobs

## What the numbers did.

Monthly emergency jobs booked, counted at every stage. Each percentage is worked out from the counts beside it.

Before: 22.9%

First 90 Days: 85.6%

Of emergency jobs had the insurance packet in within 48 hours. Before: Spring flood season (pre-implementation). First 90 Days: Late summer (post-hail-season steady state).

### Before

Spring flood season (pre-implementation)

22.9%

of emergency jobs had the insurance packet in within 48 hours

Crew assignment runs on a group chat and a whiteboard with no conflict prevention.

- Jobs booked 96
- Correct crew assigned on the first attempt, 63.5% of prior 61
- Completed without a scheduling-conflict delay, 70.5% of prior 43
- Insurance packet submitted within 48 hours, 51.2% of prior 22

### First 30 Days

Early summer (first full month live)

58.7%

of emergency jobs had the insurance packet in within 48 hours

The structured calendar and mobile check-ins are live through the start of hail season.

- Jobs booked 104
- Correct crew assigned on the first attempt, 84.6% of prior 88
- Completed without a scheduling-conflict delay, 89.8% of prior 79
- Insurance packet submitted within 48 hours, 77.2% of prior 61

### First 90 Days

Late summer (post-hail-season steady state)

85.6%

of emergency jobs had the insurance packet in within 48 hours

Job volume grows as adjuster referrals increase, and the system holds up at higher volume.

- Jobs booked 118
- Correct crew assigned on the first attempt, 94.9% of prior 112
- Completed without a scheduling-conflict delay, 96.4% of prior 108
- Insurance packet submitted within 48 hours, 93.5% of prior 101

## Other measures in the case.

### Dispatcher reconciliation time recovered

As found 1,334.84 hrs/year

As built 102.96 hrs/year

Annual labor cost: $37,376 as found, $2,883 as built. Recovered: **$34,493** a year.

Modeled at pre-implementation spring job volume versus post-hail-season volume. Higher job volume after implementation still produces less reconciliation time.

### Jobs requiring a second crew dispatch due to a scheduling conflict

Before: 1 in roughly every 2.2 jobs

After: 1 in roughly every 11.8 jobs

Taken straight from the job counts above, before implementation and at Day 90.

## Who felt the change.

### For the team

The dispatcher works from a calendar that simply won't double-book a crew, instead of catching the conflict after it's already caused a delay.

### For customers

A crew shows up when it's supposed to, right when the customer is already dealing with a flooded basement or a fire.

### Twelve months on

As adjusters learn to trust Supreme, the company can take on more referred claims without hiring more dispatchers. The coordination layer scales. A person doesn't.

### How customers see them now

Homeowners and adjusters now see a company that arrives organized and on time, right when it matters most to them.

## What this case proves.

Call capture and job coordination are two different problems. You can fix one and still have the other.

If your phones already get answered but things still fall apart, look at what happens right after the call ends. Answering calls well and running jobs well are two different systems.

The lesson any business can take from Supreme Restoration Group.

[Carter CPA's & Advisors A four-partner firm that couldn't tell a referral from a cold lead until the call had already started. Read the next case ![A partner's desk after hours in tax season: stacked client folders, a desk phone with a waiting message, the lamp still on.](https://www.thequietprotocol.com/images/proof/cpa-tax-season-desk-800.webp)](https://www.thequietprotocol.com/proof/carter-cpas-and-advisors)

## You've read the record. Now let's draw yours.

Every case here started the same way: the business as it runs today, drawn honestly. A call with us does that for yours, then tells you whether the first move is a website, call coverage, connected follow-up, or something custom.

[Book a call](https://www.thequietprotocol.com/book/intro)

- **Record**: Your business
- **Sheet**: As found
- **Survey**: Not yet started