The short answer
A roofing estimate request should leave the intake stage with a clear description of the job, a service-area check, a responsible person, and an agreed next step. Treat inspection requests and appointment preferences as requests until the roofing team confirms availability. Keep the customer informed when the office still needs to review the job.
An estimate inquiry and a scheduled inspection are different.
A homeowner asking about a replacement may be ready to arrange a visit. Someone reporting a leak may first need the office to decide how to route the inquiry. A request for an inspection can have another purpose entirely. Ask what the person wants help with before choosing a scheduling path.
Use distinct statuses such as new request, details needed, office review, offered appointment, and confirmed appointment. These are suggested office labels, not promises about how every software system works. What matters is that the person reading the record can tell what is still owed to the customer.
What belongs in the handoff?
- Location and fit: the job location needed to check your approved service area and whether you handle that kind of property or work.
- Reason for contact: repair, replacement, inspection, or a question about an existing job, in the customer's own words.
- Requested timing: the customer's preference and any concern they report, without turning it into a guaranteed service commitment.
- Contact and access: the right person to coordinate with and any details your office actually needs to arrange the next step.
- Owner: who reviews the request, who confirms the visit, and where the customer should expect the answer.
Do not make a customer repeat details already submitted through a form or email. If information conflicts, clarify that one point. Keep photos or documents in the approved system rather than spreading them across informal inboxes.
Close the gap between a requested time and a confirmed time.
In a manual workflow, send the complete request to the office and say that availability still needs confirmation. Once a person confirms the slot, record the agreed time and any approved instructions. If the requested time is unavailable, make the alternative clear instead of silently changing the request.
For example, an intake note could read: "Replacement estimate requested. Service area checked. Customer prefers a weekday afternoon. Office review pending; no appointment confirmed." This is an illustrative record, not a real customer case.
CallBack Engine's roofing workflow supports Manual Scheduling as a complete path. Google Calendar is optional where authorized and configured. Neither path should imply that an inspection has occurred, a price has been agreed, or a job has been won.
What if the request goes quiet?
First determine who owes the next action. A customer waiting for your office is different from an office waiting for a missing detail. Review the last exchange before following up, keep any additional contact within your approved policy, and stop on a decline or opt-out.
Track the unresolved reason, not just the age of the lead. Missing location, no available slot, awaiting customer response, and estimate already sent need different actions. An owner should be able to open the queue and act without rereading an entire thread.
Practical questions
Should intake discuss insurance coverage or quote a repair?
Keep intake within the business's approved scope. Record the question and route it to the responsible person. Do not turn a customer's description into a coverage decision, diagnosis, or binding price.
What should we measure?
Review how many requests are waiting on the office, how many have a confirmed next step, and why others stopped. Separate requested appointments from confirmed appointments and completed inspections. That keeps the queue useful without overstating results.