AI can help waterproofing contractors record leak enquiries and prepare site visits, but it cannot establish the source of water intrusion from a brief conversation. Keep observations, inspection findings, and proposed remedies separate. When a request involves facade safety or FISP documentation, qualified professionals must verify the relevant requirements.
Capture the pattern of the reported leak
Ask where water appears, when it was first noticed, whether weather seems related, and whether previous repairs are documented. Record the customer’s exact observations without converting correlation into cause. Water appearing near a window may originate elsewhere in the assembly. Note the building contact, affected unit, access arrangements, and urgency. If the caller describes a potentially dangerous condition, follow the approved escalation route rather than continuing a routine estimate interview.
Collect evidence without creating risk
Request existing photographs, maintenance records, prior repair scopes, and relevant reports through an approved upload process. Do not ask occupants to access roofs, ledges, or other hazardous areas to gather more evidence. Label each item with the property and reported location. AI can assemble a chronological summary and highlight gaps. A qualified reviewer should verify that it preserves uncertainty and does not turn a previous contractor’s opinion into an established finding.
Prepare the site visit and diagnostic questions
Create an agenda covering access, occupancy, relevant interfaces, prior work, and who can authorize investigation. Keep diagnostic work distinct from a repair proposal so the customer understands what the visit can establish. Ask the estimator to identify information needed before recommending a scope. If the building has facade reports, retrieve the current versions. Use the NYC DOB facade safety resource to locate official program information, then confirm property-specific obligations.
Draft scope with explicit limits
Generate proposal text only from approved findings and the contractor’s reviewed repair approach. Describe the work location, preparation, materials, access, exclusions, and any testing or inspection included. Avoid broad promises that one intervention will eliminate every leak in the building. Warranty language must come from approved terms. If new evidence changes the likely source or repair boundary, pause automated follow-up and return the project to technical review before issuing a revised offer.
Measure diagnosis and communication quality
Track complete enquiry records, unnecessary repeat visits, missing documents, proposal revisions, and callbacks caused by unclear scope. Compare projects by building type and investigation complexity. Record whether the customer understood the next step and whether the responsible professional received the evidence. Begin with intake summaries and appointment preparation rather than automatic pricing. A successful pilot helps the team arrive better prepared while preserving the distinction between a reported symptom, a verified condition, and an agreed repair.
Keep building your understanding
Start with one useful workflow.
Tell us what happens today and where it gets stuck. We’ll help define a practical next step.