Bottom line
A verified hail, wind, or heavy-rain event affected the recipient's service area and the contact has valid relationship or consent context.
Best for
Verified storm events affecting an existing customer or opted-in service-area segment.
Use when
Send within 24-72 hours after event verification and capacity review.
Watch for
Untargeted cold storm-chasing lists.
How to Use This Email
When to use this
A verified hail, wind, or heavy-rain event affected the recipient's service area and the contact has valid relationship or consent context.
What’s on their mind
The homeowner distrusts storm-chaser outreach and does not want a contractor to assume damage or promise insurance coverage.
What this email should do
Offer a local roof inspection and photo-documentation path after verified hail, wind, or heavy rain without assuming damage.
Best sender
Office coordinator
Read the Finished Email
Review the message as a recipient would see it. The names and business details are fictional.
Subject
Roof inspection availability after the October 14 stormHi Jordan,
The the current details event on October 14 affected parts of the current details. That does not mean your roof is damaged, and a roof cannot be evaluated reliably from neighborhood activity alone.
- Company and name: Northstar Services
- Date-stamped photos of observed conditions
- A plain-language inspection summary
- Repair, monitoring, or replacement options only when supported by findings
- Project documents you may choose to share with your insurer
Our next verified inspection window is 2:00–4:00 p.m.. Book here: https://example.com/next-step, or reply with the address and what you noticed. We document roof conditions; your insurer controls coverage, claim decisions, and payment.
the current details
Northstar Services
(555) 014-0182
REF-1042
Template to copy
Subject
Roof inspection availability after the [Storm date] stormHi [First name],
The [Storm type] event on [Storm date] affected parts of [Service area]. That does not mean your roof is damaged, and a roof cannot be evaluated reliably from neighborhood activity alone.
- Company and name: [Company name]
- Date-stamped photos of observed conditions
- A plain-language inspection summary
- Repair, monitoring, or replacement options only when supported by findings
- Project documents you may choose to share with your insurer
Our next verified inspection window is [Inspection window]. Book here: [Booking link], or reply with the address and what you noticed. We document roof conditions; your insurer controls coverage, claim decisions, and payment.
[Coordinator name]
[Company name]
[Phone number]
[License number]
Subject Line Variations
- Roof inspection availability after the [Storm date] storm
Ties the offer to a verified event and real capacity.
- Not sure whether the storm affected your roof?
Leads with diagnostic uncertainty.
- Photo documentation for your roof after [Storm type]
Use when documentation is the main value.
Best for
- Verified storm events affecting an existing customer or opted-in service-area segment.
- Local roofers with documented inspection capacity.
- Teams that produce date-stamped findings and clear next steps.
Don’t send this if
- Untargeted cold storm-chasing lists.
- Messages asserting damage or insurance outcomes before inspection.
- Markets where event footprint or inspection capacity cannot be verified.
When to Send It
Trigger
A verified hail, wind, or heavy-rain event affected the recipient's service area and the contact has valid relationship or consent context.
Timing
Send within 24-72 hours after event verification and capacity review.
Frequency
Send once per material local event; deduplicate overlapping weather alerts.
Timing note
Use only verified event, service-area, and inspection-capacity data.
Make This Email Yours
- Use weather data and service-area matching approved by operations.
- Populate only current inspection availability.
- Do not use a homeowner's claim status unless they supplied it for this workflow.
Before You Use This Email
Why This Approach Works
Platform Setup Steps
Trigger
Verified local weather event plus eligible service-area segment.
Segment
Known customers or opted-in local leads, excluding active projects, duplicate alerts, and unresolved complaints.
Delay
24-72 hours after event verification and dispatch-capacity review.
Reply owner: Roofing storm-inspection coordinator responsible for event eligibility, capacity, bookings, and replies.
- Verify event footprint and eligible contacts.
- Insert truthful inspection window, local office, booking path, and license details.
- Assign replies and bookings to the storm-inspection queue.
Stop conditions
- Stop on booking, reply, active project, duplicate event, service-area mismatch, or opt-out.
- Stop when inspection capacity no longer matches the stated window.
- Suppress contacts without the required relationship or consent context.
Mistakes To Avoid
- Claiming every roof in the neighborhood was damaged
Weather exposure is not proof of property damage.
Use instead: Offer inspection and documentation without a conclusion.
- Using insurer or adjuster scarcity as pressure
The roofer does not control claim decisions or carrier staffing.
Use instead: Describe the contractor's documentation process and real schedule only.
Sequence Placement
Roofing Storm Damage Follow-Up Sequence
Related Email Platform Guidance
small teams publishing newsletters, announcements, and simple series
Not best for: teams designing complex event-driven lifecycle systems
View Constant Contactagencies standardizing lead-response systems across multiple accounts
Not best for: teams expecting a native field-service or legal practice-management system
View GoHighLevelPaid linkestablished home-service businesses with complex dispatch and operating requirements
Not best for: solo operators needing lightweight scheduling and invoicing
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.