The contract is signed. The deposit cleared. The homeowner is happy. Then, about ten days later, the phone starts ringing again.
"When are you starting?" "Is it still Thursday?" "Did my shingles come in?" "Do I need to move the cars?"
None of these calls are new business, and none of them should be hard. But in a lot of roofing offices they land on the same people who answer new leads, and they get handled from memory. Someone checks the board, guesses, and promises a day the production manager never agreed to. Then the weather turns and the crew slides two days, and now the homeowner has been told two different things by your company.
Intake automation fits here. A missed sales call costs you a lead. A badly handled scheduling call costs you trust with someone who already paid a deposit.
Why signed customers call so much
Most of the calls between signing and tear-off come down to the same handful of questions:
- When does the crew show up, and roughly what time? - Has the material been delivered, or when will it be? - Do I need to be home? Should I move the car, the patio furniture, the things on the attic floor? - Is the permit done? - The forecast says rain. Are we still on?
ServiceTitan's 2026 roofing and exteriors report, a survey of more than 1,000 contractors, lists transparent communication as a top differentiator for 47% of respondents, behind only reputation at 59%. If nearly half of contractors say communication is how they win, the quiet stretch after signing is a strange place to go silent.
The same report says 34% of contractors point to sustained skilled-labor shortages as a pressure on the business. Short crews mean schedules move. Schedules that move mean more "are we still on?" calls. That's the job. The failure is answering those calls with guesses.
What the AI receptionist should do on these calls
The first job is recognition. When a call comes in, the receptionist should check the caller's number against signed jobs in your CRM or production system and confirm with a simple question, like "Is this about the roof replacement at 14 Oak Street?" If the number doesn't match, it asks for the name and address. It should not treat a signed customer as a new lead and walk them through the sales script again. Nothing makes a customer feel like a ticket number faster than being asked if they'd like a free inspection three days before their install.
Once it knows the job, it should answer only from what your system actually says. That's the rule that makes this safe:
- If the job has a confirmed crew date in the system, it can read that date back. - If the date is tentative, it says so in those words. "It's penciled in for the week of the 19th. The production manager confirms the exact day, and you'll hear from us before the crew is scheduled." - If material delivery is logged, it can say delivered. If not, it says it doesn't have a delivery date and takes the question to the person who does. - If there's no date at all, it doesn't make one up. It logs the request and tells the caller when to expect a callback.
That last case is where human answering goes wrong most. A friendly office person wants to give the caller something, so they say "probably next week." Your AI receptionist should be stricter than that, and you should write that rule down before it goes live.
Things it should never promise
Write these into the receptionist's rules explicitly:
- Never commit a crew date that isn't confirmed in the production schedule. - Never promise a weather call. Whether a crew goes up in light rain or high wind is a production decision on the day. The receptionist can say "the production manager makes that call the morning of, and we'll text you either way." - Never move a job. If the homeowner needs to reschedule, the receptionist collects the reason and the days that won't work and hands it off. Moving a crew affects other jobs. - Never answer change-order questions with a price. "Can you add gutters while you're up there?" is a real request. Log it, flag it for the salesperson or project manager, and say someone will follow up. Don't quote it. - Never discuss balance or final payment terms beyond what's already in writing. Route those to the office.
What to collect on every scheduling call
Even when the receptionist can answer the question, the call should leave a note. A good note on a signed-job call includes:
1. Job address and the name on the contract. 2. What the caller asked, in plain words. 3. What the receptionist told them, including whether the date read back was confirmed or tentative. 4. Access details the crew needs: gate codes, dogs, where to park the dumpster, cars that need moving, a contact number for the day if it's different. 5. Any new request, like added scope, a reschedule ask, or a concern about the neighbor's driveway, flagged for a person. 6. Whether a callback was promised, and by when.
Item 4 is the sneaky one. Homeowners mention the dog or the locked side gate on these calls all the time, and it never makes it to the foreman. Capture it and push it to the job record so the crew sees it.
The callback still needs a clock
Some of these calls have to go to a person. When they do, the receptionist should tell the caller when they'll hear back, and your team has to actually hit that time.
The best-known response-time research is about sales leads, not existing customers, but it says a lot about how teams behave. In a Harvard Business Review audit of 2,241 U.S. companies, 37% responded to a web lead within an hour, while 23% never responded at all. Among companies that did respond within 30 days, the average response time was 42 hours. If businesses treat leads they want that way, "I'll have the production manager call you" can slip just as easily.
A simple rule works: scheduling callbacks are returned the same business day, and anything inside 72 hours of the install date gets returned within two hours. Pick numbers your team can keep and put them in the script.
Get ahead of the calls with outbound updates
The best scheduling call is the one the homeowner never had to make. A text when the job lands on the calendar that says whether the date is confirmed or tentative, one when material is delivered, and one the day before with the arrival window and prep list will head off most of these calls. Get the customer's consent for texts first, and keep the messages plain. They need to know whether to move the car.
An example of how this sounds
This is a made-up example, not a real customer.
A homeowner calls on Tuesday afternoon. The receptionist matches her number to a signed reroof, confirms the address, and checks the schedule. The job shows a tentative start the following Monday, with material not yet delivered. The receptionist tells her the start is tentative, that the production manager confirms it by Thursday, and that she'll get a text either way. She mentions a side gate that sticks and a dog in the backyard. Those go into the job notes. She also asks whether the crew can look at a loose downspout. The receptionist logs that as an add-on request for the project manager and doesn't quote it.
Where to start
You don't need to automate every part of this on day one. Start by connecting the receptionist to the one field that matters most, which is whether the crew date is confirmed or tentative. Write the "never promise" rules. Add the access-details question to the call note. Then add the day-before text. That covers most of the calls you're getting now.
If you'd like help setting up signed-job call handling and install-date updates for your roofing company, [book a call with Chosen](https://chosenai.co/book).
Sources
- ServiceTitan, "ServiceTitan Report Finds 75% of Roofing and Exteriors Contractors Expect Revenue Growth in 2026 Despite Tighter Margins" (January 14, 2026): https://www.servicetitan.com/press/2026-roofing-exterior-market-report - James B. Oldroyd, Kristina McElheran, and David Elkington, "The Short Life of Online Sales Leads," Harvard Business Review (March 2011): https://hbr.org/2011/03/the-short-life-of-online-sales-leads