Straight answer
A completed roofing project has a clean closeout record and no open service, warranty, property, billing, or complaint issue.
Best fit
Completed-project customers with clean closeout records.
Conditional fit
Send after the post-job review and only after enough time to confirm closeout remains clean.
Main tradeoff
Customers with open workmanship, warranty, cleanup, property, billing, or complaint issues.
Industry Context And Next Action
Subject
Know someone who wants a documented roof inspection?Hi {{client_name}},
Thank you again for choosing {{company_name}} for the {{project_type}} at {{property_address}}.
If someone you know independently wants help with a roof inspection, repair, or estimate, you can forward this introduction link: {{referral_link}}. It lets them choose whether to contact us and what information to share.
We will not ask you for a list of neighbors or assume another property has damage. If your own cleanup, workmanship, warranty, billing, or documentation still needs attention, reply to {{service_owner}} instead so we can address it before any referral request.
{{coordinator_name}}
{{company_name}}
{{phone_number}}
{{license_number}}
Best For
- Completed-project customers with clean closeout records.
- Permission-based referral forms initiated by the referred person.
- Teams able to disclose and govern any referral incentive.
Not Best For
- Customers with open workmanship, warranty, cleanup, property, billing, or complaint issues.
- Purchased, scraped, or customer-supplied neighbor lists.
- Storm messaging that assumes damage at referred properties.
Variable Tokens
When To Send This Email
Trigger
A completed roofing project has a clean closeout record and no open service, warranty, property, billing, or complaint issue.
Timing
Send after the post-job review and only after enough time to confirm closeout remains clean.
Frequency
Send once per completed project.
Timing note
Do not tie the request to unverified storm damage or neighborhood fear.
Why This Email Works
Personalization Notes
- Verify the project closeout and issue state immediately before sending.
- Use a permission-based introduction link rather than requesting contact lists.
- Disclose any referral incentive and its conditions if one exists.
Platform Setup Steps
Trigger
Completed project passes closeout and service-recovery checks after the review step.
Segment
Completed residential customers with valid consent and no open issue or prior referral request for the project.
Delay
After the review request and confirmed clean closeout.
Reply owner: Roofing customer-care owner responsible for referral replies and any reopened project issue.
- Recheck completion, warranty delivery, issue, billing, complaint, and referral-request history.
- Send the permission-based referral link and any required incentive disclosure.
- Route project concerns to service recovery and record only contacts who independently submit the referral form.
Stop conditions
- Stop on reply, referral submission, reopened project issue, complaint, dispute, duplicate request, or opt-out.
- Stop when the referral offer or disclosure changes.
- Do not import neighbor or third-party contact data supplied without a valid outreach basis.
Before You Send
Note: there are laws and regulations around this. Please make sure you follow any applicable rules before sending.
Subject Line Variations
- Know someone who wants a documented roof inspection?
Frames the referral around a useful process.
- An optional introduction to {{company_name}}
Makes the request low pressure.
- Forward this only if someone asks for roofing help
Clarifies permission and intent.
Mistakes To Avoid
- Asking for every neighbor's email
The neighbors did not independently request contact.
Use instead: Give the customer an optional link to forward.
- Sending while a project issue is open
It prioritizes acquisition over customer care.
Use instead: Suppress and route the issue to service recovery.
Sequence Placement
Roofing Post-Job Care Sequence
Related Email Platform Guidance
agencies standardizing lead-response systems across multiple accounts
Not best for: teams expecting a native field-service or legal practice-management system
View GoHighLevelPaid linksmall and midsize home-service teams centralizing job operations and communication
Not best for: teams needing highly customized enterprise capacity and multi-entity controls
Visit Housecall Proservice teams managing requests, quotes, visits, recurring work, invoices, and payments
Not best for: large enterprises requiring sophisticated call-center and capacity operations
Visit Jobberestablished 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.