Route roofing enquiries by the customer’s stated goal, while leaving the decision between repair and replacement to a qualified assessment.
Classify the request, not the roof condition
Use labels that describe what the customer wants: help with a reported problem, planned replacement, maintenance inspection or uncertain. These are intake categories, not technical conclusions. A caller asking for replacement may still need an assessment; a caller requesting repair may learn that a different approach is required. Keep the original wording visible. That lets the roofer understand expectations without inheriting an unsupported diagnosis from the receptionist. Avoid labels such as “definite replacement” based only on the age of the property or a photograph.
Ask a question that reveals the purpose
Try: “Are you looking for help with a specific issue, planning a replacement, or asking us to assess the options?” Follow with location, property type and the timeframe the caller has in mind. A replacement enquiry may involve budgeting or a renovation schedule. A reported leak may involve an immediate callback under your approved policy. Do not use a rigid questionnaire to block a worried caller from reaching a person. The purpose of the question is to select the next appropriate conversation, not to force a technical choice.
Prepare different handoff notes
For a planned project, capture who approves the work, whether other work affects timing and what the customer wants to receive after the visit. For a reported issue, record the observation, when it started and any previous related job reference. For an uncertain enquiry, state exactly what remains unknown. Example: “Owner wants advice on options before exterior renovation; no inspection completed; seeks assessment next month.” Keep an estimated customer budget separate from a quotation. The business must decide whether asking about budget is useful at this stage.
Set expectations without making promises
State the booked visit’s purpose and any approved assessment terms. Do not promise that a replacement is necessary, a repair will work or an insurer will pay. Do not ask the customer to climb up to settle the category. HSE’s fragile-surface guidance supports leaving roof access to properly planned work. If the customer asks for technical advice, hand the question to an appropriate professional. A clear limit can build trust when it is paired with a useful next step rather than an abrupt refusal.
Audit whether the categories improve the diary
After a fortnight, review whether the labels helped staff allocate the correct visit and prepare appropriately. Look for enquiries repeatedly moved between categories or appointments booked with the wrong team. Simplify labels that nobody uses. Test an undecided caller, a caller correcting their request and a repeat customer with a new issue. The final record should keep the change visible and send the enquiry to one owner. Explore the roofing answering service to discuss how those routing rules fit your own intake process. Give staff a worked example for each label, including one ambiguous enquiry. If two colleagues choose different labels for the same record, clarify the definitions before using them in automated routing.
Sources and editorial notes
The workflow and examples are KEDO Labs editorial recommendations, not a promise of product functionality or professional advice. Sources checked October 8, 2026.
See the workflow
Hear the call. See the booking.
Watch KEDO handle a service enquiry, then review the current setup fee and monthly price before you pay.
Reading in Google?
Make KEDO a preferred source
Add KEDO Labs as a preferred source in Google and our guides are more likely to appear with a 'preferred' badge in Top Stories, and can carry a badge in AI Mode and AI Overviews.