Straight answer
A homeowner asks the roofer to compare project scope and a required carrier, adjuster, or project document is missing.
Best fit
Inspected projects with a customer-requested scope comparison.
Conditional fit
Send within one business day after the document task is created.
Main tradeoff
Unsolicited claim outreach.
Subject
Documents needed to compare your roof scopeHi {{client_name}},
To compare the roofing scope with the documents you received, please send the items below through {{secure_upload_link}}:
- The carrier or adjuster scope, if one has been issued
- Relevant roof estimate pages and line items
- Inspection photos or reports not already in our file
- Any material, code, or deadline notices you want us to review
You may redact unrelated policy or financial information. We use these documents to identify differences between the written roofing scopes—materials, quantities, underlayment, flashing, ventilation, permits, cleanup, and warranty—not to decide coverage or promise payment. Your insurer controls claim and coverage decisions.
Upload the documents here: {{secure_upload_link}}. If you are unsure which pages are relevant, reply or call {{phone_number}} before sending them.
{{coordinator_name}}
{{company_name}}
{{license_number}}
Best For
- Inspected projects with a customer-requested scope comparison.
- Teams using secure document upload and limited access.
- Clearly identified missing-document tasks.
Not Best For
- Unsolicited claim outreach.
- Requests for unnecessary policy or financial data.
- Messages promising insurance outcomes or interpreting coverage.
Variable Tokens
When To Send This Email
Trigger
A homeowner asks the roofer to compare project scope and a required carrier, adjuster, or project document is missing.
Timing
Send within one business day after the document task is created.
Frequency
Send once, then one reminder after 3 business days if the task remains open.
Timing note
Do not invent claim deadlines; reference only dates supplied in the customer's documents.
Why This Email Works
Personalization Notes
- Request only documents relevant to the stated scope-review task.
- Use an approved secure upload channel.
- Reference deadlines only when verified from customer-provided documents.
Platform Setup Steps
Trigger
Open document task tied to an inspected roofing opportunity.
Segment
Homeowners who requested project-scope support and have a missing document.
Delay
Within one business day; optional reminder after 3 business days.
- Confirm the exact missing document and legitimate purpose.
- Send the secure upload link and redaction guidance.
- Mark complete on upload and notify the assigned estimator.
Stop conditions
- Stop on upload, reply, task cancellation, claim-context removal, or opt-out.
- Stop when the document is already present or no longer required.
- Do not request full policy or financial records when limited pages are sufficient.
Compliance / Risk Notes
- Use secure handling for claim, property, policy, and financial documents.
- Request the minimum relevant information and permit redaction of unrelated details.
- Do not promise coverage, approval, payout, deductible treatment, or deadlines not verified in customer documents.
Subject Line Variations
- Documents needed to compare your roof scope
Focuses on the contractor's legitimate role.
- Secure upload for your roofing project documents
Use when channel security is the main concern.
- Missing document for your roof scope review
Use when the CRM identifies a specific open task.
Mistakes To Avoid
- Requesting the entire policy by default
It may collect unnecessary sensitive information.
Use instead: Request only pages relevant to scope comparison and allow redaction.
- Presenting the roofer as a claim decision-maker
The carrier controls coverage and payment.
Use instead: Limit the purpose to factual roofing-scope comparison.
Sequence Placement
Roofing Storm Damage Follow-Up Sequence
Related Email Platform Guidance
home-service teams that need configurable call, form, pipeline, appointment, email, and SMS follow-up outside their field-service system
Not best for: teams that need native technician dispatch, route optimization, job costing, equipment history, or service-agreement operations
View GoHighLevelPaid linkestablished home-service organizations that need scheduling, dispatch, job, customer, equipment, and service-agreement operations in one field-service platform
Not best for: solo operators that only need lightweight scheduling, quoting, and follow-up
Visit ServiceTitan
Disclosure
Some platform links on this page are paid links. If you choose a platform through one of them, EmailCampaigns.io may earn a commission. That does not change our recommendations. We include best for and not best for notes so you can decide based on fit, not payout.